-
Notifications
You must be signed in to change notification settings - Fork 84
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
Add intro synchronous clocks #1143
Conversation
…o clarify_communication_point_clocks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it - brief intro with problem description and example.
Can we build this example in the Reference FMUs as examples?
Do you think you want to enhance this further and keep it in draft state? |
Good idea. This would also validate the explanation. I've created https://github.com/modelica/fmi-standard/issues/1150 to keep track of this. |
@masoud-najafi , @TorstenBlochwitz : can either of you read through the PR? I would like at least one more person to share the blame ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In 2_2_common_schema.adoc I cannot understand the following phrase, is it related to SE or the TriggeredBy attribute?
If <> = <> and <> = <> the <> tick event can occur only in the model partition that is related to the referenced <>, i.e. the <<outputClock,output clock
>> value (active/inactive) can only change in this model partition.
This sentence is not part of this PR. Can you open another a new issue for this? |
Adds the introductory text described in #1073