Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atom name and abundance doesn't update when a neutron is grabbed #38

Closed
phet-steele opened this issue Jan 27, 2016 · 5 comments
Closed

Comments

@phet-steele
Copy link

In 1.0.0-dev.5, the name or abundance of an atom doesn't change when a neutron is grabbed out of the nucleus until the neutron is released. The symbol DOES update. @amyh-phet this behaviour does not match the Java and in my opinion is counter intuitive. The nucleus seen not matching the nucleus reported would cause confusion:

isoatma2

This video starts with Hydrogen-5, and I take one neutron out a time. When I grab the neutron, the nucleus only shows a mass of 4, but the name displayed is still Hydrogen-5. The symbol and scale correctly show a mass of 4.

phetsims/tasks/issues/488

@phet-steele
Copy link
Author

@aadish In the Java version of the sim, the name of the isotope updates when one of the two behaviors occurs:

  1. a neutron that is in the nucleus is selected
  2. a neutron from the bucket is dragged into the nucleus and released.

Can we investigate matching the behavior of the Java sim for neutrons on the Make Isotopes screen?

@aadish
Copy link
Contributor

aadish commented Feb 7, 2016

fixed, closing

@aadish aadish closed this as completed Feb 7, 2016
@phet-steele
Copy link
Author

phet-steele commented Feb 24, 2017

@aadish this is actually not fixed. The above commit does not take into account when you grab the LAST neutron from an atom. My guess is that

self.particleAtom.neutronCount > 0

should be changed to

self.particleAtom.neutronCount >= 0

@ariel-phet said in Skype:
"if possible this would be good to fix as a maintenance release so long as the [actual] fix is not too invasive"

@aadish
Copy link
Contributor

aadish commented Feb 27, 2017

@phet-steele thanks for catching this and yes the fix is the one suggested by you, it should have been fixed by the above commit, will go ahead and create a maintenance release

@phet-steele
Copy link
Author

Looks good, thanks @aadish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants