1 / 13

ZDC Offline Status Report

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.

catori
Download Presentation

ZDC Offline Status Report

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. ZDC Offline Status Report C. Oppedisano

  2. Centroid over ZNs: data y 4 with x 1 2 C. Oppedisano

  3. 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 PMC PM1 PM2 PM3 PM4 PMC PM1 PM2 PM3 PM4 The towers covered by the collimator jaws have less counts C. Oppedisano

  4. Dipole effect on ZDC data ZNA Dipole OFF Dipole ON • 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 C. Oppedisano

  5. Simulation • 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(); C. Oppedisano

  6. ZNC spectra DATA common PM PM 1 PM2 PM3 PM4 common PM PM 1 PM2 PM3 PM4 MC C. Oppedisano

  7. ZPC spectra DATA common PM PM 1 PM2 PM3 PM4 common PM PM 1 PM2 PM3 PM4 MC C. Oppedisano

  8. ZNA spectra DATA common PM PM 1 PM2 PM3 PM4 common PM PM 1 PM2 PM3 PM4 MC C. Oppedisano

  9. ZPA spectra ZNA common PM PM 1 PM2 PM3 PM4 common PM PM 1 PM2 PM3 PM4 ZPA  we are investigating the problem that causes the loss of charged particle signal in ZPA C. Oppedisano

  10. Shuttle and DAs • 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 C. Oppedisano

  11. ADD detector in ZDC offline • 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 ZDC • 1 ADC for ADD + 1 TDC for ADD • No changes at higher level (Reco, ESD…) at least for the moment. C. Oppedisano

  12. Offline calibration 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 data output: OCDB object AliZDCTowerCalib Once the needed parameters will be tuned we will be ready to implement it as an offline calibration task. C. Oppedisano

  13. Savannah bugs 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... C. Oppedisano

More Related