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

Add phet-io state handling for the classical and quantum coins #42

Open
jbphet opened this issue Sep 27, 2024 · 3 comments
Open

Add phet-io state handling for the classical and quantum coins #42

jbphet opened this issue Sep 27, 2024 · 3 comments
Assignees

Comments

@jbphet
Copy link
Collaborator

jbphet commented Sep 27, 2024

Setting and conveying state for classical and quantum coins is not yet working, and it's time to add it. This issue will track that work.

@jbphet
Copy link
Collaborator Author

jbphet commented Oct 23, 2024

This functionality has been added and appears to be working correctly at this point, though there hasn't been a ton of testing on it. It supports the differences between classical and quantum systems the way that was discussed in the design meetings. Briefly, this was that when a classical system is prepared but hidden and state is set, making an observation will yield the same results in both the upstream and downstream sims. When a quantum system is prepared, the states are not determined until the actual observation is made.

The state setting behavior is working in this dev version in case we ever need to reference it: https://phet-dev.colorado.edu/html/quantum-measurement/1.0.0-dev.6/phet-io/

Closing.

@jbphet jbphet closed this as completed Oct 23, 2024
@phet-dev phet-dev reopened this Nov 5, 2024
@phet-dev
Copy link
Contributor

phet-dev commented Nov 5, 2024

Reopening because there is a TODO marked for this issue.

@jbphet
Copy link
Collaborator Author

jbphet commented Nov 5, 2024

This was automatically reopened because of a TODO that I'd added related to having to use "as never" type directives. I guess I'll leave it open and look at this more deeply at some point in the future if the problem still exists.

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

2 participants