Alla Maevskaya Alla Maevskaya INR RASINR RAS

ALICE offline weekALICE offline week

20 October 200820 October 2008

T0 offline statusT0 offline status

Trigger timing (before alignment) versus bunch numbersingle shot

for SPD, V0, beam-pickup BPTX, T0 triggers

During physics run, T0physda collects the difference between During physics run, T0physda collects the difference between time on the PMT1 and all others on each side event by event.time on the PMT1 and all others on each side event by event. Using mean of these histograms, collected during 1Using mean of these histograms, collected during 1stst 20000 20000 eventsevents as equalizing shift between channels as equalizing shift between channels calculate 1st particle for both sides and vertex position as

c*(TAbest-TCbest)/2 and write vertex position in histogram for events 20000-50000The preprocessor gets the mean and RMS of these histogramsThe preprocessor gets the mean and RMS of these histograms

(24 time and 1 vertex)(24 time and 1 vertex)and writes it into OCDB to be used in reconstructionand writes it into OCDB to be used in reconstruction - as the value of the shift between the channels for equalizing- as the value of the shift between the channels for equalizing - as shift in vertex position- as shift in vertex position

run type PHYSICS event type PHYSICSrun type PHYSICS event type PHYSICS

OCDB the status of conditions objects final IOCDB the status of conditions objects final I

OCDB - the status of conditions objects OCDB - the status of conditions objects final IIfinal II

Stored in OCDB 4 x 24 TGraphsStored in OCDB 4 x 24 TGraphs• time-amplitude dependence (QTC amplitude)time-amplitude dependence (QTC amplitude)• time-amplitude dependence (LED-CFD amplitude)time-amplitude dependence (LED-CFD amplitude)• amplitude #channel vs MIPs (QTC)amplitude #channel vs MIPs (QTC)• amplitude #channel vs MIPs (LED-CFDamplitude #channel vs MIPs (LED-CFD))

Online during special multi-MIPs Laser Online during special multi-MIPs Laser calibrations runscalibrations runs

run type LASER event type CALIBRATIONrun type LASER event type CALIBRATION

T0 DPsT0 DPs

Usage of DPs - product of long discussions within T0 collaboration:Scaler DPs primarily used for Luminosity study

part of ALICE luminosity project included in DCS distributed project

cross-check of scaler performance from Reference DBall other DPs used for cross-check, monitoring and understanding the

performance of T0

DPs stored to Reference DB t00_ac_scaler_sec[0..31] and scaler_sec[0..31] – T0 scalers:

counts from 12 A-side and 12 C-side PMT counts from OR, TVDC, MPD, Mean timer and Reference point generator

t00_.._hv.. - HV on T0 PMTs t00_.._lv.. - LV on T0 shoeboxes t00_.._cfd.. - threshold and walk on CFDs t00_ac_trm and t00_ac_drm – temperature of TRM and DRM t00_ac_atten – setting of T0 LCS attenuator, recent request of T0 detector

experts

DCS part of preprocessorDCS part of preprocessor

Updated list of T0 DPsSOR and EOR scripts testedall 184 DP retrieved from Amanda server

AliT0Preprocessor - storing results to Reference DB:local tests of new version AliT0DataDCS – to be ported to the coming AliRoot

release and tested at P2

run start & stop and if changed335Cofloat5t00_ac_drm_[00..04]

run start & stop and if changed335Cofloat10t00_ac_trm_[00..09]

120503*10^81/sunsigned int32t00_ac_scaler_[00..31]

3000100.5Vfloat12t00_c_cfd_thre_[00..11]

300010-0.1Vfloat12t00_c_cfd_walk_[00..11]

3000100.5Vfloat12t00_a_cfd_thre_[00..11]

300010-0.1Vfloat12t00_a_cfd_walk_[00..11]

30000.15 6 V float 2t00_c_lv_vmon_[00..01]

30000.9 83uAfloat 2t00_c_lv_imon_[00..01]

3000 0.85 1325 V float 12t00_c_hv_vmon_[00..11]

3000 0.9 83uAfloat 12t00_c_hv_imon_[00..11]

3000 0.15 6 Vfloat 2t00_a_lv_vmon_[00..01]

3000 0.9 83uA float 2t00_a_lv_imon_[00..01]

30000.85 1325 V float 12t00_a_hv_vmon_[00..11]

3000 0.9 83uA float 12t00_a_hv_imon_[00..11]

