Summary Offline Readiness

1
Summary Offline Readiness

• Christoph Blume
• TRD Status Meeting, 30.-31.3. 2007

2
Activities

• TRD code consolidating (hopefully)
• But lots of activity right now!
• People Alexandru, Christian, Christoph, Dariusz,
  Ken, Marian, Mateusz, MinJung, Raphaelle, Silvia,
  Sylwester, Yifei, ...
• Progress is being monitored by Project Planning
  Tool
• http//pcaliproject.cern.ch8080/alice/index.php

3
Activities

• (Almost) last chance to get code into proper
  shape before data taking
• Some parts are still being implemented
• Raw data reading
• Transformation of reference systems
• Tracklets for reconstruction
• Update of PID scheme
• General revision of the code
• CPU time and memory consumption
• Code quality
• Validation
• Documentation needed !
• Aim to finish big pertubations by end of April
• Production release

4
Geometry

• General revision of TRD geometry in AliRoot
• Based on first installed supermodule
• Updates
• Services and support frame
• Material in chambers
• Total weight of SM increases by 250kg
• Not included Services outside of acceptance
  region
• E.g. cooling manifolds, HV boxes, cooling and
  power bus bars are in reality longer than TRD
  mother volume
• AliRoot 1541kg ? measured 1700kg

5
Alignment Simulation Awareness

• (Mis-)Alignment based on TGeoManager
• Consistently implemented in
• Hit generation
• Digitization (pad plane position)
• Alignable objects
• Single ROC
• Supermodule
• Symbolic names introduced
• Digits generation
• Now done in local ROC reference system
• Only depends on
• No hardwired numbers any more

6
Alignment Reconstruction Awareness

• Is implemented (in principle) since a while
• New development Transformation between local
  reference system and alignable volume
• Local RS of cluster coordinates ? RS of alignable
  volume
• Will be done via TGeoHMatrix
• Revision of current reference systems
• Cluster coordinate system not really natural
  choice
• Inconsistencies
• Procedures can be simplified
• However Delicate task!

7
Calibration (Raphaelle)

• OfflineHLT
• Quite advanced status
• DA available and will be submitted to CVS soon
• Identical algorithms
• Uses clusterizer and stand alone TRD tracking
• Gain factors, T0, drift velocities, PRFs ...
• DAQ
• First DA developed, based on HLT version
• However Basic differences since based on raw
  data input
• Tracklet information needs to be reconstructed
• Will cause divergence of algorithms
• Accuracy unclear
• Considered as fall back solution (accepted by
  offline group)

8
DCS Parameters

• Names of DCS archive datapoints defined (Dariusz)
• Open issue
• Preprocessor algorithms and FXS outout files
• Will be close to TPC solution
• E.g. AliSpline for temperatures, drift
  velocities from monitors, etc.
• However, not essential data. Mostly
  monitoring purposes
• Needs someone to take care off ...

9
Reconstruction (Sylwester)

• Ongoing task (Re-)introduction of tracklets
• Not foreseen in newly introduced general track
  parametrization (Yuri)
• Natural way to take correlations between clusters
  into account
• Right now Error parametrization not correct
• Track ?2 currently meaningless

10
Raw Data (Ken, Christian, MinJung)

• Implementation of new raw data format (i.e. SM 1
  data format) done and tested (submitted to HEAD).
• No zero suppression
• Commissioning data can be read
• Raw data version with zero suppression
• Implementation ongoing (first version ready)
• Aim to finalize for pre-production release
• MCM tracklets will be part of raw data
• Raw data embedding
• Do be done on SDIGITS level
• Needs to be looked at carefully

11
(No Transcript)
12
Summary

• Offline code approaching a ground state
• Few major changes/additions still ongoing
• Should be finalized for production release (end
  of April)
• Validation, QA, performance (CPU memory)
  important issue now

13
(No Transcript)
14
Cluster Coordinates (Currently)
Y0
X0
Z0
15
Cluster Coordinates (Proposed)
Put Y0 and Z0 relative to single
ROC, corresponding to alignable volume
Y0
X0
(for Z0 already being done in AliTRDtrackerTrans
form() )
16
Raw Data With Zero Suppression
New MCM tracklets part of raw data
stream ? not needed in trigger simulation any
more
17
Raw Data Tracklets in AliTRDmcm
18
Reconstruction PID (Alexandru)

• Ongoing investigations to improve e/?
  separation
• Impending changes
• Use 2 slices of drift amplification
  region (amplitude position of TR)
• Will use 2-dim. histograms for probability
  distributions
• Generate new probability distributions for
  pre-production release

19
HLT (Mateusz)

• Philosophy Use as much as possible from offline
  code
• E.g. algorithm of clusterizer AliTRDclusteriz
  erV1HLT public AliTRDclusterizerV1
• Calibration classes can be used as in offline
• Offline code will be modified to be usable on HLT
• E.g. no AliRunLoader
• Status
• TRD local reconstruction on HLT running
• Some testing an optimization ongoing
• Calibration running
• Histograms produced
• Calibration DB accessible
• Code to be submitted in 2 weeks

20
Event Display (Alexandru, MinJung)
21
Raw Data Embedding

• Embedding of simulated data in measured raw data
• How will this be done ?
• Will it be done on sdigits (i.e. idealized raw
  data) level as up to now ?
• Or on the real raw data level ?
• Both possible, but need to include all effects
  properly ! (e.g.
  zero suppression, digital filtes, baselines, ...)

22
Event Display Raw Data Display

• Display of digits with EVE directly from
  DATE/ROOT raw data
• Uses same Raw2Digits() as used for reconstruction
  and online monitoring
• Data from commissioning of first SM last Oct. (M.
  Kweon)