You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The constraints for fast counter hardware are a dictionary. The keys are nowhere specified however. Therefore I am having difficulty in writing a hardware module implementing the FastCounterInterface.
When does the bug occur?
not applicable
How do we replicate the issue?
not applicable
Expected behavior
The structure of the dictionary returned by get_constraints() is documented in the interface, e.g. in the docstring of this method.
Relevant log output
No response
Additional Comments
Looking through existing hardware implementations, I could find the following keys in FastComtec:
Version
current main
What is affected by the bug?
The constraints for fast counter hardware are a dictionary. The keys are nowhere specified however. Therefore I am having difficulty in writing a hardware module implementing the
FastCounterInterface
.When does the bug occur?
not applicable
How do we replicate the issue?
not applicable
Expected behavior
The structure of the dictionary returned by
get_constraints()
is documented in the interface, e.g. in the docstring of this method.Relevant log output
No response
Additional Comments
Looking through existing hardware implementations, I could find the following keys in
FastComtec
:If this implementation is correct, the docstring for get_constraints() is actually incorrect, since it states:
Contact Details
No response
The text was updated successfully, but these errors were encountered: