Conversation
Member
Author
|
@chchatte92 could you update the p and eta ranges for the dRICH? So far I just put in some rough guesses: epic-analysis/macro/ci/postprocess_eta_vs_p_forPID.C Lines 13 to 32 in 7d2d887 And here's what it looks like (with very low statistics):
|
Member
Author
|
Perhaps with the help of @preghenella, et al., we could add the other PID subsystems too. |
Member
|
@c-dilks, we will do that. BTW, with Q2>1; p_T>0.1 and 0.01<y<0.95 positive pions are like this: |
Member
Author
Member
Author
|
BTW, you can find the updated (eta,p) plots in artifact |
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?
Draw PID (eta,p) limit boxes on eta vs. P histogram (CI artifact)
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
no
Does this PR change default behavior?
no