Again we have an error-prone workflow here: When a model contains an experiment() annotation, this annotation is read each time when we switch to the simulation tab. On the one hand, this is desirable behavior since changes in the annotation are reflected in the settings of the tool. On the other hand, when the user does want to change the settings manually, they may want to go back to the model, change some other parameters, and then will not expect that their changes to, e.g. stepSize have disappeared.
I see two possible solutions to this problem:
- Deactivate the UI-elements for experiment parameters that have been read from the model file.
- Only read the parameters from file the first time the simulation tab is brought up in a session. Afterwards, respect the choices made by the user in the UI elements.
I think I prefer option 1, but a case for 2 can also be made.