Update Frequency (s)%

fluct.ValueUnitData type

No. of channels

DCS alias

12050801/sunsigned int32t00_ac_scaler_sec[0..31]

run start & stop and if changed505MIPint1t00_ac_atten

All re

triev

ed

Preprocessor and DA - are these complete, do you Preprocessor and DA - are these complete, do you foresee a major change in the procedures? foresee a major change in the procedures?

Yes, they are complete. Only number of events Yes, they are complete. Only number of events necessary for vertex calculations could be changed necessary for vertex calculations could be changed with beam energywith beam energy

What are the most common failures in theWhat are the most common failures in thepreprocessors/DA operation since December 2007?preprocessors/DA operation since December 2007?

T0 does not register cosmic data, so we can do all T0 does not register cosmic data, so we can do all calibration which will use physic data during data calibration which will use physic data during data taking with laser data. Most problem is switch DA taking with laser data. Most problem is switch DA on/off…..on/off…..

Yes ,

Do you foresee to add new object and if yes what would be the increase in size?

no Location of objects OCDB/reference Input data - do you still miss any of the input

data for the Shuttle preprocessor from DCS (data points), DAQ, HLT?

Now all DCS and DAQ data are retrieved Run types - do you foresee new run types to be

handled by the preprocessor?No, only “PHYSICS” and “LASER” as now

GRP/reco params - do you have implementation for the three defined types of reco params (low/high flux, calibration)?

For no one now

Second order calibration - what are the condition Second order calibration - what are the condition objects, methods and input data necessary for the objects, methods and input data necessary for the second order (refined) calibration?second order (refined) calibration?Will the second order calibration run during the first Will the second order calibration run during the first pass reconstruction or elsewhere? How many of the pass reconstruction or elsewhere? How many of the conditions object will be modified for the second conditions object will be modified for the second pass reconstruction and with what frequency?pass reconstruction and with what frequency?

Now we are not planning 2Now we are not planning 2ndnd order of calibration and order of calibration and 22ndnd pass of reconstruction. But if QA RecPoints will pass of reconstruction. But if QA RecPoints will show that mean reconstructed time is different for show that mean reconstructed time is different for each PMT we will need repeat calibration. And if each PMT we will need repeat calibration. And if mean vertex position will reconstruct in different Z mean vertex position will reconstruct in different Z than ITS vertex we will need redo calibration and than ITS vertex we will need redo calibration and reconstructionreconstruction.

  T

AlignmentAlignment

No T0 overlaps in the ideal, residual and fully misaligned

geometry

Survey data into alignment object (AliT0Align class)

new version to be committed this week

T0-C – last survey: 05.04.2007, available and tested

problems with “VZERO”-”V0” mismatch on the grid

T0-A – last survey 05.06.2008, but soon invalid

survey must be redone once T0-A mounted back

data available and tested (not yet to be put to OCDB)

RAW QARAW QA

During data taking laser calibration with given amplitude will take During data taking laser calibration with given amplitude will take place in big gaps between bunches to check electronicsplace in big gaps between bunches to check electronicsAliT0QAMakerRec::MakeRAW collects 2 sets of histograms: AliT0QAMakerRec::MakeRAW collects 2 sets of histograms: for event type PHYSICS ( only for monitoring)for event type PHYSICS ( only for monitoring)for event type CALIBRATION (for QA )for event type CALIBRATION (for QA )

QA RecPoints QA RecPoints RecPoints QA checks RecPoints QA checks • difference between online (apparatus) and offline mean difference between online (apparatus) and offline mean time after calibration should be stable.time after calibration should be stable.• the difference between reconstructed time on the PMT1 and all others on the difference between reconstructed time on the PMT1 and all others on each side : mean should be 0each side : mean should be 0• for pp runsfor pp runs check that amplitude measured by 2 check that amplitude measured by 2 methods (QTC and LED-CFD) has the same value methods (QTC and LED-CFD) has the same value

QA ESDQA ESD

ESD QA :

T0 writes in ESD T0 signal (T0A+T0C)/2 Vertex position (T0A-T0C)/2

AliT0QAChecker looks at RMS of these AliT0QAChecker looks at RMS of these histograms and alarms if it is more then 3 histograms and alarms if it is more then 3 channels (75 ps)channels (75 ps)

Reconstruction resultsReconstruction resultsrun47696 run47696