Protocols list

[Edoardo-Pedicillo]

Checklist:

• Reviewers confirm new code works as expected.
• Tests are passing.
• Coverage does not decrease.
• Documentation is updated.
• Compatibility with Qibo modules (Please edit this section if the current pull request is not compatible with the following branches).
  • Qibo: master
  • Qibolab: main
  • Qibolab_platforms_qrc: main

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.50%. Comparing base (44ec734) to head (89f4ac6).
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1012   +/-   ##
=======================================
  Coverage   97.50%   97.50%           
=======================================
  Files         123      123           
  Lines        9722     9722           
=======================================
  Hits         9479     9479           
  Misses        243      243           

Flag	Coverage Δ
unittests	97.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

[alecandido]

Are you planning to include other sections in the roadmap? (other than protocols)

[Edoardo-Pedicillo]

In the beginning, I was planning to add a Software section, but maybe if the issues are enough, I will remove the title.

[alecandido]

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...

[alecandido]

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.

[Edoardo-Pedicillo]

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.

[alecandido]

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.

[alecandido]

Is there a reason to completely exclude the process tomography?

[Edoardo-Pedicillo]

No, just forgotten

[andrea-pasquale]

Perhaps this one (Optimal control with rb) can be moved to high priority given that we are more or less working on it already?

[alecandido]

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)

[Edoardo-Pedicillo]

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.