-
Notifications
You must be signed in to change notification settings - Fork 3
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
Presentation of equations in Studio and the data stream #202
Comments
We talked about this issue today (the fact that each equation has to be personally laid out by the developer). We brought up Latex, which includes a math equation parser, that's not currently in any of the sims. Being new, I'm unclear whether building in Latex is either wanted or possible. |
This is a little different than how the equations are rendered, and certainly smaller in scope. I was thinking we might want a Property for each equation, whose value is a plaintext string. For the examples in the above screenshots: "3x > 2" But I'm not sure if those would really be useful, whether they would need to be parsable by wrappers/programs, etc. |
Discussed 11/8/22: Decision is to use a text string that a program could parse. This is closer to what the model knows, is human-readable, and is parsable by a program. Examples: "1 cat + 2 dog + 3 turtle > 0 cat + 1 dog + 0 turtle" "1/10 x + 3/10 = 2/10 x + -5/10" |
More notes from 11/8/22 design meeting:
|
Equality Explorer is not currently a publication priority, and it's unclear who will be continuing with PhET-iO instrumentation. So unassigning. |
This sim displays equations in a number of places. There is one or more equations above the balance scale, and zero or more equations in the Snapshots accordion box. Examples:
There is currently nothing in Studio or the data strem that presents these equations in a human-readble format, or even a format that is easily parsed by a program. Is something like that needed? If so, what is the desired format? Where should it appear in the Studio tree?
The text was updated successfully, but these errors were encountered: