Cosmics 2009

** Numbers in parentheses indicate the goal for entire cosmic period.

week 45-47: 

• Goals
  • L3=0.2 Dipole=off  SPD triggered events + ITS, TRD, TOF events with HLT mode C. 
    

week 40-44: 

• Goals
  • L3=off Dipole=off ITS, TRD, TOF events with HLT mode C. SPD still not ready
    

week 37: 

• Goals
  • MuTrg : 200M events tot. with Dipole=off (ALICE_MULTI)
  • ITS+TPC: pT-dependent alignment 200 k

Left: Integrated number of events in the first cosmic campaign since Sept 9th 2009. Right: Event recording rate.

Left: Integrated number of MuTrg events (ALICE_MULTI) in the first cosmic campaign since Sept 9th 2009. Right: Event recording rate.

week 35-36: 

•  Goals:
  • TPC:  12M events gain calib. ExB L3 = 0.5 T, Dipole = 0.7 T.
  • MuTrg : 200M events tot. with B-field(ALICE_MULTI) trigger 0MCO
  • Weekend: TPC B-scan and reversed B-polarity

Left: Integrated number of events in the first cosmic campaign since August 24th 2009. Right: Event recording rate.

Left: Integrated number of MuTrg events (ALICE_MULTI) in the first cosmic campaign since August 24th 2009. Right: Event recording rate.

• Magnetic Field:  L3=0.5T, Dipole=0.7T
• PHYSICS partition:
  • Readout: ACORDE, SPD, SDD, SSD, TPC, TOF, TRD, TRIGGER
  • Trigger:  ACORDE, SPD, TOF(+-3) 90 Hz purity 30%

week 34: 

•  Goals:
  • TPC: 12M events gain calib. cosmics + Kr L3 = off, Dipole = off . 
  • MuTrg : 200M events tot. with B-field(ALICE_MULTI) trigger 0MCO
    

Left: Integrated number of events in the first cosmic campaign since August 15th 2009. Right: Event recording rate.

Left: Integrated number of MuTrg events in the first cosmic campaign since August 15th 2009. Right: Event recording rate.

• Magnetic Field:  L3=off, Dipole=off
• PHYSICS partition:
  • Readout: ACORDE, SPD, SDD, SSD, TPC, TOF, TRD, TRIGGER
  • Trigger:  ACORDE, SPD, TOF(+-3) 90 Hz purity 30%

• MCH:
  • took cosmic already in March 2009 but ask for another 2 wks For MCH you add the request to have 2 weeks of cosmics data taking with the dipole on (this will of course to have MTR as a cosmic trigger)

• EMCAL:
  • No special request, hope to be able to run in self-trigger mode. Maybe it could provide useful trigger for other detector ‚Äì big coverage & purity.

• HLT:
  • 2 days with each big and 1/2 small sub system
  • cosmic: online reco - compare with offline. HLT cosmic trigger - tag events with at least 1 TPC track

• TOF:
  • 3 clusters
    • trg ACORDE (10 Hz) TOF+TPC maybe TRD
    • trg SPD (0.1Hz)
    • trg TOF (1 kHz) need for few 100k tracks

• TRD:
  • detectors participating: TPC, TRD, TOF trigger: TOF pre-trigger and TRD L1 duration (with 70% eff.)
  • 2 weeks without magnetic field
  • 2 weeks with magnetic field (?)
  • (please note duty factor in 2008: 200 h/3 months)

• V0:
  • we confirm our request for a long cosmics run. The run will have to start as soon as the A side disk is installed and commissioned. The goal is to have a first HV set for the 64 PMTs corresponding to the MIP through each V0 channel.

• SPD:
  • No request, just check the alignment.

• SSD:
  • Stand-alone‚ activities 50K events of stand-alone cosmics for trigger alignment Global activities 100K events of general cosmics
  • Without field
    • Detector alignemnt (internal ITS + ITS/TPC)
    • Check the gain calibration P/N
  • With field (implies ITS-TPC track matching tuning)
    • dE/dx calibration

• HMPID:
  • Global cosmics data taking: HMPID would like to run with TOF trigger + tracking detectors (ITS, TPC, ...) with magnetic field ON (and also to run with field OFF).‚ We would like to collect as many events as possible du to the small acceptance.‚
• PHOS
  1. Integration issues can be tested in any global runs, including the cosmic ones. PHOS should demonstrate that it can work in the global run together with other detectors which implies integration of DAQ, DCS and trigger. Right now we are not ready for this global run, mainly due to DCS issues, but as soon it is solved, everything should be tested in the global run.
  2. Cosmic MIPs are needed for PHOS for the preliminary calibration of a accuracy about 5%. PHOS should be cooled down to -25 degrees for this calibration.
  3. Cosmic runs are needed to validate various online algorithms (DA) which calculate the calibration parameters via MIP signals and average deposited energy.
  4. Charged tracks from cosmic events are needed for PHOS for:
      - validation of the track matching with PHOS clusters,
      - checking the alignment parameters,
      - verification of the mapping.
  5.  Cosmic MIPs are needed for PHOS to tune TRU thresholds at least for two event classes:
      - clusters above noise and below MIP
      - clusters above MIP
  6. Run conditions: PHOS should participate in different trigger partitions:
      - PHOS is self-triggered by TRU
      - PHOS is a part of the trigger partition triggered by ITS or ACORDE