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

Question on requirement for variableNamingConvention to be set to structured #70

Open
PhRosenberger opened this issue Jun 16, 2021 · 2 comments
Assignees
Labels
question General questions about the standard, work-flow and code.

Comments

@PhRosenberger
Copy link
Contributor

Describe the problem

We experienced that the line in the doc:

  • The variable naming convention of the FMU MUST be structured.

Does not hold for usage of the FMU with MATLAB Simulink, as there is the requirement to set it to flat to get it connected to other Simulink blocks.
Can we chage this requirement on the OSMP doc?
Where did it actually come from?

@PhRosenberger PhRosenberger added the question General questions about the standard, work-flow and code. label Jun 16, 2021
@pmai
Copy link
Contributor

pmai commented Jun 16, 2021

Hmmm, I have never seen a problem in Simulink with structured naming convention; can you be more specific?

The reason that structured naming convention is required (from the beginning) is that we use it in the OSMP names, and hence structured naming convention ensures that no conflicting names are generated (in flat anything more or less goes, structured is the naming convention that assigns meaning to . and [], etc.).

@PhRosenberger
Copy link
Contributor Author

So, I tried to get the FMU connected, when structured naming convention is selected.
Unfortunately, I could not manage to get the BUS input connected in Simulink that appears in this case instead of three signal inputs.
MATLAB-Docu doesn't help at all in this case.

@pmai do you guys have experience with that?
So far, I will stick to flat naming convention, as it works :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question General questions about the standard, work-flow and code.
Projects
None yet
Development

No branches or pull requests

2 participants