ZDC Offline Status Report

13
ZDC Offline Status Report C. Oppedisano

description

ZDC Offline Status Report. C. Oppedisano. Centroid over ZNs: data. y. 4. with. x. 1 2. Centroid: vertical collimator effect. y. Vertical collimator (TCTVB)  jaws aperture 15 mm, placed at x=-2.7 cm, on both sides w.r.t. the IP. 4. x. 1 2. No. of times the PM is ON. - PowerPoint PPT Presentation

Transcript of ZDC Offline Status Report

Page 1: ZDC Offline Status Report

ZDC Offline Status ReportC. Oppedisano

Page 2: ZDC Offline Status Report

ZDC

2C. Oppedisano

Centroid over ZNs: data

3 41 2 x

y

2/1ii

ZNi

PMw

1.75} 1.75,- 1.75, {-1.75, = [4]x

4

1ii

4

1ii

ZNi

centroidi

w

wxx with

ALICE Offline week, 16 March 2010

Page 3: ZDC Offline Status Report

ZDC

3C. Oppedisano

Centroid: vertical collimator effect

No.

of ti

mes

the

PM is

ON

PMC PM1 PM2 PM3 PM4 PMC PM1 PM2 PM3 PM4

3 41 2 x

y

Vertical collimator (TCTVB) jaws aperture 15 mm, placed at x=-2.7 cm, on both sides w.r.t. the IP

The towers covered by the collimator jaws have less counts

ALICE Offline week, 16 March 2010

Page 4: ZDC Offline Status Report

ZDC

4

Dipole effect on ZDC data

ALICE Offline week, 16 March 2010

C. Oppedisano

the acceptance for the hadronic calorimeters show different features depending on the ALICE dimuon field value (when dipole is ON the ZN response is ~25% lower w.r.t. the dipole OFF)

the “internal” crossing angle due to ALICE dipole and compensator fields is ~ 2 mrad (no external crossing angle since, apart from the compensators, the LHC magnets were all off)

for neutral particles the production angle is reflected in the detected spatial distribution

ZNA

Dipole OFF

Dipole ON

Page 5: ZDC Offline Status Report

ZDC

5

Simulation

ALICE Offline week, 16 March 2010

C. Oppedisano

The collimator jaw volumes are described in the ZDC geometry (AliZDCv3::CreateBeamLine()) jaws aperture and center can be set at config level, using the following AliZDC methods:

void SetVCollAperture(Float_t aperture);void SetVCollCentre(Float_t centre) ;

The length of the LHC luminometer, placed in front of ZN, is now a configurable parameter since in pp it consists of a Cu block 15 cm long, while in A-A it could be reduced to 3 cm or even removed if the machine will use the ZDC as luminosity monitors:

void SetLumiLength(Float_t length);

To correctly simulate the crossing given by dipole+compensators, G. Luparello is working on the implementation of CROSSING ANGLE (and beam divergence) at generator level. Currently the new method implemented in AliGenMC is under test:

void BeamCrossingAngle();

Page 6: ZDC Offline Status Report

ZDC

6C. Oppedisano

ZNC spectra

March 2010

DATAcommon PM PM 1 PM2 PM3 PM4

common PM PM 1 PM2 PM3 PM4MC

Page 7: ZDC Offline Status Report

ZDC

7C. Oppedisano

ZPC spectra

March 2010

DATAcommon PM PM 1 PM2 PM3 PM4

common PM PM 1 PM2 PM3 PM4MC

Page 8: ZDC Offline Status Report

ZDC

8C. Oppedisano

ZNA spectra

March 2010

DATAcommon PM PM 1 PM2 PM3 PM4

common PM PM 1 PM2 PM3 PM4MC

Page 9: ZDC Offline Status Report

ZDC

9C. Oppedisano

ZPA spectra

March 2010

ZNAcommon PM PM 1 PM2 PM3 PM4

common PM PM 1 PM2 PM3 PM4ZPA

we are investigating the problem that causes the loss of charged particle signal in ZPA

Page 10: ZDC Offline Status Report

ZDC

10

Shuttle and DAs

ALICE Offline week, 16 March 2010

C. Oppedisano

RUN TYPE SOURCE DA OUTPUT

All the remaining MON MAPPING ZDCChMapping.dat

STANDALONE_PEDESTAL LDC ZDCPEDESTALda.cxx ZDCPedestal.datZDCPedHisto.root

STANDALONE_LASER LDC ZDCLASERda.cxx ZDCLaserCalib.datZDCLaserHisto.root

CALIBRATION_EMD LDC ZDCEMDda.cxx ZDCEnergyCalib.datZDCTowerCalib.dat

CALIBRATION_MB LDC ZDCCALIBMBda.cxx ZDCMBCalib.root

the 1st 3 DAs are succesfully running at P2 the latter 2 will be used for A-A data

The Shuttle is correctly operating for the ZDC the Shuttle can process only data written on MSS

Page 11: ZDC Offline Status Report

ZDC

11

ADD detector in ZDC offline

ALICE Offline week, 16 March 2010

C. Oppedisano

In January the ADD (ALICE Diffractive Detector) modules have been added to the ZDC readout: 1 ADC (same model as the ZDC ones) + 1 TDC

The DA and the OCDB object have been updated in order to include also the mapping for the new detector

From the MAPPING DA output:

ZDC MAPPING program started ------ AliZDCRawStream -> Reading mapping from StartOfData event ------ ******** GEO 0, mod. type 1, #ch. 24 Mapping DA -> 0 ADC: mod 0 ch 0, code 12 det 1, sec 0 Mapping DA -> 1 ADC: mod 0 ch 1, code 13 det 1, sec 1 [... all the ZDC mapping data...]******** GEO 4, mod. type 1, #ch. 8 the 4 ADD ADC channels!!! Mapping DA -> 48 ADC: mod 4 ch 0, code 103 Mapping DA -> 49 ADC: mod 4 ch 1, code 104 Mapping DA -> 50 ADC: mod 4 ch 2, code 105 Mapping DA -> 51 ADC: mod 4 ch 3, code 106

AliZDCRawStream class has been updated in order to correctly decode the new data format

4 ADC modules for the ZDC + 1 TDC for the ZDC1 ADC for ADD + 1 TDC for ADD

No changes at higher level (Reco, ESD…) at least for the moment.

Page 12: ZDC Offline Status Report

ZDC

12

Offline calibration

ALICE Offline week, 16 March 2010

C. Oppedisano

An algorithm for the inter-calibration of hadronic PTMs is under study. Presently A. De Falco is testing the algorithm on ESD from December data taking.

This algorithm is a good candidate to enter in the offline calibration framework.

input: ESD dataoutput: OCDB object AliZDCTowerCalib

Once the needed parameters will be tuned we will be ready to implement it as an offline

calibration task.

Page 13: ZDC Offline Status Report

ZDC

13

Savannah bugs

ALICE Offline week, 16 March 2010

C. Oppedisano

bug #63223: ZDC preprocessor: W-AliZDCDataDCS::ProcessData: Alias 'xxx 'not foud

************ Alias: ZDC_ZNA_POS.actual.position has 4 DP values collected ************ Alias: ZDC_ZPA_POS.actual.position has 4 DP values collected ************ Alias: ZDC_ZNC_POS.actual.position has 4 DP values collected ************ Alias: ZDC_ZPC_POS.actual.position has 4 DP values collected ************ Alias: ZDC_ZNA_HV0.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZNA_HV1.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZNA_HV2.actual.vMon has 3 DP values collected ************ Alias: ZDC_ZNA_HV3.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZNA_HV4.actual.vMon has 3 DP values collected ************ Alias: ZDC_ZPA_HV0.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZPA_HV1.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZPA_HV2.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZPA_HV3.actual.vMon has 2 DP values collected ************ Alias: ZDC_ZPA_HV4.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZNC_HV0.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZNC_HV1.actual.vMon has 6 DP values collected W-AliZDCDataDCS::ProcessData: Alias ZDC_ZNC_HV2.actual.vMon not found! ************ Alias: ZDC_ZNC_HV3.actual.vMon has 4 DP values collected ************ Alias: ZDC_ZNC_HV4.actual.vMon has 4 DP values collected

In July 2008 I addressed the problem of NO DP FOUND BY THE Shuttle to DCS experts.Last February thanks to P. Chochula’s help (it was a DCS problem), the problem was solved for all but the ZDC_ZNC_HV.actual.vMon alias which is still not found...