Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/frame update #52

Merged
merged 37 commits into from
Jul 14, 2016
Merged

Fix/frame update #52

merged 37 commits into from
Jul 14, 2016

Conversation

dieris
Copy link
Collaborator

@dieris dieris commented Jul 7, 2016

Fixed merging of modulation instructions.

The sequence SimultaneousRB_AC works in the experiment, but fails in the test, with multiple differences against the example sequence. Not sure how to compare the differences.

CoherenceController added 2 commits June 29, 2016 16:12
Merge MODULATE commands when there is no pending frame update; merge
consecutive UPDATE_FRAME commands
--CAR and DR
@coveralls
Copy link

coveralls commented Jul 7, 2016

Coverage Status

Coverage increased (+0.09%) to 73.818% when pulling 492abf1 on fix/frame-update into 45226f7 on master.

@caryan
Copy link
Contributor

caryan commented Jul 8, 2016

The test data isn't wrong it just doesn't allow for dropping initial Z rotations.

@caryan
Copy link
Contributor

caryan commented Jul 8, 2016

@dieris could you please give 8745a78 a try on the qubits. It implement the initial Z rotations by putting them before the trigger (held modulation commands are also implemented on a trigger).

@coveralls
Copy link

coveralls commented Jul 8, 2016

Coverage Status

Coverage increased (+0.04%) to 73.767% when pulling 8745a78 on fix/frame-update into 45226f7 on master.

@dieris
Copy link
Collaborator Author

dieris commented Jul 8, 2016

8745a78 still doesn't cover the case where UPDATE_FRAME follows SET_FREQ (last instruction is not WAIT). Should the order be: SET_FREQ, UPDATE_FRAME, WAIT? This happens for example if the first sequence starts with a frame update.

@caryan
Copy link
Contributor

caryan commented Jul 8, 2016

Indeed, again highlighting our lack of test coverage for SSB.

@caryan
Copy link
Contributor

caryan commented Jul 8, 2016

492abf1 should cover the non-zero SSB case too.

@coveralls
Copy link

Coverage Status

Coverage decreased (-53.5%) to 20.176% when pulling 96bdd81 on fix/frame-update into 45226f7 on master.

@coveralls
Copy link

coveralls commented Jul 8, 2016

Coverage Status

Coverage increased (+0.009%) to 73.734% when pulling 071ec78 on fix/frame-update into 3970877 on master.

@dieris
Copy link
Collaborator Author

dieris commented Jul 12, 2016

There is still something inconsistent. These RB_AC seqs. are nominally the same, but they work for one qubit and not for the other! The failing seqs. (wrong result) are those starting with ArbAxis for APSII3 (but they are okay for APSII7). I can't find the difference... (apart from pulse length)

See for example instructions 145 to 167 in both files, corresponding to:

[WAIT,
 ArbAxis(q)⊗ TRIG(slaveTrig)⊗ Id(digitizerTrig)⊗ Id(M-q),
 U(q),
 ArbAxis(q),
 Y(q),
 ArbAxis(q),
 Y90(q),
 ArbAxis(q),
 ArbAxis(q),
 MEAS(M-q)⊗ TRIG(digitizerTrig)⊗ Id(slaveTrig)⊗ Id(q)]

I'll do more testing on the qubits. When SSB and pulse lengths are the same, the pulses are identical at the scope.

caryan and others added 18 commits July 12, 2016 11:22
also allow some PatternUtil functions to check for other waveform types

with @blakejohnson
calling `logging.getLoger` on every call was surprisingly slow

with @blakejohnson
construct `APSWaveform` object for repeats and add equality testing for
`APSWaveform` class
namedtuple Pulses and other performance improvements
Merge MODULATE commands when there is no pending frame update; merge
consecutive UPDATE_FRAME commands
--CAR and DR
@coveralls
Copy link

coveralls commented Jul 14, 2016

Coverage Status

Coverage decreased (-53.4%) to 20.33% when pulling f20e0ec on fix/frame-update into 3970877 on master.

@dieris dieris merged commit 397d2bd into master Jul 14, 2016
@caryan
Copy link
Contributor

caryan commented Jul 15, 2016

@dieris so was there a resolution to SSB sign issue?

@dieris
Copy link
Collaborator Author

dieris commented Jul 15, 2016

yes, the sign is correct. But the atomic Clifford gate fidelity for one of the qubits is just terrible (independently of mixer, APS, etc.)

@caryan caryan deleted the fix/frame-update branch July 17, 2016 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants