arun3688

@AnHeuermann > The `getSolutions` function behaves very different when setting input `name=nothing`. It's not returning solutions but a list of all variables in the result file. > I would expect...

As you see in the paper returning the results in `Vector{Float64}` makes it easy for plotting tools, off course there are some other plotting tools which accepts data frame.

Also i am currently working on julia wrapper functions for OpenModelica Scripting API, where we can have most of the settings available, I am trying to write some automation script...

@casella I did a quick test and found that OMEdit is creating directory with fully qualified path for example `C:/Users/DEMO/AppData/Local/Temp/OpenModelica/OMEdit/Modelica.Fluid.Examples.HeatExchanger.HeatExchangerSimulation` Instead of fully qualified path we can simply use the...

> However, we could _build_ the FMU in a temporary directory with a short path name, and then just copy the FMU to the fully qualified pathname when the building...

@casella After some discussion with Adeel we now have some short path and we hope it should fix most of the cases, and now we should surely get rid of...

@casella that is true having `tmp4de3` is much better because there is nothing to debug in the temp directory and users are only interested in generated fmu, We will see...

@deepak19015 @casella I tried to export the FMU `Buildings.Examples.VAVReheat.ASHRAE2006` both in OMEdit and mos script, And it worked for me, see below screenshot  But one issue is OMEdit does...

@casella Yes i am on windows, and even in windows OMEdit is freezed until the fmu is generated, But from command line it should work fine even in linux

@deepak19015 I tested the some models you posted above and the fmus are generated correctly through command line (mos script), but it took `19 minutes ` to generate a fmu...