run coordination 31 january 2012

9
Run Coordination 31 January 2012

Upload: zwi

Post on 05-Jan-2016

35 views

Category:

Documents


2 download

DESCRIPTION

Run Coordination 31 January 2012. Tests tbd before 2012 run (TC requests). Kr data taking: TRD: week 6 or 7 (staring on 06 Feb or 13 Feb) TPC: week 9 (starting on 27 Feb) Cosmic data taking ( TPC +TRD+?) Starting around week 7 (on 13 Feb) Preparation needed - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Run Coordination 31 January 2012

Run Coordination31 January 2012

Page 2: Run Coordination 31 January 2012

Tests tbd before 2012 run(TC requests)

- Kr data taking:TRD: week 6 or 7 (staring on 06 Feb or 13 Feb)TPC: week 9 (starting on 27 Feb)

- Cosmic data taking (TPC+TRD+?)Starting around week 7 (on 13 Feb)Preparation neededTrigger: TOF back-to-back + TRD L1, or anything new?

- CTP new firmware running test in technical run

- L1R, L2R busy-time measurements

- Realistic trigger implementation in technical run

Page 3: Run Coordination 31 January 2012

Requests from the detectors

SDD: stability test of the vdrift -> measurement with the injectors; needed: - DCS, DAQ standalone and local trigger- 4 days of full availability for SDD, the 2 last days with full availability of SPD and SSD in stable ready state (not running)

No SPD and no SSD in stable ready state before end of February/beginning of March

Page 4: Run Coordination 31 January 2012

CTP

02/02 - ALICE on BEAM1 clock -jitter investigation 03/02 -  moving CTP lab 06/02 - tests of new CTP firmware in CTP lab 13/02 - installation of new CTP firmware in the pit

Cosmic runs: can be started immediately

L1R,L2R busy-time measurements: can be done in standalone(detectors who have doubts about it). The test in globalrun: starting on 13 Feb.

Realistic trigger in technical run: as soon as partitiondefinition is prepared, probably from second half of Feb.

Page 5: Run Coordination 31 January 2012

DAQ- EMCal new links & re-shuffling of LDCs: done, tbt- TRD new links, re-shuffling & 10 Gb Ethernet: done, testing in progress

-- One LDC (aldaqpc180, ldc-TRD-09-10-11-0) needs some fixing (slow disk), will be done this week-- Run-time profiling for the DDLs/LDCs: in progress

- TDS upgrade: in progress, TDS expected online before the end of the week- HMPID broken LDC (aldaqpc146, ldc-HMPID-2-0) replacement: during this week- TPC LDC with IPMI problems (aldaqpc108, ldc-TPC-A12-1): service contacted, no ETA, machine works OK (problems only @ reboot)

- Thursday or Friday: ECS/DAQ software upgrade (downtime: ~1 hour)

-- Fix for the "SMI dead" problem

Page 6: Run Coordination 31 January 2012

DCS- The new DCS cluster is up, running and available for migration by detectors (some are already more or less advanced, some still need to start...). All detectors willfinish the migration by the end of next week (hopefully!).

- Migration of the central systems ongoing, the most critical once will be done this week. There might be some perturbations due to that.

Feedback from the detectors

Page 7: Run Coordination 31 January 2012

HLT

HLT system was switched on again last week (wk 4). Tests ongoing in standalone. Planning for the next few weeks: cleaning-up some issues identified last year or at the HLT review workshop two weeks ago in Frankfurt.

Last week for these activities is wk9, afterwards HLT is ready for combined tests.

Page 8: Run Coordination 31 January 2012

OFFLINE

- Ready

DQM

- AliRoot version update (to be decided)- Reorganization of the DQM & OFFLINE PCs in ACR (tbd)

Page 9: Run Coordination 31 January 2012

E-Logbook entry (from last TC meeting)

Subsystem choice in “Add Log Entry”:- TRIGGER: removed or disabled- CTP: CTP technical issues - Run Coordination: RC & TC issues

New trigger implementation and request for data taking in both CTP and Run Coordination

Associated e-groups:- CTP [email protected] (by Anton)- Alice-triggersupport: removed- TC and DTC in e-group of Run Coordination (currently [email protected] [email protected])- New [email protected] for the SRCs only

Physics trigger discussion - [email protected] (trigger detector&CTP experts and coordinators included, SRCs are requested to subscribe)