-
Notifications
You must be signed in to change notification settings - Fork 13
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
Consider adding an apex marker to the path #132
Comments
This would be super helpful for math teachers using this sim when teaching about parabolas. |
I think I could use basic physics equations to find the apex of the path that isn't affected by drag force, but I'm not sure how to calculate the apex for paths with drag force. @ariel-phet @arouinfar any ideas? Another option would be to use one of the three data points between each timing dot, and use the data point that is closest to the apex. Because the model collects data points every 25 ms but only shows timing dots every 100 ms. It would be close, but it wouldn't be exactly the apex, and may be more off if we have, say, a projectile with very high speed with more spaced out data points. |
@arouinfar @andrea-phet the apex will always occur when the velocity in the "y" direction is zero. So you probably just need to look for a velocity within some small range of zero for the vertical component of velocity. You might also be able to run a numerical solver to find the apex and @jonathanolson may have some idea. You are also drawing the path, depending how the path is drawn, the apex will also be when the tangent to the path is a horizontal line, not sure if that information could be used to approximate the apex. |
@arouinfar how does that look? A green dot represents the apex. It's calculated by doing a linear regression between two dots where the y velocity crosses over zero. |
@andrea-phet It definitely passes the "eye-ball" test...Trying a bunch of conditions quickly the green dot seemed to visually be right at the apex. I will let @arouinfar make the call, but looking good to me. |
Since @arouinfar is on vacation, since this looks good, closing |
In #130, the timing dots were changed to 0.1 s intervals. One downside is that it'll be less likely to have a dot at (or very near) the apex. One possibility would be to add a marker at the apex. The marker would be visually distinct from the timing dots.
@andrea-phet does the current model allow you to easily find the apex of the path?
The text was updated successfully, but these errors were encountered: