-
Notifications
You must be signed in to change notification settings - Fork 6
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
Adjust min/max threshold for figures #39
Comments
@arouinfar I'm not sure I fully understand what you're looking for here. Could we take a few minutes today or tomorrow to discuss? |
After speaking with @mbarlow12, I've learned that the mapping between the force and the figure is a bit complicated, particularly because the force can be positive or negative. We spent some time adjusting |
@mbarlow12 let's go with |
Thanks! Fixed in above commit. Closing. |
When reviewing #27, I noticed that the figures could be a bit more responsive at the extremes.
At the default values, the figure appears to be figure_pull_1/ figure_pull_atomic_1, so decreasing the force does not show any apparent change in the figure's stance.
On Atomic Scale, there is a slightly larger range of forces that can go off-screen, as compared to Macro. (Partly due to the user's ability to get the charges closer to one another.) At the minimum distance, the figure takes the deepest stance for any charge combination greater than 1/2 e.
I think it would be a helpful visual cue if there was a bit more resolution at the lower and upper ends of the force range. The threshold for figure_1 could be a bit lower (on both screens) and the threshold for figure_31 could be a bit higher (on Atomic Scale). That way, students may still see the figure's stance move a bit, even when the vectors themselves are too extreme for a change in their magnitude to be noticeable.
I realize there will always be some degree of saturation where the force increases/decreases but the figure doesn't appear to change, but I would like to reduce the range where saturation occurs.
The text was updated successfully, but these errors were encountered: