Closed Gregtom3 closed 7 months ago
Testing it on ifarm now, but it might be nice to have an option similar to the energy settings to select only whatever Q2 ranges you're interested in (not sure if this would make the Q2 weighting a pain though)
May want to increase the memory request for the parallel analysis jobs, they all failed due to running out of memory for me.
Tested this again while being better at reading all your comments in the readme, and it seems like your default memory request should be okay up to 3 files per job.
Briefly, what does this PR introduce?
Parallel computing capabilities with JLab's ifarm computing. Allows for multiple root files to be analyzed per job while maintaining proper Q2weighting across entire pipeline.
New script titled
hpc/run-local-slurm-pipeline.rb
creates the full pipeline that is run with a 'single button press'. After running the script, it will generate a new "run" script inhpc/project_scripts
that will do the following for each campaign and beam energy..config
file for the chosen campaign, detector configuration, and beam energy.config
file into multiple batches, with a number ofROOT
files per batch specified by the userQ2
range studied, either by reading the TTrees directly or calling their values from csvs inhpc/nevents_database
. New files have their number of events automatically added to the database for faster access in the future.Q2weights
for each range and insert them into the batched.config
files.config
file on the analysis macro specified by the userWhat kind of change does this PR introduce?
Q2weight
issue wherebeamCrossing!=0
changes the trueQ2 of the event, causing us to assign itsQ2weight
to the wrong value.Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
Does this PR change default behavior?
Yes. See
Q2weight
issue above.