EMSO Language Changes Suggestions

ext keyword for global parameters

Currently the ext keyword is used to obtain a global parameter. I've observed that this keyword is not well suited for its meaning.

The idea from ​http://www.modelica.org is to have outer parameters, which means a parameter from one of the parents. Then the simulator will look for the parameter in the parent tree until it finds it (maybe it is found only on the FlowSheet? but it can be matched before).

Usage example:

Error: Failed to load processor mso

No macro or processor named 'mso' found

Then when feed is instantiated on the FlowSheet? feed.NComp will be a reference for NComp on the FlowSheet?. But if the stream is used in a model this model can have a NComp parameter and this will be referenced.

Who	Opinion	Why
Rafael	agreed	proposed the change
Paula	agreed	because this change gives more flexibility to the user

CalcObject's

This is another example of keyword which is not directly understood by the users. I suggest to use just Plugin instead of CalcObject.

Usage:

Error: Failed to load processor mso

No macro or processor named 'mso' found

Another problem with the Plugin's is that each Plugin call (e.g. PP.LiquidEnthalpy?(T, P, z)) generates a units of measurement warning. In order to solve this problem I suggest the specification of the File attribute even for outer Plugins (as exemplified above). Then the simulator can check the units of measurement and number of arguments when checking the model and not only when the simulation is run.

Who	Opinion	Why
Rafael	agreed	proposed the change
Paula	agreed	because the warnings about unit checked in models cause a bad impression

Repository Directory Layout

This is not exactly a change on the language, but in order to support a change on the language we will need a branch on the models repository.

Usually, SVN repositories follow the layout:

• trunk (the main development)
• branches (the branches for parallel development with the trunk)
  • branch1
  • branch2
  • etc

In order to implement this change we could just rename the mso directory on the repository to trunk and create another top folder called branches.

Who	Opinion	Why
Rafael	agreed	proposed the change

Model Attributes

Currently only types have attributes, examples:

Error: Failed to load processor mso

No macro or processor named 'mso' found

In the above type declarations, Brief, Lower, etc are attributes. We are planning to add attributes also for Models and we need to define a syntax for their declaration.

Option 1

Something similar to the types declaration:

Error: Failed to load processor mso

No macro or processor named 'mso' found

Option 2

A new section for setting the attributes:

Error: Failed to load processor mso

No macro or processor named 'mso' found

Option 3

Leave the attributes handling to the graphical interface (as gPROMS does), then:

• Models remain as they are today
• The user edits graphically:
  • which models appear on the pallet
  • the documentation of the model (probably with a graphical editor with support for bold, italics, lists, etc
  • which variables should appear on results
  • which variables can be specified or not (this can be even refined supporting specification sets)
  • which is the icon for the model
  • the relative position where the ports are shown

All the information configured graphically by the user can be stored in a XML file on the same folder of the models.

Who	Opinion	Why
Rafael	option 3	With option 3 we have a clear distinction between the graphical interface and the models