Closed KatieWoe closed 4 years ago
There have been a number of issues like this. Extremely rare, and difficult or impossible to create locally. Energy Skate Park: Basics was developed before we had fuzz testing or CT. In prior issues, @jessegreenberg and I worked together to add information to the assertion messages to help us work backwards to see what is happening, but these are difficult issues to investigate. Some ideas for proceeding:
?fuzz
is enabled. For a particular class of problems in PhET-iO, that was the appropriate solution.@ariel-phet what do you recommend for this issue and others like it?
@samreid I would like to discuss a bit at dev meeting to get a better perspective. I am leaning towards your second suggestion
Shut off assertions like this when ?fuzz is enabled. For a particular class of problems in PhET-iO, that was the appropriate solution.
But want to make sure there is consensus.
Here is the original issue with notes about work done for this so far: https://github.com/phetsims/energy-skate-park/issues/45
I'm not in favor of turning off assertions when ?fuzz is enabled, or any other "solution" that hides errors. It's better to live with errors than to hide them, and address them when we have time. If we can't find time, then there is a bigger problem than the errors.
After discussion @ariel-phet said, after GQIO and diffraction, can investigate ESP CT fails with @jessegreenberg for 1/2 day to a day.
@jonathanolson recommended recording the sim so that we have the reproducible events that lead to this issue.
Unassigning, we are pursuing solutions in https://github.com/phetsims/energy-skate-park/issues/45
@jessegreenberg can this issue be closed? Are all of the concrete problems noted in other issues?
Yes this can be closed. This assertion in particular has a proposed fix and is being tracked in #45.