Quasi-free processes with pluto #3
Open
Conversation
This file contains hidden or 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
…e of the coding to how it is done elsewhere
…be more similar to others
…ll to a separate ProcessHits for the active target, which turned out to not be needed
…, separate material section for TPB, fixed some material properties, square fibers, added epoxy and SiPMs, made SiPMs sensitive
…so important to check visually for now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When using the nucleus_fermi plugin of pluto, the output tree now has two pseudo-particles, the first being the beam+target, the second being the beam+quasi-free-target. The first commit forces the code to use the first pseudo-particle to get the beam information (as it has an at-rest target). The second commit adds a carbon nucleus as a target. This should be generalized to include other nuclei in pluto.