dymola

I am running Modelica simulations with Dymola via the Dymola Python interface. My aim is to have the result file written to textual output (i.e. to a .txt file). Even though my model contains the annotation __Dymola_experimentSetupOutput(textual=true, events=false) , the output is written to a .mat file. Unfortunately, when I type find() into the Dymola command line, I cannot find a suitable flag for setting the output format via dymola.ExecuteCommand() . Is there a possibility to set the output format to textual via the Python interface? Thanks! You can set textual output in the python

I have a custom package that I find myself reusing repeatedly in Dymola models, and I'd like to put this package in a common directory that is automatically loaded whenever I start Dymola. My current strategy is to load the custom package when a model I'm working on is loaded and then save total. This is not elegant because the contents of the custom package end up saved in multiple locations across my hard drive, and if I change one of them, the changes are not reflected everywhere. I would like a more robust way of distributing this custom package to all of my models. Is there a way to tell

I have encountered an issue while trying to simulate a model using an fmu file in Simulink: I am using the Modelon FMI toolbox for a Dymola/Simulink interface to import a Model-Exchange type fmu file (version 1.0) into the Simulink model. I have a Matlab m-file that programmatically simulates the model sequentially, saving the final internal states of the model for initialization in the next simulation. The first iteration of the simulation runs without errors, but on the second iteration, Matlab returns the following errors at the call for the simulation: module = partial_run_sim2/BasicModels

Is there a way to automatically load libraries, change to a certain working directory, etc. when launching Dymola? The question is slightly ambiguous - the other answer is quite good for one scenario. (The openModel call in Step 2 can be modified.) However, if you always want to launch Dymola in a specific directory etc it is possible using the GUI in Dymola 2017 FD01 (and slightly differently from Dymola 2016 FD01): Change Directory (File>Change Directory) Add to Modelica Path (File>Modelica Path) Save those settings (Edit>Options>Settings: Select Startup and Modelica Path) If you want to

This is a companion question to External Functions: Reference headers in C-script to compiled dll . That stack overflow question is using a Modelica external function call to a c-script. That c-script then uses c-functions contained within a .dll. Below is the initial preferred method I had attempted and a working attempt that I do not prefer. Initial Attempt: The following code would not work. My assumption was since I loaded the .dll Library libgsl in Modelica I could then simply use headers in the C-script to use function calls from that .dll. However, the dslog.txt file indicated that it