•SIMULATE>LINEARIZE sets a flag to direct the following ordinary simulation to generate linearization output.
•SIMULATE>LIN_HEART sets a flag to run Heart of the Systemâ„¢
•SIMULATE>LIN_INTEL sets a flag to run eigenvalue analysis and other metrics falling under VenTelligenceâ„¢
•SIMULATE>LIN_CREATE_FILES|0 or |1 controls whether the results are also written to tab-delimited sidecar files beside the run. One switch for all of the above; it is on for a new model, and a model saved before the setting existed has it off. Without it the results are kept in the run for the loop tools to read, which is no use to a command script.
The frequency of these operations can be controlled with the LINEAR_ special variables.
These run on an ordinary single simulation only. An optimization, a sensitivity run, a game, a Reality Check and SyntheSim all skip them. Each of those simulates the model many times, so the analysis would describe a trajectory you did not ask about and be overwritten by the next one, while every simulation paid the cost of producing it.
To analyse the result of an optimization, run an ordinary simulation with the optimizer's .out file as a changes file. That sets the model to the optimum and gives you the analysis of it. The same approach works for any one case out of a sensitivity ensemble.