This request refers to the three questions:
https://uk.mathworks.com/matlabcentral/answers/1736580-cannot-find-state-n-in-the-given-variable-error-when-trying-to-start-a-simulation-using-previous?s_tid=prof_contriblnk
https://uk.mathworks.com/matlabcentral/answers/182251-simulink-cannot-load-the-initial-simstate?s_tid=srchtitle
https://uk.mathworks.com/matlabcentral/answers/38166-simstate-error?s_tid=srchtitle
In all these examples, users (including me) are struggling because we are trying to use the "Save Operating Point" method.
The "Save Operating Point" method is extremely powerful, and a very useful feature of Simulink that we would like to exploit to its fullest extent.
However, as users find, it is extremely easy to encounter the following error, when trying to run the simulation using the "Saved Operating Point":
"Simulink cannot load the initial SimState because the model, ‘xxxx’, was changed after the SimState was saved. Run the simulation again and resave the SimState.
This is problematic when the model is very large, as the search space (number of subsystems and parameters) is huge. Finding the problem block/parameter is like looking for a needle in a haystack.
Often everything is PERFECT, except for perhaps one single parameterised block that is causing the issue. For the user to find this, without a hint from Simulink about where to start looking, is very difficult.

Simulink must KNOW where the new model is different to that in the saved states, because it is detecting that place and throwing the error.
Please could Simulink then tell the user WHICH block/parameter the problem is with?
Even just the FIRST block/parameter problem would be a help, because often there may be only one.
A link could be provided to the relevant block/parameter, or even just the text listing the block pathname.
Ideally a list of the problem blocks/parameters could be provided, if there are more than one.

Please can this be included in future Simulink versions?This request refers to the three questions:
https://uk.mathworks.com/matlabcentral/answers/1736580-cannot-find-state-n-in-the-given-variable-error-when-trying-to-start-a-simulation-using-previous?s_tid=prof_contriblnk
https://uk.mathworks.com/matlabcentral/answers/182251-simulink-cannot-load-the-initial-simstate?s_tid=srchtitle
https://uk.mathworks.com/matlabcentral/answers/38166-simstate-error?s_tid=srchtitle
In all these examples, users (including me) are struggling because we are trying to use the "Save Operating Point" method.
The "Save Operating Point" method is extremely powerful, and a very useful feature of Simulink that we would like to exploit to its fullest extent.
However, as users find, it is extremely easy to encounter the following error, when trying to run the simulation using the "Saved Operating Point":
"Simulink cannot load the initial SimState because the model, ‘xxxx’, was changed after the SimState was saved. Run the simulation again and resave the SimState.
This is problematic when the model is very large, as the search space (number of subsystems and parameters) is huge. Finding the problem block/parameter is like looking for a needle in a haystack.
Often everything is PERFECT, except for perhaps one single parameterised block that is causing the issue. For the user to find this, without a hint from Simulink about where to start looking, is very difficult.

Simulink must KNOW where the new model is different to that in the saved states, because it is detecting that place and throwing the error.
Please could Simulink then tell the user WHICH block/parameter the problem is with?
Even just the FIRST block/parameter problem would be a help, because often there may be only one.
A link could be provided to the relevant block/parameter, or even just the text listing the block pathname.
Ideally a list of the problem blocks/parameters could be provided, if there are more than one.

Please can this be included in future Simulink versions? This request refers to the three questions:
https://uk.mathworks.com/matlabcentral/answers/1736580-cannot-find-state-n-in-the-given-variable-error-when-trying-to-start-a-simulation-using-previous?s_tid=prof_contriblnk
https://uk.mathworks.com/matlabcentral/answers/182251-simulink-cannot-load-the-initial-simstate?s_tid=srchtitle
https://uk.mathworks.com/matlabcentral/answers/38166-simstate-error?s_tid=srchtitle
In all these examples, users (including me) are struggling because we are trying to use the "Save Operating Point" method.
The "Save Operating Point" method is extremely powerful, and a very useful feature of Simulink that we would like to exploit to its fullest extent.
However, as users find, it is extremely easy to encounter the following error, when trying to run the simulation using the "Saved Operating Point":
"Simulink cannot load the initial SimState because the model, ‘xxxx’, was changed after the SimState was saved. Run the simulation again and resave the SimState.
This is problematic when the model is very large, as the search space (number of subsystems and parameters) is huge. Finding the problem block/parameter is like looking for a needle in a haystack.
Often everything is PERFECT, except for perhaps one single parameterised block that is causing the issue. For the user to find this, without a hint from Simulink about where to start looking, is very difficult.

Simulink must KNOW where the new model is different to that in the saved states, because it is detecting that place and throwing the error.
Please could Simulink then tell the user WHICH block/parameter the problem is with?
Even just the FIRST block/parameter problem would be a help, because often there may be only one.
A link could be provided to the relevant block/parameter, or even just the text listing the block pathname.
Ideally a list of the problem blocks/parameters could be provided, if there are more than one.

Please can this be included in future Simulink versions? operating point, initial simstate MATLAB Answers — New Questions

​