- 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
PrimaryVertexCuts: min and max z
Updated on Tue, 2015-09-22 15:23. Originally created by genevb on 2015-09-22 15:23.
Proposal:
Add two data members to the class StDb/idl/VertexCuts.idl and consequently the offline database table Calibrations/tracker/PrimaryVertexCuts:
These will be used by vertex finders to restrict the allowable range in z for vertex searching and positions. It is up to the individual vertex finders to implement usage of these varaibles.
Example need:
The Minuit vertex finder has traditionally used a hardwired limit of |z|<200 cm. The fixed target program would like to use this vertex finder, but extend its range to z beyond -210 cm, where the fixed target was installed. Using the new database table parameters, vertex-finding can be tuned specifically for their data production without affecting any other productions.
The Minuit code can use ZMin == ZMax (as would be returned for old table entries in the database where these variables were not filled) as a condition to fall back to its historical defaults of -200,+200 cm.
________
-Gene
Add two data members to the class StDb/idl/VertexCuts.idl and consequently the offline database table Calibrations/tracker/PrimaryVertexCuts:
float ZMin; // Min z of possible vertex positions float ZMax; // Max z of possible vertex positions
These will be used by vertex finders to restrict the allowable range in z for vertex searching and positions. It is up to the individual vertex finders to implement usage of these varaibles.
Example need:
The Minuit vertex finder has traditionally used a hardwired limit of |z|<200 cm. The fixed target program would like to use this vertex finder, but extend its range to z beyond -210 cm, where the fixed target was installed. Using the new database table parameters, vertex-finding can be tuned specifically for their data production without affecting any other productions.
The Minuit code can use ZMin == ZMax (as would be returned for old table entries in the database where these variables were not filled) as a condition to fall back to its historical defaults of -200,+200 cm.
________
-Gene
»
- genevb's blog
- Login or register to post comments