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
ScheduledBasicBlock::get_waveform_duration_seconds assumes that the duration of all built-in waveforms is equal to their duration parameter. This isn't true for erfsquare, though; the duration is just that of the main pulse, and the padleft and padright parameters specify silent padding on either side, which contributes to the total duration.
If provided as a test case to program::schedule::tests::schedule_seconds, it will produce instruction timings of [0.0, 1.0, 1.1, 1.6], when it should instead produce [0.0, 1.5, 3.0, 4.5].
The text was updated successfully, but these errors were encountered:
@erichulburd That's part of a more in-depth solution, but it requires figuring out how WaveformTemplate integrates into quil-rs; as it stands, it's exported but never used internally. This means that deciding on how WaveformTemplate should be used is a bigger change, and I'd like to fix this specific issue before we resolve that.
ScheduledBasicBlock::get_waveform_duration_seconds
assumes that the duration of all built-in waveforms is equal to theirduration
parameter. This isn't true forerfsquare
, though; the duration is just that of the main pulse, and thepadleft
andpadright
parameters specify silent padding on either side, which contributes to the total duration.To see this, consider the following program:
If provided as a test case to
program::schedule::tests::schedule_seconds
, it will produce instruction timings of[0.0, 1.0, 1.1, 1.6]
, when it should instead produce[0.0, 1.5, 3.0, 4.5]
.The text was updated successfully, but these errors were encountered: