aryaraeesi/BEvAn-data
BEvAn — COSI activation simulations MEGAlib simulation files backing cosi-betadecay/BEvAn, a physics-based likelihood classifier that tags each simulated COSI event as a β⁺ / positron-annihilation signal (back-to-back 511 keV photons) or background from its Compton kinematics. All events come from a cosima activation simulation (BeamType Activation, DecayMode ActivationBuildup): cosmic-ray protons irradiate the instrument, the activated isotopes decay, and the β⁺ emitters among… See the full description on the dataset page: https://huggingface.co/datasets/aryaraeesi/BEvAn-data.
BEvAn — COSI activation simulations
MEGAlib simulation files backing `cosi-betadecay/BEvAn`, a physics-based likelihood classifier that tags each simulated COSI event as a β⁺ / positron-annihilation signal (back-to-back 511 keV photons) or background from its Compton kinematics.
All events come from a cosima activation simulation (BeamType Activation, DecayMode ActivationBuildup): cosmic-ray protons irradiate the instrument, the activated isotopes decay, and the β⁺ emitters among them produce the 511 keV annihilation signal the classifier is trained to find. The three-step cosima source files that generate this are in the GitHub repo under `data/cosima/` and are not duplicated here. Produced with MEGAlib 4.00.00.
Datasets
One folder per detector geometry. The geometries ship with MEGAlib under $MEGALIB/resource/examples/geomega/:
Files in each folder
For a dataset {name}:
The COSIBalloon_* folders additionally carry a crossections/ directory — MEGAlib-generated cross-section tables. They are regenerated on demand by MEGAlib and are included only so the folders are a byte-exact mirror.
Results
results/ holds the outputs of the ablation study over the datasets above — a mirror of ablations/results/ in the GitHub repo (which remains the source of truth; these are generated files, published here so the figures and numbers are citable alongside the inputs they came from). 25 MB total.
One folder per run, named by timestamp:
Each run folder has:
tables/— one CSV per ablation (factor_contributions,learned_weights,no_ckd_order,gt_tolerance/label_window, …) plus asummary.csv.deployment.csvis the champion deployed per dataset at the dedicated-prior operating point.figures/— one PNG per ablation at the top level, plus a per-dataset subfolder (SPILike/,NCT/,Max/,GeACT/,COSIBalloon_*/) of the per-run plots for that geometry.
Regenerate with python ablations/main.py from the GitHub repo.
Download
hf download aryaraeesi/BEvAn-data --repo-type dataset --local-dir data/Note this pulls results/ into data/ too. For just the simulation inputs, or a single dataset (remember to take its .inc* chunks along with the .sim):
hf download aryaraeesi/BEvAn-data --repo-type dataset \
--include "SPILike/*" --local-dir data/Or just the results, without the multi-GB simulations:
hf download aryaraeesi/BEvAn-data --repo-type dataset \
--include "results/*" --local-dir .Gotcha: the geometry path is absolute
The Geometry line inside every .sim header is an absolute path from the machine that ran the simulation (/home/arya/Documents/megalib/...). MEGAlib will not find the geometry on your machine unless you either point that line at your own $MEGALIB checkout or pass the geometry explicitly — which is what the BEvAn entry scripts do via --geo-file:
python src/BEvAn/analysis.py \
--geo-file $MEGALIB/resource/examples/geomega/special/SPILike.geo.setup \
--sim-file data/SPILike/SPILike.sim \
--tra-file data/SPILike/SPILike.tra \
--prior-sim data/SPILike/SPILike_P1.sim data/SPILike/SPILike_P2.simLicense
Apache-2.0, matching the BEvAn repository.
