To make a test with the L0Muon trigger in RUN mode and the TELL1 in RICH TRANSPARENT mode the following components have to be initialized in the following order.

TFC initial setting:

Prepare the TFC to send triggers (see L0MuonHowToConfigureTFC)

Start it to RUNNING state and then pause it to PAUSE state.

TELL 1 setting:

  • Log onto the TELL1
  • Start the TELL1 acquisition task daq_tell1 on the proper TELL1 (see L0MUonHowToConfigureTELL1) with the proper configuration files (RICH1.v21.tmutellqxy.cfg (xy is taken into 01-02-12-03-04-34 depending of the used crate))

Processing and Controller boards setting

With the PVSS toolBox tool Test communication and do remote shell commands :

  1. On the Processing Boards part (upper part of the panel)
  • Select the crate(s) you want to use
  • Select the boards you want to use in each crate (likely to be ALL)
  • From the Command list button open the list of available commands andf double click on Set_Run_Mode_On_PB.py to select it
  • The selected command appears in the command line test window.
  • Send the command for execution to all the selected CCPC by clicking on the button SEND PB Paralell CMD
  • The leds switch to yellow on the selected board(s) while the command is executed. When they switch back to blue the command is finished.
  • Check the result of execution by clicking on the Trace button associated to each board.

  1. On the Controller Boards part (lower part of the panel) * Select the crate(s) you want to use * From the Command list button open the list of available commands andf double click on CB_Send_Sync.py to select it * The selected command appears in the command line test window. * Send the command for execution to all the selected CCPC by clicking on the button SEND CB Paralell CMD * The leds switch to yellow on the selected board(s) while the command is executed. When they switch back to blue the command is finished. * Check the result of execution by clicking on the Trace button associated to each board.

TFC start:

Start the TFC to switch it in RUNNING state. L0Accept are then sent to the L0Muon and its TELL1.

TELL monitor events MEP:

You can check in another window of the TELL1 with the program console_tell1 option d (Detector Specific) then option l (Read and Parse MEP during run) that data are received and MEP(s) produced

Event buider:

You have to start the event builder (see L0MuonHowToWriteMEPsOnMarmuon4) to collect the data and then analyse them (see L0MuonHowToReadMDFOnMarmuon4).

Notice the event builder can be started or restarted any time independantly of the rest of the sequence. Ecah time it is stopped or restarted it creates or recreates the output file. So save /rename your file if you want to keep it for later analyse after each stop.

IMPORTANT: at any time you can start or stop sending L0Accept by swiching the TFC from RUNNING to PAUSE state. But if you happen to switch it in another state (READY or NOT_READY or ERROR) you will have to redo the full sequence from the very beginning because the L0Muon processor boards will have lost their configuration.

-- PierreYvesDuval - 01 Nov 2007

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2007-12-05 - PierreYvesDuval
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback