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

Fix Clocks/FMI3.xml and validate in CI #93

Merged
merged 4 commits into from
Apr 20, 2021

Conversation

t-sommer
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@KarlWernersson KarlWernersson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Several comment but only initialUnknowns must be fixed

Clocks/FMI3.xml Outdated
<InitialUnknown valueReference="2001"/>
<InitialUnknown valueReference="2002"/>
<InitialUnknown valueReference="2003"/>
<InitialUnknown valueReference="1005"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<InitialUnknown valueReference="1005"/> should not be there.
Clocks should not be in initalUnknonws.

<Clock name="inClock3" valueReference="1003" start="0" causality="input" interval="countdown" priority="2"/>
<Clock name="outClock" valueReference="1005" causality="output" interval="triggered" priority="2" clocks="1001 1002 1003"/>
<Int32 name="inClock1Ticks" valueReference="2001" causality="output" clocks="1001"/>
<Int32 name="inClock2Ticks" valueReference="2002" causality="output" clocks="1002"/>
<Int32 name="inClock3Ticks" valueReference="2003" causality="output"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it intentional that inClock3Ticks does not belong to a clock?

<Clock name="outClock" valueReference="1005" causality="output" interval="triggered" priority="2"/>
<Int32 name="inClock1Ticks" valueReference="2001" causality="output"/>
<Int32 name="inClock2Ticks" valueReference="2002" causality="output"/>
<Clock name="inClock1" valueReference="1001" start="0" causality="input" interval="constant" intervalDecimal="1.0" priority="0"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think start values for clocks are pointless and confusing. But it is correct according to the current standard.
I will open a sperate ticket about it

@t-sommer t-sommer requested a review from KarlWernersson April 20, 2021 08:59
@t-sommer t-sommer merged commit 0c71b88 into modelica:master Apr 20, 2021
@t-sommer t-sommer deleted the fix-clocks-xml branch April 20, 2021 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants