-
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
User suggestion: vector values #151
Comments
My physics teacher uses the sim for her classes and she would really love to see this addition! |
@andrea-phet @arouinfar perhaps on the vectors screen we could put a tool the looks/behaves just like the trace tool but has a different background color and Gives V_tot V_x and V_y for each point? My thought would be to remove the measuring tape on that screen and replace it with this tool (I think if you have "measuring tape learning goals" they could be gotten to on the other screens) and I would worry that we want to keep the play area as open as possible. @andrea-phet - I assume that much like Time, Height, and Range, the velocity and components could be recorded for each point? |
Yes, velocity can be recorded. (In fact, it already is recorded just like time, height, etc., and just needs to be accessed). |
I really like this idea @ariel-phet! The velocity trace tool would be useful beyond the goals of the Vectors screen, though. I think measuring V_x would be more useful on the Drag screen than the tape measure. So perhaps the tape measure could be on the Intro screen only? In the meeting notes for 2/9/2017 we discussed the possibility of a vectors trace tool to show the vectors along the path and a snapshot tool to allow students to allow students to simultaneously compare the vectors at different locations on the path. We decided that these tools, while useful, were beyond the scope of 1.0. Not sure if this is too much feature creep, but perhaps we could include some of this functionality in the velocity trace tool. Since it sounds like the velocity is being already being recorded at each point, perhaps we could draw the velocity vectors at point being measured. We could also consider having two vector trace tools in the toolbox to allow simultaneous comparisons. Here's a rough mockup showing the velocity trace tool in action (color and labels TBD). |
@arouinfar I personally think I would just have the velocity trace tool only show values. For one, things will get a bit messy with the tool when the vectors overlap the tool. I also think the learning goals around the values don't necessarily need to show the vectors. To me the dynamic vector representation, and the ability to use the "step" as we already have it is much more compelling for the comparison of vectors at different points along the trajectory. Seems like worth a quick discussion at design meeting with @kathy-phet |
@ariel-phet I'd be find with only showing the values. I had remembered some discussion of features for 1.1+, and thought those features could possibly piggyback on the vector trace tool.
Great point. Moving the probe to the right side of the tool will minimize vector overlap with the tool, but then becomes unusable for the first few points along the trajectory.
While pause/step is powerful, it doesn't really facilitate simultaneous comparison of vectors along the trajectory. One could fire multiple projectiles at once (that's how I got two sets of vectors in the image above), but it doesn't really allow the user much control.
Agreed! Unassigning myself for now. |
When we discussed this feature last fall, there was some concern about such a tool giving away too much information. However, I think we may still want to consider some sort of velocity tool when this sim gets revisited. By then, we may have also had more teacher requests. |
Tagging @arouinfar because there is work being done in this sim again. Let me know if you want this implemented. |
@arouinfar I remember discussing this during design, but I forget what conclusion we came to. I thought that we at least decided that the above tool was not going to be created for the coming version. Is that right? |
@zepumph the decision was that we were not going to add this feature to Projectile Motion, and the issue can be closed. |
A similar request was made in #227
|
Another similar request received into phethelp:
|
Since there continue to be user requests about this feature, I'm reopening the issue so we can consider it during the next release. |
The text was updated successfully, but these errors were encountered: