Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s1singlescatter update #172

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

s1singlescatter update #172

wants to merge 3 commits into from

Conversation

jingqiangye
Copy link
Contributor

I propose an updated S1SingleScatter cut for both SR1 and SR2 in PAX6101. See details in the note. I can also present it in telecon if necessary.

Copy link
Contributor

@JelleAalbers JelleAalbers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice note Jingqiang! I think it would be an interesting presentation, but up to you and the X1T coordinators. The cut seems fine to me.

Since the afterpulse-induced acceptance drop is much larger in SR2 than SR1, I would guess the amount of afterpulses is much larger in SR2 than SR1. If so, could this have any other effects, e.g. on the S1 detection efficiency or the acceptance of other cuts? Is the waveform simulator (used for S1 efficiency and other things) already updated with the new AP intensities?

@jingqiangye
Copy link
Contributor Author

jingqiangye commented Sep 5, 2019

Thanks Jelle! I'll contact 1T coordinator.

Actually from Fig. 8 in the note, cut acceptance drop in SR2 is slightly worse than SR1, I think it's from increasing after pulse.

The afterpulses may affect s1 detection efficiency if AP and s1 are merged and identified as S2. S1Width cut may have but a very limited affect, as S1Width requirement is pre-applied in PAX6101 now.

I have no idea about waveform simulator, should contact the expert. But yeah it'll be nice to add it if haven't.

@jingqiangye
Copy link
Contributor Author

As pointed out by @ershockley , we need to set a threshold for largest other s1. See details in later part in this section or Fig. 6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants