Add approximate settings for early science beam configurations #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ate until official ones are made
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Briefly, what does this PR introduce?
This PR adds settings for the afterburner to allow burning of e+D, e+He3, and e+p configurations which match the settings of the early-science program. For now, these settings assume "BeAGLE" style input for the nuclei, where the momenta are assumed be for the "active" nucleon participating in the hard interaction.
For example, 10x130 GeV/n e+deuteron interactions are "looking" for either a beam proton or a beam neutron with ~ 130 GeV of energy.
If a generator is used which assumes the actual nucleus as an incoming beam in the HEPMC event record (e.g. status == 4 hadron beam), and new PR will be needed to add the proper functionality.
It should be noted that these "new" beam configurations are APPROXIMATE, using existing proton beam settings that are "close" in beam energy.
We do not have official beam settings from the project, but once we do, these numbers will be updated in the afterburner promptly.
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Offline tests have been completed and it seems to work as expected. We will perform tests once we have events generated to ensure all settings are okay - but this needs to be available on a short timescale so people can begin testing and provide feedback.
See comments in the modified code.
This has been discussed with some of the interested analyzers, and more will be discussed at the ePIC meeting.
Does this PR introduce breaking changes? What changes might users need to make to their code?
No, it just adds more functionality.
Does this PR change default behavior?
It shouldn't, no. It should only add more usable configurations for other inputs.