Repository navigation
create lund monitoring
This page is generated from docs/create-lund/monitoring.md. Do not edit it directly; change the repository source and let automation publish the Wiki.
The uniform LUND creator saves histograms and plots of the particles it generates. The physical LUND converter reports event counts and the settings used, but creates no monitoring histograms.
Each uniform run writes every histogram once to:
RUN/lundfiles/lund-creation-monitoring/<PREFIX>__monitoring_plots.root
It renders the same objects into:
RUN/lundfiles/lund-creation-monitoring/MonitoringPlotsPath/
├── <PREFIX>__plots.pdf
├── <PLOT_INDEX>_<HISTOGRAM>.png
└── ...
The plots cover the quantities relevant to the selected channel:
- electron momentum,
$\theta$ , and$\phi$ ; - hadron momentum,
$\theta$ , and$\phi$ foreh; - vertex coordinates, except in the electron-tester angular scan;
- single-particle momentum/angle correlations; and
- electron–hadron correlations.
Hadron object names include both species and region: pFD, nCD, pipFD, and so on. Production object names end with the complete channel label so ROOT's statistics display identifies the sample. Electron-tester objects instead use the suffix Tester_e.
Histograms use 100 bins per axis. Momentum displays extend to Number of events; two-dimensional plots use ROOT's colz rendering.
Use these plots to inspect the sampled momenta, angles, and vertex coordinates. They show what was generated, not what the detector reconstructed. Plot axes stay fixed when you change sampling limits. If a limit extends beyond an axis, check ROOT's underflow and overflow counts: entries below or above the displayed range. These plots alone do not measure detector acceptance or show that GEMC and reconstruction are correct.
For a small uniform run, open the ROOT file and combined PDF, and inspect the PNG files in the plot directory. Check that the expected plots for your channel are present and readable. A missing or unreadable export needs investigation even when the final LUND creation log exists.
The monitoring routine checks that it can create the ROOT file and write each histogram. It then asks ROOT to export PDF and PNG files, but does not check those files afterward. The final LUND creation log records completion of the program's checked stages; it is not an independent validation of rendered plots. Preserve the ROOT file and terminal diagnostics when reporting a rendering failure. Do not rerun into the same output parent merely to retry rendering: creation replaces the entire resolved run directory, including earlier simulation output.
Generated from the e4nu/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