pasqal-io/neutral-atom-toolkit

Guides a user who has decided on the CEA/GENCI route through applying for QPU hours on the Pasqal Ruby (Orion) analogue neutral-atom quantum computer at GENCI/CEA TGCC - via either the French GENCI eDARI portal or the EuroHPC Quantum Access Pilot call - and through the follow-on TGCC computing account. Relevant to requests such as "apply for TGCC hours", "eDARI application", "apply for Ruby/Pasqal QPU allocation", "GENCI allocation", "request a TGCC computing account", "EuroHPC quantum hours", "Quantum Access Pilot", "apply on access.eurohpc-ju.europa.eu", or "attach to a project / rattachement". Concerns obtaining access only, not running sequences, submitting jobs, or analysing results on already-granted hardware. Not sure whether CEA/GENCI or Pasqal Cloud fits? Use choose-access-method first.

Helps a user who does not yet have QPU access decide which route to pursue - free CEA/GENCI/EuroHPC access to Ruby (weeks of lead time, specific eligibility) versus Pasqal Cloud pay-as-you-go (available today, any country, a card). Relevant to requests such as "how do I get QPU access", "which account should I use", "Pasqal Cloud vs CEA", "do I qualify for free QPU time", "I don't have an account yet and don't know where to start", or "what's the fastest way to run on real hardware". Once the route is decided, hand off by name to create-pasqal-cloud-account or apply-genci-tgcc-cea - this skill is for the decision itself, not either account-creation flow.

Guides a user who has decided on Pasqal Cloud through getting access to it - creating the account on portal.pasqal.cloud, and optionally coupling it to Google Cloud Marketplace so real QPUs and the advanced emulators become available. Relevant to requests such as "create a Pasqal Cloud account", "sign up for Pasqal Cloud", "I need a PASQAL_PROJECT_ID", "connect Pasqal to Google Cloud", "subscribe to Pasqal on GCP Marketplace", "how do I run on FRESNEL", or "my project only shows EMU_FREE". Concerns obtaining access only, not building sequences, submitting jobs, or analysing results. Not sure whether Pasqal Cloud or CEA/GENCI fits? Use choose-access-method first.

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

Emulate a neutral-atom Pulser sequence's time evolution under the target Rydberg device's live noise model, producing noiseless and noisy trajectory curves with a quantile envelope. Asks where to run — this machine, a GPU cluster, or Pasqal Cloud emulators. Use this to study how noise shapes a signal over time; use validate-emu to decide whether an experiment is worth submitting. Triggered by phrases like "run a noise emulation of this sequence", "emu-mps with noise", "noise envelope".

Submit a neutral-atom experiment_spec.json plus its Pulser sequence file to a Rydberg QPU on Pasqal Cloud, with an optional pre-calibration batch that measures the device's Rabi frequency and Rydberg resonance and compensates the submitted jobs. Writes batch IDs for harvest-and-analyze. For a QPU reached over SSH through a cluster scheduler, use submit-to-cea. Triggered by phrases like "submit this spec to the QPU", "run this sequence on Fresnel", "send it to the neutral-atom hardware".

Generate a Pulser sequence builder for a neutral-atom (Rydberg) experiment from an experiment_spec.json. Output is a *_sequence.py with two standardised functions — build_sequence() and compute_observable() — consumed by validate-emu, qpu-submit and harvest-and-analyze. Triggered by phrases like "generate the Pulser sequence", "write the sequence file for this spec", "spec to sequence", "turn the spec into Pulser code".

Submit a Pulser parametric experiment to Ruby, the neutral-atom QPU hosted at CEA/TGCC on the irene supercomputer, over SSH — generate the job bundle, deploy it, launch the ccc_msub jobs, monitor them, collect the results, with no manual copying. The templates are TGCC-specific and say what a sibling Bull or Slurm site needs changed; use qpu-submit for a cloud-API QPU. Triggered by phrases like "submit to CEA", "launch on Ruby", "submit to TGCC".