- genevb's home page
- Posts
- 2024
- 2023
- 2022
- September (1)
- 2021
- 2020
- 2019
- 2018
- 2017
- December (1)
- October (3)
- September (1)
- August (1)
- July (2)
- June (2)
- April (2)
- March (2)
- February (1)
- 2016
- November (2)
- September (1)
- August (2)
- July (1)
- June (2)
- May (2)
- April (1)
- March (5)
- February (2)
- January (1)
- 2015
- December (1)
- October (1)
- September (2)
- June (1)
- May (2)
- April (2)
- March (3)
- February (1)
- January (3)
- 2014
- 2013
- 2012
- 2011
- January (3)
- 2010
- February (4)
- 2009
- 2008
- 2005
- October (1)
- My blog
- Post new blog entry
- All blogs
DB table for TPC Padrow T0s
Updated on Mon, 2009-05-18 15:27. Originally created by genevb on 2009-05-18 15:22.
TPC calibration analyses have observed timing offsets as a function of padrow for clusters which were found online. While pad-to-pad T0 variances are handled by the online cluster finder, the variations between padrows are not (see this plot of padrow-by-padrow variations from sector 7 which demonstrate offsets corresponding to RDO regions at padrows 14-21 and 22-29).
To this end, we propose to add a table at Calibrations_tpc / tpcPadrowT0 which will need a single column for:
float T0[45]; /* T0s per padrow */
I have placed this declaration into an idl file at StDb/idl/tpcPadrowT0.idl in CVS, which should appear in DEV in tonight's AutoBuild. The table should use the same 24 elementIDs labeled as "Sector" ("SectorIDs") used frequently in the TPC tables.
Thanks,
-Gene
»
- genevb's blog
- Login or register to post comments