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

Confusing rules for clock input/output causality #707

Open
nickbattle opened this issue Jan 14, 2020 · 2 comments
Open

Confusing rules for clock input/output causality #707

nickbattle opened this issue Jan 14, 2020 · 2 comments
Labels
Milestone

Comments

@nickbattle
Copy link
Collaborator

@nickbattle nickbattle commented Jan 14, 2020

The table that defines default initial values in section 2.2.10 has confusing causality columns, with two input/outputs?

The table above it that defines causality types does have two entries for "input" and "output", the second pair of which seem to be to do with clocks specifically. I note the (F) and (G) cases are only for "clock" variability, but why are these not in the same column as the other input/outputs? Ditto for the table defining legal combinations - the (18) case does say that these are clock variables, but I cannot see the significance of the separate columns.

(Note, I am working together with Claudio Gomes and Casper Thule from Aarhus University, who will join the design meeting in the end of February).

@andreas-junghanns

This comment has been minimized.

Copy link
Contributor

@andreas-junghanns andreas-junghanns commented Jan 14, 2020

I am on it for in a different ticket...

@nickbattle

This comment has been minimized.

Copy link
Collaborator Author

@nickbattle nickbattle commented Jan 14, 2020

OK, thanks. I did search for this, but couldn't find an open issue dealing with it.

@chrbertsch chrbertsch added this to the v3.0 milestone Feb 11, 2020
@t-sommer t-sommer added the Berlin2020 label Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.