issue with model operating points: when restarting the simulation it immediately stops because the stopping criteria already met

simulation is stopped using the stop block with logic. Using model operating points to store the simulation state, when restarting the simulation, it immediatelty stops. how to avoid that?

[Daniel]

Without more information on this, I don't think anyone is going to be able to help. What condition is triggering the stop block? Can you share a screenshot showing the logic driving the Stop block?

[Mehreen Khan]

Its a simple logic when the relative error is less than the specified value, stop the simulation. and save the simulation state. and when i restart the simulation it imediately stop because the condition, specified that was already true. what i want to do is change the relative error for continuing the simulation to a better accuracy.

Answer 1

[Daniel]

If you want to pause rather than stopping, you can connect the output of the Relational Operator to a Terminator, and set a breakpoint on the signal. Select the signal, then go to the Debug tab and click "Add Breakpoint". (That's the method for R2023a anyway. I haven't checked on how backwards-compatible that is with earlier versions.)

By the way, you can accomplish your comparison a little more easily with a Relational Operator. Pass "Measured Relative Error" and "Value" into a Relational Operator block, and check the output of that block, rather than using the two or three blocks you're using now.