-
Notifications
You must be signed in to change notification settings - Fork 7
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
Ramsey unrolling #666
Merged
Merged
Ramsey unrolling #666
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f5eff74
draft
Jacfomg 84c2c33
it was already working
Jacfomg 4643ca0
signal ramsey and remove useless ramsey file
Jacfomg 528c3b9
fix
Jacfomg 577dc98
Merge branch 'main' into ramsye_unrolling
stavros11 d23cb1a
Merge branch 'main' into ramsye_unrolling
stavros11 ac5eda7
Add Ramsey sequences for detuned experiments
Jacfomg a5b2f92
Merge branch 'ramsye_unrolling' of https://github.com/qiboteam/qiboca…
Jacfomg 4494d97
fix: Fix typo in tests and operations
andrea-pasquale 9a0f1e7
test: Fix coverage
andrea-pasquale File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a lot of repeated code under the cases
n_osc == 0
andn_osc != 0
. I would like to suggest unifying them, or moving the repeated functionality into a function. It would be even nicer if theramsey_signal
also benefits from such unification. Unfortunately I am not able to understand what is the meaning ofn_osc
from its documentation, so cannot suggest a more concrete refactoring. Let's discuss.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @hay-k. We should definitely find a way to improve it. Just for reference
n_osc
stands fornumber of oscillations
. In the ramsey protocol by putting a non zero integer value we include a detuning through the relative phase that will generaten_osc
number of oscillations in the plot.qibocal/src/qibocal/protocols/characterization/ramsey.py
Lines 190 to 195 in 528c3b9
Having said this, I believe that in
ramsey
we differentiate between then_osc==0
and then_osc!=0
case because in the first case the protocol can be implemented through a simple sweeper on the start of the second RX90 pulse while in the second case, if I remember correctly, there are some limitations in our drivers that prevents us from sweeping start and relative phase at the same time. @stavros11 feel free to correct me if I said something wrong.Of course the best solution for qibocal should be to keep the code as clean as possible and let the drivers handle these specific cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks for the explanation! I think, in general, the drivers (and their developers, of course) will benefit a lot from a more unified and consistent implementation. Anyways, that's a story for another day. I believe we should still simplify the code in this particular instance, even without improving anything else anywhere else. That should be doable, and I am here to assist. @Jacfomg probably best if we discuss AFK.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, it's sounds like a good plan.