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
@alecandido following the meeting last Wednesday, I understood that PulseSequence.concatenate in the last example pads the the sequence with delays so that the MZ plays after RX. However, the following example:
Yes, that's correct. I can add this change (and a test) in the PR that will implement this issue.
Two concatenatedPulseSequence should actually start one after the other. If they need to be played in parallel (as it could be the case for different qubits) you should instead use .extend() (or the associated list operator, i.e. +, which will create a new sequence, same as | will do for .concatenate()).
The idea is to make it simpler to create sequences.
Currently, you have to do something like this:
(cf.
conftest.py
, theexecute
fixture)A couple of proposals to make it simpler are:
Native.create_sequence()
with.__call__()
PulseSequence.concatenate()
with.__or__()
.concatenate()
will be.__ior__()
, since the operation is in-places1 | s2
just by creating a new sequence:It should be possible to then write it like the following:
The text was updated successfully, but these errors were encountered: