1. Alignment software update For the review, we worked with some old structures. Some changes are now needed : 1.Geometry 2.Hit definition / Hit collection Definition 3.Tracking 4.Alignment code 2/7/131new wave of software : alignment

2. 1. Geometry We used a version of the pixel geometry where the sensors were placed approximately ( originally there were only full active ladders, no sensors ) to get the rotation matrices for each of them Now that we have the updated geometry : – Get the proper sensor placement ( rotation matrices ) – Produce geometry tables ( PixelOnLadders, LaddersOnSectors,etc … ) – Check that StPxlDbMaker (maker that reads these tables and fill on the fly the rotation matrices) runs well 2/7/132new wave of software : alignment

3. 2. Hit/Hit collection We used StRndHit and StRndHitCollection where we added the local position. Now we have to use StPxlHit and StPxlHitCollection : – For this, we can use, even the codes are under or near reviewed, Mustafa’s PixelFastMaker and Hao’s StPxlHit structure – I guess the final structures will be roughly the same [after reviews] so we can start from there 2/7/133new wave of software : alignment

4. 3. Tracking StiPixelDetectorBuilder and StPixelHitLoader have to be changed: StiPixelDetectorBuilder : 1.new geometry ( definition/name of active and inactive volumes have changed ) 2.New numbering : layer/ladder  sector/ladder/sensor StiPixelHitLoader : 1.Should retrieve hits from StPxlHitCollection with StPxlHit format 2.New numbering 2/7/134new wave of software : alignment

5. 4. Alignment code It should use : – StPxlHit from StPxlHitCollection – retrieve updated geometry tables – Will check numbering scheme 2/7/135new wave of software : alignment