You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
#79 dramatically worsened simulation times and causes large simulation errors #80
I remember you said that if you have and output-interval as non integer that it would get stuck, maybe this is what it happens and the timeout just forces to finish (correctly).
But then how comes we still get the verification right? Could it be that it is still using the previously computed result file? If so, then you should probably update the test script to delete all such file before starting the new simulation.
But then how comes we still get the verification right? Could it be that it is still using the previously computed result file? If so, then you should probably update the test script to delete all such file before starting the new simulation.
We always delete the previous results so that's not the case.
It is possible that the simulation is finished in way less time that 50 but is stuck, so the result files are correct when is killed.
One more piece of info: many of those models timing out fail on verification with really weird results, e.g.:
Something's really weird going on there. @adrpo, how can we debug this? Can you try to run the same fmpy command line on your computer and see what the result is?
changed the title [-]#79 dramatically worsened simulation times[/-][+]#79 dramatically worsened simulation times and causes large simulation errors[/+]on Mar 30, 2024
Activity
casella commentedon Mar 20, 2024
The 50 s timeout likely plays some role, but we still get successful simulation and verification, so it's not failing. Not sure what is going on.
adrpo commentedon Mar 20, 2024
I remember you said that if you have and output-interval as non integer that it would get stuck, maybe this is what it happens and the timeout just forces to finish (correctly).
casella commentedon Mar 22, 2024
Yes, that could be, see CATIA-Systems/FMPy#655.
But then how comes we still get the verification right? Could it be that it is still using the previously computed result file? If so, then you should probably update the test script to delete all such file before starting the new simulation.
adrpo commentedon Mar 26, 2024
We always delete the previous results so that's not the case.
It is possible that the simulation is finished in way less time that 50 but is stuck, so the result files are correct when is killed.
casella commentedon Mar 27, 2024
OK. Any clue what is actually going on there?
casella commentedon Mar 30, 2024
One more piece of info: many of those models timing out fail on verification with really weird results, e.g.:
Something's really weird going on there. @adrpo, how can we debug this? Can you try to run the same fmpy command line on your computer and see what the result is?
[-]#79 dramatically worsened simulation times[/-][+]#79 dramatically worsened simulation times and causes large simulation errors[/+]