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

Add driver that performs SVT cluster position smearing #1050

Open
bloodyyugo opened this issue Sep 20, 2024 · 2 comments · May be fixed by #1075
Open

Add driver that performs SVT cluster position smearing #1050

bloodyyugo opened this issue Sep 20, 2024 · 2 comments · May be fixed by #1075
Assignees

Comments

@bloodyyugo
Copy link
Contributor

Add a driver to be used (optionally) to smear the local SVT cluster positions in MC.

The goal is to better duplicate the hit residuals and track chi2 seen data but the plan is to start simple and add complexity.

  • step 0: single smearing factor (or absolute number) for all clusters over all layers and nHits
  • step 1: separate factors for 1 & 2 hit clusters
  • step 2: also separate by layers in some way (eg L0+L1 vs the rest or L0+L1, L2+L3, outer layers)
  • step 3: position dependent smearing ... we would need some guidance from data for this

I don't plan to include everything in this issue, probably just up to step 2.

@bloodyyugo bloodyyugo self-assigned this Sep 20, 2024
@bloodyyugo
Copy link
Contributor Author

It would be even better to move the smearing down to the SVT hit making level, based on some real physical basis. TKNelson has some experience with tuning MC in this way, so he will consult on that. Plan for that to be next project after this.

@bloodyyugo
Copy link
Contributor Author

Long time, no update. Here it is.

An example steering file (for 2016) is at:
steering-files/src/main/resources/org/hps/steering/recon/PhysicsRun2016FullReconMC_KF_Killer_Smearer.lcsim

Smearing values are stored as a resource in: org/hps/recon/tracking/svtTimeAndPositionSmearing/

I've implemented svt cluster smearing in org.hps.recon.tracking.StripHitSmearer.java. Default smearing (in steering file above) is 8um for all sensors. This gives decent matching between data/MC chi2, d0, z0 and hit residuals and smears out the FEE peak momentum some (not quantified, need to do this at some point). See slides 6-9 in this talk: https://indico.slac.stanford.edu/event/9304/contributions/10517/attachments/4694/12677/hps-anaws-tweaking-oct8-2024.pdf

Timing currently is smeared at the FittedHit level...i.e. after the raw hit is fit, I smear the fitted t0. Current defaults are 4ns for the thin sensors, 2ns for normal ones. This does pretty well to match data/mc for hit time distributions but the track time is still narrow. Probably have to add a dedicated track time smearing.

@bloodyyugo bloodyyugo linked a pull request Jan 8, 2025 that will close this issue
@bloodyyugo bloodyyugo linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant