AssignBunchTimingMC tool + config file changes #323
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
James processed new tank samples that have smaller flux windows and utilize a different timing scheme, where t0 is assigned as the beam dump rather than when the particle enters the detector geometry. The
AssignBunchTimingMC
tool has a hard coded configuration that uses the average neutrino flight time from beam dump to the detector (extracted from all WCSim production samples) and uses that to construct BNB-style bunches. As we are using a new flux window (size reduced by x2), the flight time needs to be adjusted.Also added the configuration file for this tool to some popular toolchains (
BeamClusterAnalysisMC
andCC_MC_Reco_ntuple
).Added additional configuration variables to the
PhaseIITreeMaker
(including one for the Bunch Timing tool) that are absent in the normal configuration variables within the toolchains mentioned above.This PR is mainly to get all configurations and tools in order for James' end-to-end CC analysis workflow. It involves more than a single change but its just adding the same config file over and over for different toolchains.
Checklist before submitting your PR
new
usage, there is a reason the data must be on the heapnew
there is adelete
, unless I explicitly know why (e.g. ROOT or a BoostStore takes ownership)Additional Material
Details on how the bunch timing is assigned can be found here: https://annie-docdb.fnal.gov/cgi-bin/sso/RetrieveFile?docid=5768&filename=AssignBunchTimingMC%20Tool%20PR%20304%20_%20Steven%20Doran.pdf&version=1