1 / 9

Alignment using high Pt tracks

Alignment using high Pt tracks. In parallel (or together) with R-T calibration stream, a track alignment stream has to be setup for the following alignment tasks:. Small w.r.t. large barrel chambers BEE w.r.t. EC chambers Endcap – Barrel BIS8 w.r.t. BIS7 Inner tracker – Muon spectrometer

garin
Download Presentation

Alignment using high Pt tracks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Alignment using high Pt tracks In parallel (or together) with R-T calibration stream, a track alignment stream has to be setup for the following alignment tasks: • Small w.r.t. large barrel chambers • BEE w.r.t. EC chambers • Endcap – Barrel • BIS8 w.r.t. BIS7 • Inner tracker – Muon spectrometer • TGC w.r.t. EC MDT chamber. Not discussed here High pT means: Selected by High pT Level1 trigger + level2 cut pT>20GeV For items 1-4, the target precision transverse to the track direction in the bending plane is of the order 30 mm. For item 5, a precision of the order 200mm in the toroid bending plane is sufficient. Not discussed here: alignment with field off (or cosmic) straight tracks (considered as an offline “one time” task) C.Guyot Saclay 30/112005

  2. Small-Large barrel chambers Track selection at level 2: High Pt muon in full overlap (BIS-BIL-BMS-BMLS-BOS-BOL tracks) Selected tracks rate at L=1033: ~3 Hz (barrel, 200 towers) Frequency : every 2 hours (~100 segments per chamber overlap) CPU requirement: ~ 3 PC (~3 Hz with ~1s per track reconstruction) Comments : optical alignment and track information are correlated in the final fit DCS condition database data have to be available ATHENA Track reconstruction in the large chambers + Segments in the small chambers Overlap Track digits Segments in the small chambers: Predicted from large Reconstructed in small ASAP optic ASAP fitter optic + segments Optical sensors data A lines combined A lines optic

  3. STANDARD BARREL SECTOR BARREL FOOT SECTOR Trigger zone for overlaping tracks MDT overlap

  4. BEE / EC chambers Track selection at level 2: High Pt muons in the overlap EIS-BEE-EMS-EOS Selected tracks rate at L=1033: ~10Hz (1.45<|h|<1.70, 30% of 2p) Frequency : every 2 hours (~1000 segments per BEE in the edge zones) CPU requirement: ~ 3 PC ( ~3Hz with ~1s per track reconstruction) Comments : Only tracks crossing the edges of BEE chambers should be considered Edge zone Excluded zone BEE2 BEE1 Track reconstruction in EIS-EMS-EOS + Segments in BEE Segments in BEE: Predicted from EI-EM-EO Reconstructed Overlap Track digits ARAMYS optic Segment fitter: Fit BEE positions A lines BEE Optical sensors data A lines optic

  5. Endcap / Barrel (1) Track selection at level 2: High Pt muons in the overlap BIL6-EIL4-BML6-BOL6 Selected tracks rate at L=1033: ~4Hz (Dh~0.05, Df~60% of 2p) Frequency : every 2 hours (~1000 segments per EIL4) CPU requirement: ~ 4 PC ( ~4Hz with ~1s per track reconstruction) Comments : The final fit involves both barrel and EC optical data in additions to the segments in EIL4. The fitted objects could be barrel layers + EC bars. With EEL: tracks in the overlap BIL6-EIL4-EEL2-EML5 also possible.

  6. Endcap / Barrel (2) Track reconstruction in the barrel + Segments in EIL4 Overlap Track digits Segments in EIL4: Predicted from Barrel track Reconstructed from digits ASAP optic Global fitter optic + segments A lines combined Optical sensors data A lines optic ARAMYS optic

  7. BIS8 / BIS7 Track selection at level 2: High Pt muons in the overlap BIS7-BIS8 Selected tracks rate at L=1033: ~1Hz (Dh~0.05, Df~20% of 2p) Frequency : every 4 hours (~1000 segments per BIS8) CPU requirement: ~ 1 PC ( ~1Hz with ~1s per segment reconstruction) Comments : The segments could the same as those used for R-T calibration BIS7 BIS8 Fit of BIS8 position w.r.t. BIS7 Segments Reconstruction In BIS7 and BIS8 Overlap Tracks digits Segments in BIS7 and BIS8 A lines of BIS8 A lines of BIS7

  8. Muon spectrometer w.r.t. inner detector Event selection at level 2: Event with a very high Pt muons (e.g. > 50 GeV) both in ID and muon spectro Selected event rate at L=1033: >10Hz (from W/Z events) + pre-selection Frequency : every 6 hours (~10000 tracks required to achieve the precision) CPU requirement: ~ 5 PC ( ~0.5 Hz with ~1s per track reconstruction) Comments : The final fit involves both barrel and EC optical data in additions to the segments in BI/EI. The fitted objects could be barrel layers + EC bars. Track recons in the ID + extrapolation to BI/EI Global fitter optic + segments Digits in ID Extapolated segments in BI/EI New A lines Digits in Muon spectro Stand alone track recons In the spectro Segments in BI/EI ASAP optic Optical sensors data A lines optic ARAMYS optic

  9. Conclusions/comments • At lower luminosity (or if a detailed analysis shows tat the rates are much lower than anticipated), tracks selected at level2 with a lower pT cut (e.g. >10GeV) can be used. • Total rate of selected events for alignment with tracks should be ~ 20Hz (L=1033) • CPU time is dominated by the full track reconstruction: ~20-30 PC are required (<10% of calibration load) • As expressed in the updated LOI, these alignment tasks would be worked out in tier-2 calibration centers. • The various tasks could be split as follow: • Optical alignment (ASAP/ARAMYS) : at ATLAS Point1 • Track + segment reconstruction: in Tier2 • Combined fits using segments + optical information : Tier2 • Alignment specific developments will start at MPI Munich tier2. • A collaboration with Saclay has been started to cover the issues of trigger rates in the alignment stream (detailed study with full MC simulations), specific track/segment reconstruction, combined track/optical sensors fits,… • DC3/CSC simulation data with in a step first ideal detector geometry and later with “as built” detector geometry should be used as a starting point. Realistic rates and efficiencies have to be worked out. • EDM should be updated to include the notion of extrapolated segment

More Related