You need to generate the FMU on the same platform as you are running SystemModeler, so if you use SystemModeler on macOS you need to export the FMU on macOS as well.

Otto

Thank you. This allows the full power of Mathematica to be easily applied to a external simulation.

I had assumed that the model would need to exist in SM, but almost all the functionally exist with just the imported .mat data file. I have never seen that advertised anywhere.

This has saved me hours.

Thanks again.

Good morning.

The saving of the line settings does help in a minor way. What I have ended up doing is just pulling the data to Mathematica where I can have width, dashing, filling, colour all saved. It works, but is two steps. In future SM, it would be great if something similar were possible. For example, being able to save a preset for a plot to meet a certain publication standard (colours, Labels, width, etc) would be great. For now, Sm-> Mathematica works.

For now, working with Modelica Fluids, I do this: - design and edit in SM - to OMEdit for final edit and running the model - .mat to SM MC for an easy import/conversion to .csv - Import[] to Mathematica then to post-processing and plots .

Eventually I will parse the .Mat directly in Mathematic. It works, but painful.

Again, thanks for the help.

Thanks for the help.

Thank you for that bit of knowledge - the MDI vs TDI displays. That goes a long way as it saves the plots. When working one type of model, it is helpful to see a parametric and a group y-time plots. - so for my mechanical models (rotational...), this is much better - being OMEdit, yet for Fluids... perhaps SM13.

On a side question, is it possible to save the plot settings - ie, the shading and line width, axis labels. While one can save the plot data selection, plot improvements beyond that do not save (at least with the knowledge I have).

Thanks for the help.

Hi,

I have tried Fluid models in SM. For a long time did try building models in SM, yet past the basic editing, there were always errors that I believe had to do with the Flow connectors. I built the same models in OMEdit and they run. With those working models, I then try them in SM, but no luck. The models are not complicated: a sink and source (ideal gas), two valves, and a volumetric compressor. Even using only standard Modelica 3.2.3 elements, it does not work. I tried with with SM12 and SM12.1. Often they seem ok in SM yet fail in compiling in MC or fail the run.

This is unfortunate since the SM environment is much nicer to work in and the integration with Mathematica is great. Yet I must say that OMEdit is getting much better and has several advantages over SM: - being able to arrange and move plots around - while SM has a nice presentation, they are a fixed stack order, meaning if you want to change this, you must rebuild the work (yet OMEdit doesn't save plot settings, so each has its own issues)

- Optimaztion is much better in OMEdit: 
    1) It is easier to do parameter sweeps in OMEdit and appears to be faster than the SM->Mathematic path
   2) The OMOtim package of OMEdit allows system optimisation of the system - it is much faster than the parametric optimisation of SM->M.

I do have great hope for SM13 with learning all the tricks of OMEdit and of course Fluids.

For now I am working OMEdit for my fluid projects an then -> .xls -> Mathematica for post-processing.

• perhaps more than you asked, but for thought.

Hi Otto,

Thank you for the help. In the longer term I will get OMEdit on my Mac side as it seems the solution. Yet due to some complexities (having openFoam CFD on my Mac side), the installation is problematic. I think I found a work around in the Windows environment.

I realise this is likely not for public consumption, but does it look like System Modeller might support fully Fluids in the next version - Spring 2021? I do have my hopes.

Chris

Hi Otto,

I just want to confirm that both of these (System Modeller, OMEdit) running on one OS, namely Windows 10, that the FMU 32bit vs. 64bit is solved. I will have to purchase an additional Wolfram license and don't want to do so unless this is a path forward.

With this I will create Fluids models in SM for ease of editing and such, then move the .mo to OMEdit, create the run it, edit as required, then export the working model to FMU. Then open in SM on Windows.
- from what I understand of what you are saying this should work?

I then plan to call is as a model in Mathematica for optimisation and data work. Do you foresee this as also requiring a Windows version of Mathematica?

Thanks for the help.

Chris