Paper runcards

[rodolfocarobene]

I added a new folder with the runcards used for the paper, in this way we can link directly the experiments for reproducibility.

Checklist before merge:

• [ ] Reviewers confirm new code works as expected.
• [ ] Tests are passing.
• [ ] Documentation is updated.

[codecov[bot]]

Codecov Report

Patch has no changes to coverable lines.

:loudspeaker: Thoughts on this report? Let us know!.

[alecandido]

--no-update should be available as a runcard key (even top-level). If that works, it should either be specified to use it in some note (e.g. README.md), or by plugging that key in the runcard itself.

[andrea-pasquale]

--no-update should be available as a runcard key (even top-level). If that works, it should either be specified to use it in some note (e.g. README.md), or by plugging that key in the runcard itself.

I think that you can simply but update: False at the top of the runcard and it should work.

EDIT: Actually if you care only about the acquisition time you can also do qq acquire <path_to_runcard>, but this is not available yet in the stable release of qibocal. This will also solve the problem with update.

[alecandido]

I think that you can simply but update: False at the top of the runcard and it should work.

The If that works part meant something like if you really do not need to update between subsequent steps.

[andrea-pasquale]

The If that works part meant something like if you really do not need to update between subsequent steps.

I think the only issue could be that if you have a completed uncalibrated chip and you run all the routines sequentially you might end up with values that don't make sense, such as amplitude > 1, which will trigger and error in qibolab therefore stopping the execution. In this sense, if you care only about performance setting update=False it is the safer option.

[rodolfocarobene]

Thanks @AleCandido @andrea-pasquale, now that is fixed!