-
Notifications
You must be signed in to change notification settings - Fork 10
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
Modify PhysicsRun2019MCRecon.lcsim to solve a bug #876
Conversation
…ster corrections are applied twice when recon particles by both GBL and KF tracks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The official recommendation for 2019 of the analysis working group is to use KF tracking only. https://confluence.slac.stanford.edu/display/hpsg/5.26.2021+Weekly?preview=/311544557/311546122/210526_kfSummary.pdf
Please change the order of ReconParticleDriver_Kalman and ReconParticleDriver and the configuration so the ecal cluster corrections are based on matching to the KF tracks. I do not mind to making this change for you if you want.
I personally agree with you, Cameron. Please make the change as you suggested. |
The steering file PhysicsRun2019MCRecon_LCIO.lcsim also needs to be modified. |
@normangraf Done |
Thank you. |
Modify PhysicsRun2019MCRecon.lcsim to solve a bug that the Ecal cluster corrections are applied twice when recon particles by both GBL and KF tracks. Meanwhile, following what we did for 2016 MC, pedestals from DB are applied for MC, instead of running pedestal. So EcalRunningPedestal is removed.