Opened 10 years ago

Closed 7 years ago

#3125 closed defect (worksforme)

Modelica.Media.Air.MoistAir.PsychrometicData

Reported by: Christoph Höger Owned by: Adrian Pop
Priority: high Milestone:
Component: Frontend Version: trunk
Keywords: Cc:

Description (last modified by Christoph Höger)

I wanted to test my observation (https://trac.modelica.org/Modelica/ticket/1654) that there is some recursion in the MoistAir model and run omc 1.9.1 on it:

$ omc +i=Modelica.Media.Air.MoistAir.PsychrometicData test.mo Modelica
Error processing file: test.mo
Error: Class Modelica.Media.Air.MoistAir.PsychrometicData not found in scope <TOP>.

# Error encountered! Exiting...
# Please check the error message and the flags.

Execution failed!
$ omc +version
1.9.1+dev (r20342) (RML version)

I think this is a bug, regardless of the handling of the recursive element, since at least the error message is totally misleading. However, the omc build status seems to indicate that MoistAir.PsychrometicData is either not used in any simulation or somehow handled by omc.

Change History (4)

comment:1 by Christoph Höger, 10 years ago

Description: modified (diff)

comment:2 by Adrian Pop, 10 years ago

Yes, the error message is wrong.
We can handle some recursion (and there is plenty of it in some of the Modelica libraries, Complex, MultiBody Orientation, etc) but it seems we cannot handle this case. Basically you need some sort of lazy lookup and flattening of package Modelica.Media.Air.MoistAir.

comment:3 by Adrian Pop, 10 years ago

Component: UnknownFrontend
Milestone: 1.9.2Future
Owner: changed from somebody to Adrian Pop
Status: newaccepted

comment:4 by Martin Sjölund, 7 years ago

Milestone: Future
Resolution: worksforme
Status: acceptedclosed

This model was deprecated when MSL 3.2.1 was released, around the time of the ticket (and thus changed location). Also, the model has since then started working although using the command in the ticket will force MSL 3.2.2 to be loaded where the model has a different name. So I will just close the ticket.

Note: See TracTickets for help on using tickets.