Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception: Simulation terminated with error after successful simulation #472

Closed
bresait opened this issue Feb 22, 2022 · 1 comment · Fixed by #473
Closed

Exception: Simulation terminated with error after successful simulation #472

bresait opened this issue Feb 22, 2022 · 1 comment · Fixed by #473

Comments

@bresait
Copy link

bresait commented Feb 22, 2022

Hey,
Using buildingspy v3.0.0, I am getting the following exception after an apparently successful simulation.

*** Error: Log file contained the line ' = false'
*** Error: Simulation failed in '.'
   Exception: Simulation terminated with error. Check .\simulator.log..

Simulator.log contains the following:

RunScript("c:/program files/dymola 2021/insert/dymola.mos", true);
 = true
Successfully loaded settings file C:/Users/xxx/AppData/Roaming/DassaultSystemes/Dymola/2021/setup.dymx
RunScript(".\\run.mos");

// File autogenerated by _get_dymola_commands
// Do not edit.
//cd(".");
openModel("Modelica\package.mo", changeDirectory=false);
 = false
Modelica.Utilities.Files.remove("simulator.log");
OutputCPUtime:=true;
modelInstance="Modelica.Blocks.Examples.PID_Controller()";
Declaring variable: String modelInstance ;

simulateModel(modelInstance, startTime=0, stopTime=3.2, method="dassl", tolerance=1e-06, resultFile="PID_Controller", numberOfIntervals=100);
 = true
savelog("simulator.log");

I am under the impression that the error is raised because of the ' = false' in

openModel("Modelica\package.mo", changeDirectory=false);
 = false

which I am not sure how to understand.
The simulation runs without any error (as also checked with showGUI(show=True) and produces fresh .mat results.
Is this expected behaviour?

@mwetter
Copy link
Member

mwetter commented Feb 24, 2022

Thanks for reporting. This will be corrected through #473

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants