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
When sending two pulse sequences over the same channel, provided they don't overlap in time, they are not getting separated into different sequencers. Consequently, the frequency of the first pulse defines the nco frequency for the sequence and all the following pulses use the same frequency irrespective of their settings. For instance, the following code generates the attached sequences sent to qblox.
@jevillegasdatTII I will take a look at your commits, but for the future can you please not push any commits directly to the branch qblox-ad-hoc-features, and instead create a PR pointing to that branch.
qibolab/src/qibolab/pulses.py
Line 1586 in 898fa86
When sending two pulse sequences over the same channel, provided they don't overlap in time, they are not getting separated into different sequencers. Consequently, the frequency of the first pulse defines the nco frequency for the sequence and all the following pulses use the same frequency irrespective of their settings. For instance, the following code generates the attached sequences sent to qblox.
Z_qcm_rf0_sequencer1_sequence.json
Z_qcm_rf0_sequencer0_sequence.json
Z_qcm_rf0_snapshot.json
Notably, only two sequencers are created, where we need three (channel 2 with two different frequencies and channel one a single one).
The text was updated successfully, but these errors were encountered: