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

Remove causalities "inferred" and "triggered" #617

Open
t-sommer opened this issue Sep 12, 2019 · 3 comments

Comments

@t-sommer
Copy link
Collaborator

commented Sep 12, 2019

and use "input" and "output" instead for variables of type "Clock" (as discussed at the Clocks & Hybrid CS Face-2-Face meeting 12-09-2019)

@chrbertsch

This comment has been minimized.

Copy link
Collaborator

commented Sep 20, 2019

Regular design meeting:
Andreas P: Let's do this naming discussion after the merging.
Klaus: "inferred" is used in Modelica?
Andreas P: right; some expert in ME should comment on this
Klaus: In Modelica: language is acausal, do not use inputs and outputs for clocks. In FMI we should use inputs and outputs.
Andreas P: We should discuss this at the design meeting

Torsten S.: Related question: fmi3Clock type is not used in the set/get functions
Andreas P: this was a mistake
Torsten S: I will open an issue

@chrbertsch chrbertsch added the Lund2019 label Sep 20, 2019
@t-sommer

This comment has been minimized.

Copy link
Collaborator Author

commented Oct 1, 2019

@HansOlsson, what's your opinion on this?

@HansOlsson

This comment has been minimized.

Copy link

commented Oct 1, 2019

@HansOlsson, what's your opinion on this?

I think this should be ok. I could see two cases for "output" a periodic clock that has parameters that specify it that are known for the importer, and one that is just internally generated in an unspecified way. I don't know if we should separate them.

t-sommer added a commit to t-sommer/fmi-standard that referenced this issue Oct 1, 2019
and use "input" and "output" for clocks

see modelica#617
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.