Repository navigation
development overview
This page is generated from docs/development/index.md. Do not edit it directly; change the repository source and let automation publish the Wiki.
Read these pages in this order when changing the code:
- Architecture
- Source and API map
- LUND data contract and provenance
- Sampling models and random numbers
- External geometry and detector inputs
- Contributing
- Developer build reference
- Scientific validation boundaries
Then use adding a physical-input adapter for that specific extension, or Wiki publishing when changing documentation and its publication. The getting-started path remains the operating guide; developer pages explain the implementation behind it.
Use Preparing a publication PR to copy reviewed application files from dev onto release-candidate and open a PR into main.
When changing behavior, update the code, command-line help, profiles, tutorials, and Wiki source together. Readers should not have to guess which description matches the current program.
Generated from the alons126/CLAS12-sample-tools documentation.
Source links use branch dev. Source checkout: d5987f01550d; commit date: 2026-10-13T14:52:09+03: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