Opened 6 years ago
Closed 6 years ago
#5259 closed discussion (wontfix)
Portability between OM and Dymola on the delay() operator
Reported by: | Owned by: | Adeel Asghar | |
---|---|---|---|
Priority: | normal | Milestone: | Future |
Component: | OMEdit | Version: | |
Keywords: | Cc: | audrey.jardin@… |
Description
Hello,
Please open under OM the attached file temp.mo and check the model RealTransmission.mo (in Basics.Operators).
An error is detected on the function delay().
Now uncomment the line at the end of the model (y[i]...) and comment the line just above (y(i]...). The check is now correct.
As the first version of the model is correct for Dymola (and perfectly runs also) my suggestion is to do the same with OM for portability reason in spite of the fact the parameter maxDelay is mandatory in the Modelica specification.
Best
Attachments (1)
Change History (2)
by , 6 years ago
comment:1 by , 6 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Sorry, the Modelica specification is very clear, see section 3.7.2
If you want to use OpenModelica, you need to use valid Modelica code.
In this case, you may easily add a parameter delayMax with a default of your choice, rather than leaving this choice to the tool. The code will be valid and will run in both tools.