harvest-and-analyze
Collect neutral-atom QPU bitstrings by batch ID once a submission has run, correct them for detection error, compute the target observable, compare it to the emulated baseline from validate-emu, and return an accept/reject verdict. Runs after a submission, never instead of one. Triggered by phrases like "collect the QPU results", "harvest these batch IDs", "compare the QPU data to the emulation", "is the QPU data consistent with the noise model".
Pinned to revision 2b0353d83e65, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/harvest-and-analyze/SKILL.md
- skills/harvest-and-analyze/support/correct_readout.py
- skills/harvest-and-analyze/support/harvest_qpu.py
- skills/harvest-and-analyze/support/pasqal_auth.py
- skills/harvest-and-analyze/support/plot_qpu_vs_emu.py
Every link opens the file at its source, pinned to the revision this page describes.