Set-Up Instructions for First Collisions 450 GeV

Included Subsystems

  • Subsystems In: ALL but ALFA MMEGA
  • Subsystems Out: ALFA and MMEGA

Useful Information

Filling scheme

  • We will run the first part of the test with flat bunch groups. Later we will load the following bunch scheme

CTP

  • Call CTP expert on-call and have them set:
  • Simple Dead Time 4
  • complex 15/370 (L1calo), 42/381 (TRT), 8/350 (LAr), 3/400 (PIX/IBL)

Run Control

  • beam type: protons
  • data tag: data15_comm
  • recording: enabled
  • lumiblock length: standard

Trigger

LUMINOSITY

  • The preferred algorithm is MBTS_EventAND
  • It needs ATLAS partition to be RUNNING to give meaningful luminosity values
  • It will become ATLAS_PREFERRED for the instantaneous luminosity tonight (will thus be forwarded to LHC Page 1)
  • It is sent to LHC via dip folder:
  • dip/ATLAS/LHC/LumiScan0 (set to preferred)
  • The backup algorithm is BCMTOR, sent in dip folder:
  • dip/ATLAS/LHC/LumiScan6
  • It does not need ATLAS to be RUNNING
  • IntTime needs to be changed to 1or 2 seconds (7 seconds right now). It will be changed at the same time we switch the ATLAS_PREFERRED tonight.

Event Display

Changes done to flip to Cosmics which need to be reverted tomorrow.

  • Complex deadtime Bucket 3 : 2/400 needs to go back to 3/400
  • simple deadtime 21 on request by CTP to have larger readout window.
  • remember to have beam spot, and OLC to HLT disabled
  • remember to have ROI L1 TOPO disabled
  • Could possibly enable muon triggers in all sectors

-- Main.apolini - 2015-05-04

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2015-05-06 - bschneid
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding ATLAS?Please contact the page author (see Topic revision above) or the Run Coordinator of the specific system.
Contact SysAdmins support only for technical issues