Contents page for CI validation documentation:
- CI_Validation_Instructions: Instructions for shifters checking CI validation plots. Includes the basics of how to access and navigate the CI validation dashboard.
- Extra tips and tricks for navigating the CI validation dashboard
- Triggering the CI validation
- How to cancel a CI validation
- Checking whether the CI validation has worked
- Finding log files and debugging information if the CI build fails
- Finding output files from the CI validation for further tests
- How to run the CI validation scripts locally
- Full documentation of CI validation scripts: Docdb-13373
Finding the CI validation output files¶
One of the great side effects of the CI validation is that it produces and reconstructs an MC or data sample from scratch! This can be very useful - if you find any unexpected features in the CI plots, you can use these generated files to investigate further, without needing to run the code and generate new files yourself. You can also use the merged analysistree file produced by the CI to run the "long-form" validation suite, as described in the validation documentation in Docdb-13373.
The validation scripts run on the output of analysistree. The merged analysistree file generated by the CI is saved to persistent pnfs space in the following directories:
/pnfs/uboone/persistent/users/uboonepro/CI_physics_validation/data_data_cosmic_validation/for the cosmic data workflow (triggered using
/pnfs/uboone/persistent/users/uboonepro/CI_physics_validation/data_mc_cosmic_validation/for the cosmic MC workflow (triggered using
/pnfs/uboone/persistent/users/uboonepro/CI_physics_validation/mc_bnb_validation/for the BNB MC workflow (triggered using
Inside each of these directories will be a directory with your branch or tag name, and inside that directory should be a file called
The CI also writes the output files from each of its three stages (simulation, reconstruction, and anatree) to scratch pnfs space, in the following directories:
/pnfs/uboone/scratch/users/uboone/ci_validation/data_data_cosmic_validation/reco1_data/ /pnfs/uboone/scratch/users/uboone/ci_validation/data_data_cosmic_validation/reco2_data/ /pnfs/uboone/scratch/users/uboone/ci_validation/data_data_cosmic_validation/mergeana_data/
/pnfs/uboone/scratch/users/uboone/ci_validation/data_mc_cosmic_validation/sim/ /pnfs/uboone/scratch/users/uboone/ci_validation/data_mc_cosmic_validation/reco/ /pnfs/uboone/scratch/users/uboone/ci_validation/data_mc_cosmic_validation/mergeana/
/pnfs/uboone/scratch/users/uboone/ci_validation/mc_bnb_validation/sim/ /pnfs/uboone/scratch/users/uboone/ci_validation/mc_bnb_validation/reco/ /pnfs/uboone/scratch/users/uboone/ci_validation/mc_bnb_validation/mergeana/
/reco2_data/ directory contains reco2 output files and the individual anatree output files. The
/mergeana_data/ directory contains a single merged analysistree file (the same one that is also copied to
Note that because these files are written to scratch they will get deleted after not too long. If you want to keep the files for further study, you will need to copy them as soon as possible to persistent or /uboone/data storage.