Skip to main content

How is the electron cloud model different from a real atom?

The electron cloud model was designed by Erwin Schrödinger in 1926 with the help of Werner Heisenburg. These two physicists set out to solve a complicated problem that arose when trying to model atoms and make calculations based on electron positioning. The problem was that electrons moved incredibly fast, not in a fixed orbit but also in between energy levels, making it impossible to know exactly where the electrons were in space relative to the nucleus. At that point, the most current model was the Bohr model, and that model did not account for the movement of electrons between orbitals and was only two dimensional. While finding the exact position of an electron at any given time is impossible, Schrödinger realized that he could figure the probability of an electron being at a certain place in a given atom. Using these probabilities, he developed the electron cloud model which gave a three dimensional prediction of the location of electrons in an atom.


The electron cloud model is different from a real atom in that it depicts where an electron is likely to be instead of the actual position of the electron. This allows scientists to make calculations based on an educated guess of where the electrons are in relation to the nucleus of an atom. While a scientist may not know exactly where the electron is, the electron cloud model gives him or her enough information about where the electron probably is to use for his or her studies.

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...