1 / 9

Run Coordination 31 January 2012

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

zwi
Download Presentation

Run Coordination 31 January 2012

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. Run Coordination31 January 2012

  2. 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 • Trigger: 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

  3. 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

  4. 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 pitCosmic runs: can be started immediatelyL1R,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.

  5. 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

  6. 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 will • finish 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

  7. 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.

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

  9. 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  alice-ctp-support@cern.ch (by Anton) • Alice-triggersupport: removed • TC and DTC in e-group of Run Coordination • (currently alice-src@cern.ch  alice-rc@cern.ch) • New alice-src@cern.ch for the SRCs only • Physics trigger discussion • alice-trig@cern.ch (trigger detector&CTP experts and coordinators • included, SRCs are requested to subscribe)

More Related