-
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
Create a Wave Interference variant where each screen is a different wave type #356
Comments
Is this supposed to be based on the "waves" screen of Wave Interference, with neither slits nor multiple source? |
@samreid there hasn't been any design work beyond the one brainstorming meeting. The sim would only include the Waves screen of Wave Interference. Instead of three scenes (one for each wave type), we would have three screens -- Water, Sound, and Light. I would say a first pass at implementation would be to split the Waves screen into these three separate screens, but we would really need to have more design discussions before taking things any further. |
In the preceding commit, I created a rough draft for the simulation, you can see it on phettest at: I'll create issues for some follow-up work/questions. |
The main work is done, I noted 2 issues above. Reassigning to @arouinfar for other feedback on this rough draft. |
Thanks @samreid! Could you publish this as a dev version instead? The VPN is super sluggish here. |
I'm happy to create a new dev version, but suffering from the problem described in https://github.com/phetsims/special-ops/issues/133, so cannot easily create dev versions at the moment. I'll keep you posted. |
Here's an initial dev version: @arouinfar anything else for this issue? |
Don't think so! I'll go ahead and close, thanks. |
From my notes from Thursday's status meeting:
This idea is also mentioned in the design meeting notes from February 19, 2019.
I'd like to finalize the sim name before creating the repo. But I can start prototyping it in the wave-interference repo (perhaps with query parameters) before we create the repo.
The text was updated successfully, but these errors were encountered: