Repository navigation
development building
This page is generated from docs/development/building.md. Do not edit it directly; change the repository source and let automation publish the Wiki.
Use direct CMake builds for source development. Normal ifarm operation uses run.csh, which reads config/run.json and builds LUND applications automatically.
cmake \
-S . \
-B build/debug \
-G "Unix Makefiles" \
-DCMAKE_BUILD_TYPE=Debug
cmake \
--build build/debug \
--parallel 4-S . tells CMake to read the source from your current directory. -B build/debug puts generated build files and compiled code in that separate directory. CMake saves its selected compiler, libraries, and options there in a cache. Use different build directories for different compilers, ROOT installations, or build types so an old cache does not select the wrong settings.
The code adopts the C++ standard published by ROOT and requires at least C++17. It does not force a different standard that might be incompatible with the selected ROOT build.
If CMake cannot find the intended ROOT installation, configure a fresh tree with its prefix:
cmake \
-S . \
-B build/debug-with-root \
-DCMAKE_BUILD_TYPE=Debug \
-DCMAKE_PREFIX_PATH="$(root-config --prefix)"
cmake \
--build build/debug-with-root \
--parallel 4Confirm that root-config names the intended installation before configuring.
Both applications are enabled by default. A focused build can omit the unused application and its ROOT components:
cmake \
-S . \
-B build/uniform-only \
-DCMAKE_BUILD_TYPE=Debug \
-DBUILD_GENIE=OFF
cmake \
--build build/uniform-only \
--parallel 4cmake \
-S . \
-B build/physical-only \
-DCMAKE_BUILD_TYPE=Debug \
-DBUILD_UNIFORM=OFF
cmake \
--build build/physical-only \
--parallel 4BUILD_GENIE=OFF omits the physical LUND converter. BUILD_UNIFORM=OFF omits the uniform LUND creator and monitoring code.
build/debug/apps/uniform-lund-creator --help
build/debug/apps/event-generator-to-lund-converter --helpThen run a small sample using fixed nonzero seeds through the code you changed. Inspect its files, event counts, LUND creation log, and printed messages. Build commands alone never create LUND files or submit simulation.
Generated from the e4nu/CLAS12-sample-tools documentation.
Source links use branch main. Source checkout: 6281a91714f4; commit date: 2026-10-13T14:50:21+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