"with parallel" breakage #298
Labels
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/nac3#298
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This works (from the analyzer unit test):
This doesn't:
or
I am trying to port the test case to
min_artiq.py
, and I don't know how to port this specific statement:What is the type of
dmgr
, and is it possible for me to change this to directly pass theCore
instance inCreateTTLPulse
?Just follow the min_artiq example
https://git.m-labs.hk/M-Labs/nac3/src/branch/master/nac3artiq/demo/demo.py#L11
After testing with
73500c9081
, this is the result:More kernel test results:
succeeds with no issues:
succeeds with no issues:
fails with only the failing edge being received:
fails with no pulse being received:
So upon re-evaluating the fix for this, I have come up with two ways of addressing this issue with slightly different semantics.
sequential
block is executedThis can be seen as a "loose" implementation of deep parallel, as it does not strictly obey the that only function calls will reset the timeline.
sequential
block is executedThis is a strict implementation of deep parallel, but may be confusing when
now_mu()
is used (directly or indirectly) in the next function call, asnow_mu()
will only be reset after the function call returns, and the function call cannot be any of the builtin timeline functions (now_mu
,at_mu
,delay_mu
, which skips the timeline reset logic).