forked from cms-sw/cmssw
-
Notifications
You must be signed in to change notification settings - Fork 0
results of the comparison between AlCaBeamSpotProducer and BeamSpotProducer
sarafiorendi edited this page May 12, 2015
·
2 revisions
I can only compare LumiByLumi results for variables extracted from d0_phi fit (PVfitter results not saved in the ntuple, so far I didn't managed to add another ttree to the edm file)
Some results are here
For the IOV definition, the results are:
AlCaBeamSpotManager (note the the end_lumi is not included in the IOV):
Weighted BeamSpot will span lumi 500 to 587
Weighted BeamSpot will span lumi 587 to 658
Weighted BeamSpot will span lumi 658 to 702
Weighted BeamSpot will span lumi 702 to 703
Weighted BeamSpot will span lumi 703 to 737
Weighted BeamSpot will span lumi 737 to 797
Weighted BeamSpot will span lumi 797 to 871
BeamSpotMerge.py + DCS Json:
[(500, 586), (587, 657), (658, 701), (702, 702), (703, 736), (737, 796), (797, 870), (871, 900)]
- Instructions for ReReco
- BS parameters for MC production & upload to CondDB
- Talks
- Useful links
- Notes for BS fit on VdM scans
- Notes for error scale computation
- Begin of run checks
- DQM and PCL beam spot fits
- BS for FTV
- BS Trends Plots
- Payloads log 2015
- Payloads log 2016
- Payloads log 2017
- Payloads log UL2017
- Payloads log 2018
- Payloads log 2019
- Payloads log 2022
- Payloads log 2023