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 about output clocks with HighCut #199

Open
Tc-Muent opened this issue Oct 22, 2024 · 1 comment
Open

Question about output clocks with HighCut #199

Tc-Muent opened this issue Oct 22, 2024 · 1 comment
Assignees

Comments

@Tc-Muent
Copy link

Hello
I have a question regarding the clocks in the high cut.
In the ls bus it says that the output clocks should be periodic or aperiodic.

"The output Clock type, periodic or aperiodic, is defined by the sending FMU. This allows the FMU (or better the exporting tool) to balance the accuracy and performance of its network communication:" [4.2.2. Clock Variables]

This means that they are timebased. But according to the FMI 3 standard, only triggered clocks can be output clocks. See FMI 3 standard [2.2.8.2. Clock Types] . Or am I misunderstanding something in relation to the clocks at Hig Cut?

Thank you very much.

@chrbertsch
Copy link
Collaborator

Pierre: the FMI standard refers to "input" and "output" w.r.t. who does the clock ticking, not w.r.t the information flow
Markus: Can we change "output" to Tx?
Klaus: for high cut we do not have "Tx".
Pierre: We need to have some good name for it in the text. I can try to make a proposal
(Klaus: we have some "implicitely introduced" terms, such as "sending FMU".)

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

No branches or pull requests

3 participants