FinalState Operating Points Generated by Parallel Pool

I'm running a model on a set of parallel workers (MDCS) and I'd like to use the FinalState operating points from these runs to as the InitialStates for second set of simulations. My code runs fine when I'm not using the parallel pool (run a single simulation, use its FinalState as the InitialState for the second run), however when the first set is run on the parallel pool, I get an error saying that the model was changed after the operating point was saved. The only change I'm making between parallel runs is to assign the InitialState to the SimulationInput parameter for the second set.

Answer 1

[Ayush]

Hi @Peter Carow

I understand that you are get an error saying that the model was changed after the operating point was saved when using parallel pool. The error has been fixed in R2020b Release, you can use parsim to simulate the multiple system in parallel. You may refer to this documentation to read about parsim: https://www.mathworks.com/help/simulink/slref/parsim.html.

If you are facing issues in R2020b release kindly attach your model for further assistance.

Thanks,

Ayush

[Peter Carow]

Hi @Ayush, thanks for the reply. I did some additional testing and I still have a problem, albeit a slightly different one. I found that my initial problem was due to the fact that I was generating the FinalState output using parsim, and then trying to run a single, non-parallel run using a parsim-generated FinalState as InitialState, which I think violates the constraint that the two runs must be simulated in the same mode.

I ran a set of simulations using parsim and each run generated a FinalState model operating point. I then attempted to initialize a second set of simulations to be run using parsim, and this time assigned the InitialState for each simulation input object to be the FinalState from the corresponding previous run. I then kicked off the second set of simulations using parsim, however it appears that the InitialState is being ignored and the second batch of simulations is starting from the same point as the first batch.

I'm running in 2022b, by the way

[Ayush]

could you please attach your code here?