Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

matchingRule of terminals #771

friedrichatgc opened this issue Feb 19, 2020 · 1 comment

matchingRule of terminals #771

friedrichatgc opened this issue Feb 19, 2020 · 1 comment


Copy link

@friedrichatgc friedrichatgc commented Feb 19, 2020

The matchingRule of terminals defines the rules how the member variables inside of a terminal are matched. The according table in the document gives precise information about these rules.
However, later on the document states

Tools which apply sequence based matching should also provide unique member names, so that all importing tools which use name based matching use the same member names.

What is the matchingRule: a definition how the matching must be done or is it just a recommendation and everyone is free do do something else (which may not be the intend of the exporter who defined the matchingRule)

@t-sommer t-sommer added this to the v3.0 milestone Feb 21, 2020

This comment has been minimized.

Copy link

@CSchulzeTLK CSchulzeTLK commented Apr 1, 2020

There is the mentioned table with basic matchingRules. Others might be added by other standards. They are described in normative text.

This sentence you're citing was added to avoid that sequence based tools export FMUs without member name (so we finally made this attribute mandatory), and that these tools provide the same member name for several variables (so we made the member name unique). Both has been described in other places. So this is merely an information for the sequence based tool FMU exporters, that tools use these names for member variable matching. Maybe we can adapt the formulation to make this clear. Maybe remove.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.