Hi Clarisse,
true, such initial mismatch between versions may occur when a model uses a sequence of interdependent expressions for initialization of model components or when Systems and Events are defined without a user-specified timestep. Depending on the capabilities of the (adaptive) solvers in the respective Morpheus version, these specific models may get executed with differently optimized timesteps and that may result in different solutions. The solvers always report their chosen timestep both in the GUI/Description/ModelGraph (the yellow boxes with numbers under each dynamics element) as well as in the simulation output's model.xml.out file in a section
...
======================================================
Time Schedule
======================================================
...
When migrating a model between Morpheus versions, then the two respective Time Schedules should be compared and if needed, then the timestep attributes can be reset manually. If the Time Schedule by a newer Morpheus version differs from an older version then this had the aim of faster overall runtime using the added solver capabilities.
We are also happy to assist if you need help.
Best,
Lutz