Validating Changes - DUNE/dune-tms GitHub Wiki

Running some test files

Prerequisites: Before proceeding, ensure that you have:

  1. Set up and compiled your modified version of DUNE TMS.
  2. Edited config/TMS_Default_Config.toml to set MaximumNEvents to a reasonable value (e.g., 5000).
  3. Selected test files for validation.

Running Test Files:

To validate the process, start by running some test files using the ConvertToTMSTree.exe command. Here are examples of commands for different scenarios:

  • NERSC files:
ConvertToTMSTree.exe /pnfs/dune/persistent/physicsgroups/dunendsim/abooth/nd-production/MicroProdN1p2/output/run-spill-build/MicroProdN1p2_NDLAr_1E18_RHC.spill.nu/EDEPSIM_SPILLS/0000000/0000100/MicroProdN1p2_NDLAr_1E18_RHC.spill.nu.0000110.EDEPSIM_SPILLS.root
  • Events on TMS and LAr:
ConvertToTMSTree.exe /pnfs/dune/persistent/users/kleykamp/nd_production/2024-04-18_rhc_test/edep/RHC/00m/00/antineutrino.0_1713482441.edep.root
  • LAr-only, not from NERSC:
ConvertToTMSTree.exe /pnfs/dune/persistent/users/kleykamp/nd_production/2024-05-13_lar_only_rhc/edep/RHC/00m/00/antineutrino.0_1715654453.edep.root

All commands should complete within a reasonable time frame, depending on your system's resources and the chosen MaximumNEvents value. Once completed, you can inspect the output using validation scripts.

Running Validation Scripts

See Validation Plots

Debugging:

If you encounter issues or need to debug the code, consider using gdb. To use it:

  1. Start gdb by running gdb ConvertToTMSTree.exe.
  2. Run the executable with a file using r <file>.
  3. Use bt for backtraces and other commands as needed (e.g., set breakpoints, read memory).
  4. If the code is stuck in an infinite loop, use ctrl-c to stop it, then resume with c. Repeat until you've isolated the issue.

For more information on using gdb, consult online guides tailored to your specific operating system and environment.

Additional Notes:

  • If you encounter any bugs or have suggestions, please report them on the DUNE TMS GitHub repository's issue tracker.
  • For general inquiries, reach out to us on slack via #nd_muon_spectrometer or #nd_muon_spectrometer_code
⚠️ **GitHub.com Fallback** ⚠️