Difference: Eventbuilder (1 vs. 2)

Revision 22008-02-09 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="SliceTest"

Slice Test - Running the Eventbuilder

Line: 23 to 23
 
  1. Wait until the run stops.
  2. Check that the expectyed number of events really has arrived in all the buffers displayed in the window "MBMMon".
  3. Stop the Eventbuilder with the help of ./stopEventbuilder.sh. Answer the arising question with "y".
Changed:
<
<
>
>
  1. You find the data in the directory /velo/data/slicetest/
  -- OlafBehrendt - 08 Feb 2008

Revision 12008-02-08 - OlafBehrendt

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SliceTest"

Slice Test - Running the Eventbuilder

Setup (only at the start of the day)

  1. Login to the filter farm node hlte0603 (Linux) and change to the directory /group/velo/sw/scripts.
  2. Setup the environment for the eventbuilder by executing the command "source startEventbuilder.sh". You should end up in the directory /group/velo/sw/cmtuser/Online_v3r2/Online/OnlineTasks/v1r4/job

Configuration (only if you change the slice)

  1. Open a shell on any machine in the online network. Change to the directory /group/velo/sw/scripts. Adjust the configuration files of the eventbuilder to the TELL1 under test by making use of the PERL script configureEventbuilderSlicetest with the following syntax: ./configureEventbuilderSlicetest Tell1IpAlias (e.g. "vetella17")

Running the Eventbuilder

  1. Go back to the shell on the filter farm node hlte0603.
  2. Start the Eventbuilder with the command: ./slicetest.sh slotLabel Tell1SerialNumber runType. Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
  3. Many windows will pop up.
  4. Check that there are three buffers in the window "MBMMon". If not, stop the Eventbuilder (see below) and start over from 1.
  5. Wait for the message "crhhh...3 Event# nrx" to appear in the window "EvtProd".
  6. Start the run in PVSS!
  7. Should the message "Unexpected event package from ..." or "Missing event package from ..." appear call the expert.
  8. Wait until the run stops.
  9. Check that the expectyed number of events really has arrived in all the buffers displayed in the window "MBMMon".
  10. Stop the Eventbuilder with the help of ./stopEventbuilder.sh. Answer the arising question with "y".

-- OlafBehrendt - 08 Feb 2008

 
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