Custom Query (5234 matches)

OMEdit on startup (at least on Linux) shows a dialog asking the user to either load the Modelica standard library version 3.2.3 or 4.0.0, regardless of whether the MSL 4.0 has been installed through the package manger or not.

If the user selects MSL 4.0, then OMEdit complains it can't find it. Closing and reopening OMedit no longer opens any dialog, and the user is left with an OMEdit that keeps failing to load the MSL 4.0 and can't use the MSL.

I could fix it by manually installing the MSL 4.0, but less knowledgeable users may not fix it so easily.

Hello I'm using the scripting API of OpenModelica. I want to compile a FMU to a specific directory. I think in the moment it is not possible.

function translateModelFMU
  input TypeName className "the class that should translated";
  input String version = "2.0" "FMU version, 1.0 or 2.0.";
  input String fmuType = "me" "FMU type, me (model exchange), cs (co-simulation), me_cs (both model exchange and co-simulation)";
  input String fileNamePrefix = "<default>" "fileNamePrefix. <default> = \"className\"";
  input Boolean includeResources = false "include Modelica based resources via loadResource or not";
  output String generatedFileName "Returns the full path of the generated FMU.";
end translateModelFMU;

right?

This is a feature request, resulting as a conclusion of the non-working models of my students that I had to investigate over the last years.

Whenever the connections of a graphical model in Modelica looks OK but the connections are not OK, it is very hard to identify the underlying problem. Typical issues in electrical circuits are:

• Shortening the two pins the current path of (a) a current or (b) a power sensor (see attachment Example1: wrong connect(currentSensor.p, currentSensor.n))
• Instead of connecting the two connectors of a component, the connections are made to the same one connector of the component (see attachment Example1: connect(ground.p, resistor.p) instead of connect(ground.p, resistor.n))

Such issues can usually not be identified in the diagram layer, as the wrong connections interfere with the icon. Depending on the complexity of the model, is more less time consuming to identify such issues in OpenModelica.

In order to trace such issue a button like "Check connections" could be introduced. This could for example trigger some simple checks:

• List the not connected connectors (possibly output connectors could be excluded from the list)
• Highlight the connection with bold line width (and shade and flashing or whatever) in the foreground so that the icons are in the background and each connection can be checked thoroughly