Alignment software update For the review we worked

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

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 ( Pixel. On. Ladders, Ladders. On. Sectors, etc … ) – Check that St. Pxl. Db. Maker (maker that reads these tables and fill on the fly the rotation matrices) runs well 2/7/13 new wave of software : alignment 2

2. Hit/Hit collection • We used St. Rnd. Hit and St. Rnd. Hit. Collection where we added the local position. • Now we have to use St. Pxl. Hit and St. Pxl. Hit. Collection : – For this, we can use , even the codes are under or near reviewed, Mustafa’s Pixel. Fast. Maker and Hao’s St. Pxl. Hit structure – I guess the final structures will be roughly the same [after reviews] so we can start from there 2/7/13 new wave of software : alignment 3

3. Tracking • Sti. Pixel. Detector. Builder and St. Pixel. Hit. Loader have to be changed: • Sti. Pixel. Detector. Builder : 1. new geometry ( definition/name of active and inactive volumes have changed ) 2. New numbering : layer/ladder sector/ladder/sensor • Sti. Pixel. Hit. Loader : 1. Should retrieve hits from St. Pxl. Hit. Collection with St. Pxl. Hit format 2. New numbering 2/7/13 new wave of software : alignment 4

4. Alignment code • It should use : – St. Pxl. Hit from St. Pxl. Hit. Collection – retrieve updated geometry tables – Will check numbering scheme 2/7/13 new wave of software : alignment 5