Allow step-by-step translation and simulation with scripting API

[robert.sandmann@…]

Dear developers,

currently, it is not possible to simulate a model without translating it at the same time. That means that if a translated model is available in the working directory, a call to simulate translates the model again.

To be able to compare timing statistics of the separate steps check, translate and simulate, it would be great to be able to only simulate a model without translating it at the same time using the scripting API (also via the Python interface).

I thank you in advance for looking into this.

Kind regards, Robert

[massimo ceraolo]

Maybe to solve your problem you just need ticket #4565 be fixed?
The solution of that ticket indeed would give users a lot of information on where computing time goes.

[Andreas Heuermann]

I'm not sure if this solves your issue but you can use API function OpenModelica.Scripting.system to call your executable directly. See also the ​API-documentation
So for simulating a model bouncingBall.mo you could do something like this mos-Script

// Load your Modelica model
loadFile("bouncingBall.mo"); getErrorString();

// Get time informations for build process
setCommandLineOptions("-d=execstat"); getErrorString();

// Check and translate and build model
buildModel(bouncingBall); getErrorString();

// Simulate model
// with some example flags
system(realpath(".") + "/bouncingBall -lv=LOG_INIT,LOG_STATS_V -override stopTime=2.0", "bouncingBall.log"); getErrorString();

On Linux systems you don't need to save the output to some log file, but on Windows you do and then can read the file with OpenModelica.Scripting.readFile.

[Martin Sjölund]

You can also do translateModel, which will not compile the code. Or use execstat in the scripting API to get timing (or access the timers directly like the library testing scripts do).