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.
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
Protocols list #1012
Protocols list #1012
Changes from 3 commits
7a06837
0fff1a8
977e0a6
d00d800
89f4ac6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Are you planning to include other sections in the roadmap? (other than protocols)
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.
In the beginning, I was planning to add a Software section, but maybe if the issues are enough, I will remove the title.
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.
Of course, we could even try to schedule some more relevant software feature for the future.
However, software-wise we're really moving on a need-based approach (mainly because of the lack of person power), so I'd not be so systematic in this respect, since it may end up being completely useless...
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.
Perhaps this one (Optimal control with rb) can be moved to high priority given that we are more or less working on it already?
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.
Agreed.
Though, I'm not sure I would classify that as a protocol at all...
Instead, I would build as a protocols' composition with scripts. And, as part of this effort, I could finally work out a way to meaningfully distribute even this kind of pre-compiled applications with Qibocal, or in parallel to it (but within the repo).
In any case, this is just an opinion, and up for discussion.
(there will be an acquisition, a fit, a report, and an update generated - but the acquisition and the fit won't be really two separate phases, that's why I'd not make it a protocol itself)
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.
Yes, but at the moment I would like to collect all the missing protocols in the file, so both routines and scripts, since at the moment they will be collected in this repo.
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.
Speaking of MM. Should we also add other possible implementations of Z rotations? (14.6.4)
As low priority, of course.
Not much because they may be useful as gates, but just because they are possible, and they may be used as further checks on the qubit, since they are playing with the same parameters.
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 would peronally avoid them since they don't add information, maybe the only one to take into consideration is the one using the AC Stark effect to study the phenomenon itself.
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.
To be fair, that's the one I mostly had in mind...
(the virtual Z we already had, and the composition of other X and Y gates requires a calibration of the Y for arbitrary angles...)
Maybe, the other one I would have considered is fluxing the qubit to measure the Z rotation. As a (redundant?) way to show control over the flux.
In any case, if interesting, we could even reconsider at a later stage.
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.
Is there a reason to completely exclude the process tomography?
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.
No, just forgotten