Data
Available background-mixed datasets in Rucio. Source of truth:
rucio did list --filter 'is_background_mixed=true' 'epic:*'The campaign strips below are authored by hand with the <DidStrips> component — see .vitepress/theme/components/DidStrips.vue. To refresh them after a new Rucio campaign, run the update-data-md skill: it queries Rucio, digests the DIDs with scripts/summarize_rucio_dids.py, and guides authoring the strips (labels, colours, and tooltips are set by hand).
Last updated: 2026-09-29
Conventions
- FULL — DD4hep simulation output (sim-level, full Geant4 hits).
- RECO — EICrecon reconstruction output (reco-level).
- Each strip covers one
(campaign, data_name)pair. Click a strip to reveal the exact Rucio DIDs with copy buttons; hover any tag for a description. main/branch / CI / Test entries are filtered out — only versioned campaigns are shown.epic_craterlakeis the only detector configuration.- Use the per-row 📋 to copy a single DID, the Copy all button to copy every DID in a strip (newline-separated), or click the prefix line to copy the shared DID prefix.
Campaign 26.07.1
epic:/{FULL|RECO}/26.07.1/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/Copy prefixAdds a SIDIS branch (pythia6-eic 1.0.0, q2_0to1) alongside the DIS/NC grid, and every dataset now has both a FULL (sim) and a RECO partition.
Campaign 26.07.0
epic:/{FULL|RECO}/26.07.0/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/DIS/NC/Copy prefixCampaign 2026-06
Meson-structure k-Λ background
/work/eic3/users/romanov/meson-structure-2026-06/reco-background/Copy prefixk-Λ signal reconstructed with background + beam effects — not on Rucio, on the JLab work disk (XRootD via root://dtn-eic.jlab.org). One leaf per beam energy of k_lambda_<beam>_5000evt_*.edm4eic.root; file counts are in the beam-energy tooltips above.
Campaign 26.05.0
epic:/RECO/26.05.0/epic_craterlake/Bkg_Exact1S_2us_e_only/GoldCt/10um/EW_BSM/ALP/madgraph5-3.7.0-1.0/Copy prefixroot://sci-xrootd.jlab.org//work/eic/users/romanov/epic-background-2026-05/csv_eicrecon/Copy CSV pathCampaign 26.04.1
epic:/{FULL|RECO}/26.04.1/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/DIS/NC/Copy prefixCampaign 26.03.0
epic:/RECO/26.03.0/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/Copy prefixCampaign 25.10
Not available on Rucio, but can be downloaded from JLab xrootd (root://dtn-eic.jlab.org//volatile/eic/...). These strips list the directory paths under each background configuration rather than leaf DIDs.
/volatile/eic/EPIC/RECO/25.10.0/epic_craterlake/Bkg_1SignalPer2usFrame/Copy prefixroot://sci-xrootd.jlab.org//work/eic/users/romanov/epic-background-2025-10/csv_reco/Copy CSV path/volatile/eic/EPIC/RECO/25.10.4/epic_craterlake/Bkg_1SignalPer2usFrame/Copy prefixroot://sci-xrootd.jlab.org//work/eic/users/romanov/epic-background-2025-10/csv_reco/Copy CSV pathThe six signal channels above resolve to eight leaf datasets (the directories that actually hold the RECO .edm4eic.root files). The DDVCS_ABCONV channel splits into hminus/hplus, and the Synrad_18GeV_… folder is a self-contained subtree (DIS/NC + DVCS_ABCONV) mixed with synchrotron radiation only rather than the full cocktail:
| Leaf dataset | Beam | Background | Files |
|---|---|---|---|
DIS/NC/10x100/minQ2=1 | 10x100 | cocktail | 4 978 |
DIS/NC/10x275/minQ2=1 | 10x275 | cocktail | 5 922 |
EXCLUSIVE/DDVCS_ABCONV/…/q2_0_10/edecay/hminus | 18x275 | cocktail | 7 517 |
EXCLUSIVE/DDVCS_ABCONV/…/q2_0_10/edecay/hplus | 18x275 | cocktail | 7 517 |
EXCLUSIVE/DVMP/…/unpolarised/18x275/q2_1_1000 | 18x275 | cocktail | 6 803 |
SIDIS/pythia6-eic/1.0.0/18x275/q2_0to1 | 18x275 | cocktail | 1 ⚠️ |
Synrad_18GeV_…/DIS/NC/18x275/minQ2=1 | 18x275 | synrad-only | 46 696 |
Synrad_18GeV_…/EXCLUSIVE/DVCS_ABCONV/18x275 | 18x275 | synrad-only | 20 103 |
⚠️ SIDIS currently has a single reconstructed file (
…run10.ab.0173…) — the rest of that dataset is not (yet) reconstructed on XRootD. Treat it as a placeholder until the campaign completes.
/volatile/eic/EPIC/RECO/25.10.4/epic_craterlake/Bkg_Exactly1SignalPer2usFrame/Copy prefixroot://sci-xrootd.jlab.org//work/eic/users/romanov/epic-background-2025-10/csv_reco/Copy CSV path/volatile/eic/EPIC/RECO/25.10.4/epic_craterlake/Bkg_OnlyPer2usFrame/Copy prefixroot://sci-xrootd.jlab.org//work/eic/users/romanov/epic-background-2025-10/csv_reco/Copy CSV path/volatile/eic/EPIC/RECO/25.10.4/epic_craterlake/Bkg_RealisticSignalPer2usFrame/Copy prefixroot://sci-xrootd.jlab.org//work/eic/users/romanov/epic-background-2025-10/csv_reco/Copy CSV pathUsing these DIDs
A DID is just a pointer — it resolves to a set of files (PFNs) on Rucio Storage Elements. Two upstream pages cover this in full; this section is the bare minimum to get you started.
- 📚 Rucio usage tutorial — setup, auth, full command reference.
- 📚 Use-cases tutorial — download vs. stream, batch workflows, common patterns.
1. One-time setup (inside eic-shell)
# Voms / OIDC auth — pick what matches your account (see Rucio tutorial).
rucio whoamiIf rucio whoami returns your identity, you're done. If not, follow the auth steps on the Rucio usage tutorial.
2. See what's inside a dataset
rucio did content list 'epic:/RECO/26.04.1/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/DIS/NC/10x100/minQ2=1'Get list of files to
rucio replica list file --protocols root --pfns --rses isopenaccess 'epic:/RECO/26.04.1/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/DIS/NC/10x100/minQ2=1'3. Download files locally
rucio download 'epic:/RECO/26.04.1/epic_craterlake/Bkg_Exact1S_2us/GoldCt/10um/DIS/NC/10x100/minQ2=1'(!) You probably don't want to download the full dataset!
Downloads land in a directory tree mirroring the DID. Add --nrandom N to pull only a sample, or --rse <RSE> to pin a storage element.
4. Stream over XRootD (no local copy)
Most analyses can read directly from XRootD — faster on the JLab farm and saves disk:
# List replica URLs for a DID
rucio list-file-replicas --pfns 'epic:/RECO/26.04.1/.../minQ2=1' | head
# Then open them directly, e.g. in ROOT / uproot / EICrecon:
root -l 'root://dtn-eic.jlab.org//volatile/eic/EPIC/RECO/.../file.edm4eic.root'See use-cases for the recommended patterns when running many jobs over a dataset.