- bouchet's home page
- Posts
- 2016
- 2015
- December (1)
- November (3)
- October (2)
- September (2)
- August (2)
- June (2)
- April (5)
- March (2)
- February (3)
- January (2)
- 2014
- December (2)
- November (2)
- October (3)
- September (2)
- August (3)
- July (1)
- June (3)
- May (6)
- April (6)
- March (1)
- February (2)
- January (1)
- 2013
- December (2)
- November (3)
- October (3)
- September (4)
- August (1)
- July (1)
- May (4)
- April (6)
- March (4)
- February (3)
- 2012
- 2011
- December (2)
- November (2)
- October (4)
- September (1)
- August (2)
- July (6)
- June (2)
- May (3)
- April (3)
- March (2)
- 2010
- 2009
- December (2)
- November (1)
- October (3)
- September (1)
- August (1)
- July (1)
- June (2)
- April (1)
- March (2)
- February (2)
- January (1)
- 2008
- My blog
- Post new blog entry
- All blogs
instructions for StPxlDbMaker
1) Introduction
This maker is used to calculate the rotations matrices associated to each PXL sensors.
Rotation matrices are used for global(STAR) to local(SENSOR) transformation.
The make uses geometry tables (for now ideal tables from simulations) to place the PXL on IDS, each PXL sector on Half ,etc ...
The relationship between tables and their meaning is below :
2) tables
a) gen
For now : Tpc2Global, Ids2Tpc, Pxl2Ids, DShell2Ids, Sector2DShell are unitary matrix. It means there is no rotation and no translation.
These are placeholders for future measurements.
b) Ladder2Sector table
This table has 40 entries ( --> # of ladders ) and place each ladder in (X,Y) coordinates
c) Sensor2Ladder
This table place the 10 sensors (of each ladder) along the Z coordinate
It has 400 entries (10sectors * 4 ladders * 10 sensors) which are recognized later in the code by their Id :
You also need to have in the directory where you run the BFC chain a StarDb directory with the following tree.
The maker access locally this directory to find the tables :
The How-to remains almost the same. The only correction ( pointed by Hao during the meeting) is the PXL BFC option missing in the chain above.
The 2 BFC options to include the PXL in tracking are below :
UML diagram of the StPxlDbMaker class (test, not sure about gStPxDbMaker pointer representation)
This maker is used to calculate the rotations matrices associated to each PXL sensors.
Rotation matrices are used for global(STAR) to local(SENSOR) transformation.
The make uses geometry tables (for now ideal tables from simulations) to place the PXL on IDS, each PXL sector on Half ,etc ...
The relationship between tables and their meaning is below :
2) tables
a) gen
For now : Tpc2Global, Ids2Tpc, Pxl2Ids, DShell2Ids, Sector2DShell are unitary matrix. It means there is no rotation and no translation.
These are placeholders for future measurements.
b) Ladder2Sector table
This table has 40 entries ( --> # of ladders ) and place each ladder in (X,Y) coordinates
c) Sensor2Ladder
This table place the 10 sensors (of each ladder) along the Z coordinate
It has 400 entries (10sectors * 4 ladders * 10 sensors) which are recognized later in the code by their Id :
/* id = 1000 * sector + ladder * 100 + sensor with 1<=sector<=10 1<=ladder<=4 1<=sensor<=10 id goes from 1101 to 10410 */
3) how-to
a) code
To run this maker ,StRoot/StBFChain/BigFullChain.h has to include pxlDb option.
{"Event" , "","","MakeEvent", "","","Request to initialize event",kFALSE},
{"pxlDb" ,"pxlDb","","tpcDb","StPxlDbMaker","StPxlDbMaker","Load and run PxlDbMaker", kFALSE},
{"pxlFastSim","","","StMcEvent,StEvent"
, "StPxlSimMaker","StPxlSimMaker","FastPixelSimulator",kFALSE},
Then when running the BFC chain, the maker should be called prior the reconstruction in the pxlFast maker
root4star -b -q 'StRoot/macros/bfc.C(1,10,"y2013,AgML,ITTF,Sti,tpcI,TpcFastSim,pxlDb,pxlFastSim,-ssdfast,VFMCE,
McEvent,geant,IdTruth,fzin,NoSvtIt,NoSsdIt,StiPulls,Bana,tags,clearmem,evout,McEvOut,MiniMcMk,McAna,
MakeEvent","debug.fz")
b) TablesYou also need to have in the directory where you run the BFC chain a StarDb directory with the following tree.
The maker access locally this directory to find the tables :
StarDb/Geometry/pxl/ PxlHalfOnPxl.y2013.C PxlIdsOnTpc.y2013.C PxlLaddersOnSectors.20130201.C PxlPstOnIds.y2013.C PxlPxlOnPst.y2013.C PxlOnGlobal.y2013.C PxlSectorsOnHalf.y2013.C PxlSensorsOnLadders.y2013.C
04/11/2013 : update after Calib. meeting (04/07/2013)
Updated version of the maker is at :
/star/institutions/ksu/bouchet/PxlDbMaker_v2/StRoot/StPxlDbMaker
Changes :
- tables name are updated according the templates in CVS
- added timestamp according to simulation : *.20121215.C (see Jerome's email)
|-StarDb |---Geometry |-----pxl |------idsOnTpc.y2013.C |------pxlHalfOnPxl.20121215.C |------pxlOnPst.20121215.C |------pxlSensorOnLadder.20121215.C |------pstOnIds.20121215.C |------pxlLadderOnSector.20121215.C |------pxlSectorOnHalf.20121215.C
The How-to remains almost the same. The only correction ( pointed by Hao during the meeting) is the PXL BFC option missing in the chain above.
The 2 BFC options to include the PXL in tracking are below :
root4star -b -q 'StRoot/macros/bfc.C(1,10,"y2013,AgML,ITTF,Sti,tpcI,StiRnD,PixelIT,TpcFastSim,pxlDb,pxlFastSim,-ssdfast,VFMCE, McEvent,geant,IdTruth,fzin,NoSvtIt,NoSsdIt,StiPulls,Bana,tags,clearmem,evout,McEvOut,MiniMcMk,McAna, MakeEvent","debug.fz")
UML diagram of the StPxlDbMaker class (test, not sure about gStPxDbMaker pointer representation)
Groups:
- bouchet's blog
- Login or register to post comments