Sensor normal surface #38
Draft
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
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?
The goal is to study the impinging angle of the photons (at this level just reconstructed photons but setting QE and safety factor to 1 one can mimic it to a MC level information) wrt the normal of the sensor surface. The code introduces some changes to compute the angle coming from the EICRecon level branch (
pdu-update-normal-surface). Right now, I am just printing the angles for 50 generated particles; in future the plan is to plug them into the output root file. This is why it is just a draft PR, to check the methods are right or not.What kind of change does this PR introduce?
Please check if this PR fulfills the following:
I have discussed with @c-dilks about these changes.
Does this PR introduce breaking changes? What changes might users need to make to their code?
Does this PR change default behavior?