130 likes | 144 Views
Calibration almost complete, no major changes, DA status stable. Investigating track alignment issues. Optional new HMPID data format discussed.
E N D
HMPID offline status report ALICE Offline Week, CERN, 16 March D. Di Bari, L. Molnar, G. Volpe
Calibration • Calibration procedures for HMPID have been almost completed. • No major changes from the last offline week (see October talk). • No major changes foreseen. • Objects foreseen to be stored in the OCDB: • - CsI QE maps; • - status word (1 32 bits word).
Status of DA • Implemented, in production, stable • Planned change(s): • Short error report to InfoBrowser • Re-use of error files (1 / DDL, with long error summary: where , what , how many times …) • Export pedestal map to AMORE-HMP.
Alignmenttracks extrapolation problem • Alignment procedures test is in progress. • Anyway a strange behavior in the track extrapolation has been detected. • It is present in the last AliRoot versions (trunk) after the changes related to the magnetic field.
Alignment Mip-track distance Old AliRoot version 3 GeV/c proton, 0.2 Tesla
Alignmenttracks extrapolation problem • Mip–track mismatching is not the same for all the HMPID modules. • After a first investigation we didn’t find the real origin of the problem. • What’s going on? We are investigating. • Finish date for alignment on planning page 30/01/09 ?!!
Optional new HMPID data format • Introduce 5 new words immediately after the HMP equipment header for each DDL • Optional: • can be turn on/off from firmware, DAQ • Default: • OFF, however in the first runs: ON • Why: • track RO firmware, DAQ errors.
Old & new HMPID data format New version of raw data format: Common Data Header (CDH) 0000b87c 00000011 00000600 00000000 00000000 00000000 00000004 ffffffff 0207091d 003beaa8 00000000 0000093e 00000000 00008000 000000000000000d 00000200 00000000 00000001 00000000 01ea32a8 0044006f 00441079 0044309c 00444094 00446072 00447077 00449092 0044a06f 0044c071 0044d060 0044f04d Old version of raw data format: Common Data Header (CDH) 0000b868 00000011 00000600 00000000 00000000 00000000 00000004 ffffffff 02070b70 002a0e6d 00000000 00000b6e 00000000 00008000 0000000001ea32a8 00440076 00441081 0044207f 004430a0 00444096 0044508a 00446077 00447077 Blue raw data words: HMP equipment header Red raw data words: 5 new raw data words Green raw data words: Payload, actual pad values In AliHMPIDRawReader the decoding starts after the HMP equipment header.
The 5 new words • Word 1: (ie. 0000000d) = “Firmware version” • bit map [31-0] = firmware version • Word 2: (ie. 00000200) = “Status and error bits copied from CDH (5th word)” • bit map [31-16] = 0 • bit map [15-0] = status and error bits • Word 3: (ie. 00000000) = “# FEE_RESET received from TTC_RX before” • bit map [31-0] = # FEE_RESET received from TTC_RX before • Word 4: (ie. 00000001) = “# TTC_READY signal has gone down before” • bit map [31-0] = # TTC_READY signal has gone down before • Word 5: (ie. 00000000) = Reserved • bit map [31-0] = 0 The 5 words will be saved to OCDB, probably combined with the HMP Status Word from HMP-DCS!
Change in the HMPID code • Current decoding (AliHMPIDRawStream) is transparent no need for change,but … • In case of errors: • (Word 2 or CDH 5th word): change from “Normal” (circular multiple check decoding) to “Turbo” (linear decoding) in AliHMPIDRawStream. • Update the simulated raw data writing • Update Preprocessor to save words to OCDB
Status of AMORE • AMORE-HMP is updated following changes in AMORE core • Planned change(s): • Include pedestal map from HMP-DA • Improve on the fly noise calculation