Repository navigation
Repository Overview
This page is generated from README.md. Do not edit it directly; change the repository source and let automation publish the Wiki.
This project prepares CLAS121 simulation samples for the e4ν collaboration. It prepares truth-level particles as LUND files and submits them for GEMC2 detector simulation and COATJAVA3 reconstruction, with explicit sample and detector settings. The project provides two workflows: creating LUND files and submitting CLAS12 detector simulation and reconstruction jobs.
| Workflow | What it does | Main result |
|---|---|---|
create-lund |
Creates LUND input from random acceptance-test kinematics or converts existing event-generator truth-level data | LUND files and a completion manifest log |
submit |
Submit simulation and reconstruction jobs to Jefferson Lab’s computing farm (ifarm), using the Slurm job scheduler | GEMC detector simulation followed by COATJAVA reconstruction |
The uniform LUND creator makes deliberately unphysical samples that cover configured momentum and angle ranges. The physical LUND converter preserves supported particles from existing event-generator output; it currently reads GENIE GST ROOT trees and does not run GENIE. Both paths use the same target geometry, LUND writer, file splitting, provenance, and completion rules where their meanings agree.
The workflows stop at reconstructed HIPO output, which can be analyzed with CLAS12ROOT. They do not generate physical interactions, calculate detector acceptance, skim reconstructed data, or perform physics analysis.
For the legacy code: see legacy-code-archive tag.
The code Wiki is the user and developer manual. Its home page gives separate reading paths for running the software and extending it.
For a small uniform run on the ifarm, use the uniform-1e-5986MeV.conf:
source run.csh \
--workflow create-lund \
--source uniform \
--config config/samples/uniform-lund-creation/uniform-1e-5986MeV.conf \
--events 100 \
--output /path/to/quickstart-outputrun.csh is designed for a disposable ifarm checkout: it discards tracked changes and removes untracked and ignored files, preserving only the checkout's build/ tree, then updates from Git and builds when needed. Full workflow validation happens after this refresh. Commit and push valuable development work before running it, and keep sample output outside the checkout. Local developers should build with CMake and invoke the compiled executables directly.
After LUND creation succeeds, preview simulation submission with the run's lundfiles/ directory:
source run.csh \
--workflow submit \
--lund-dir /path/to/quickstart-output/Uniform__1e__5986MeV/lundfilesPreview is the default. Add --execute only after reviewing the resolved detector settings and output actions.
Useful entry points:
The longer command collections under tutorials/ demonstrate every public option. Historical implementations are preserved in the legacy-code-archive tag and are not part of the current manual.
1. V. D. Burkert et al., “The CLAS12 Spectrometer at Jefferson Laboratory,” Nucl. Instrum. Meth. A 959, 163419 (2020). doi:10.1016/j.nima.2020.163419 ↩
2. M. Ungaro et al., “The CLAS12 Geant4 simulation,” Nucl. Instrum. Meth. A 959, 163422 (2020). doi:10.1016/j.nima.2020.163422 ↩
3. V. Ziegler et al., “The CLAS12 software framework and event reconstruction,” Nucl. Instrum. Meth. A 959, 163472 (2020). doi:10.1016/j.nima.2020.163472 ↩
Generated from the alons126/CLAS12-sample-tools documentation.
Source links use branch main. Source checkout: df853e1e8efc; commit date: 2026-11-07T16:35:09+02:00. Source checkout was clean when generated.
- Getting started
- Dependencies and execution environments
- Quickstart
- Run directories and outputs
- Troubleshooting
- Create LUND files
- Uniform LUND creation
- Physical LUND conversion
- LUND-creation configuration reference
- Uniform monitoring
- LUND-creation examples
- Sample profiles
- Submit GEMC and reconstruction jobs
- Ifarm environment and checkout model
- Simulation submission guide
- Submission configuration reference
- Follow jobs and verify output
- Submission examples
- GEMC and reconstruction worker
- Concepts and contracts
- Architecture
- LUND data contract and provenance
- Sampling models and random numbers
- External geometry and detector inputs