-
Notifications
You must be signed in to change notification settings - Fork 14
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
Include photon purity #17
Comments
Description of the method. |
Documenting the email exchange with Andreas Us: Regarding the measurement of the photon purity for the photon CR: in the latest analysis I remember, there were two ways of measuring it. One could either use the distribution in the photon isolation variable, or in EGamma shower variables. Both methods were shown to give the same results. Are you still going to use both, or are you using only one now? Andreas: Just now, we've seen the first results from the isolation-based measurement. This is still a bit WIP as we see some differences between a) sieie measurements by different groups and b) the sieie and isolation-based measurements. We will decide what to do once we Us: Do you have the photon purity study implemented in coffea? In that case, can you point me to your photon purity processor? What do you use to perform the template fit? Do you do it in combine? Andreas: The purity processor is here: https://github.com/bu-cms/bucoffea/blob/master/bucoffea/photon_purity/photonPurityProcessor.py Us: Do you perform the photon purity measurement separately per year? Us: If I understand correctly you store the photon purities in this file: Would you mind pointing me to the part of the code that uses this file in input and applies the purities to derive the shape/rate of QCD in the photon CR? Andreas: to avoid binning effects, I perform an exponential fit to the individual points stored in the file you point out. This is shown in Fig. 14 of [1]. [1] http://cms.cern.ch/iCMS/jsp/db_notes/noteInfo.jsp?cmsnoteid=CMS%20AN-2020/042 |
No description provided.
The text was updated successfully, but these errors were encountered: