Detector Online Monitoring

The scheleton we are presenting here for the Online Monitoring of the detector is based on three different approaches. Still everything is based on the nice SPY system developed by the DAQ group.

• A) Online Histogramming:

  Our proposal at the moment is really minimalistic. We need to learn how to interpret the data on memory. In this case all calls to filling object histograms is done using the "c"-language. Minimal usage of the offline reconstruction is needed here. There are two possible scenarios:

  • An HISTO_PRODUCER process runs on each SBC farm node and send histograms to an HISTO_ADDER running elsewhere in a standalone machine.

  • The SPYDAEMON process only runs on each SBC. A GLOBAL_HISTO_PRODUCER looking at all SBC nodes runs in a standalone machine fetching events as fast as he can and it is dedicated only to filter data and fill histograms.

  In both cases the HISTO_ADDER or the GLOBAL_HISTO_PRODUCER can either send the histograms on request to the HISTO_PRESENTER or work as in the "old-gone" days in the scheme of CONSUMER/PRODUCER fetching histos on request from a global section or a shared histogram file.

  We do not have preferences. Whatever it is decided is fine. What is clear is that the HISTO_PRESENTER, for "normal online detector monitoring" should:

  • not to be based on PAW ! (it is too late. It is gone)
  • be nice and simple to be used by X-term.
  • be stable and reasonably fast.

  These requirements reduce a lot the easyness to use F77 or A_C to do it if we do not want to introduce another SHARED memory between the HISTO_PRESENTER and the PRODUCER (for istance, see the connection in DIDONE between Vis.exe and A_C.exe). Our proposal instead is the following:

  Let us use "C" as the basic language for Online monitoring. More sophysticated analysis as, for istance, tracking reconstruction/calibration and so on DO NOT NEED TO BE "exactly" ONLINE. Indeed, we expect to close a file each 2-3 minutes. The EMC group intend to process as quick as possible, with all the magic of OFFLINE reconstruction, all the coming data in order to calculate calibrations and monitor relevant physical quantities (energy-time scales and resolution + efficiencies).

  An A_C program spying/reading from files can always book HBOOK histos that can be quickly converted "ON REQUEST" to other objects as ROOT or OSH files.

  ******* ROOT USAGE NOW 8-AUG-1997 ********

  Using the shared memory facility of the new ROOT version (v1.02), a producer & a consumer program have been created. The first one, uses the events coming from the online spy process, fills the histograms and stores them in a memory map file. The second one connects to this file and display the histograms.

  All the code is in the area /kloe/soft/monitor/src/

  PRODUCER: emchisprod.cxx

  CONSUMER: CalSysTest.C,Input.C,BarrelHisto.C

  *** HOW TO RUN IT OFFLINE *****

  If you want to taste how the presenter looks like, a procedure to run it offline from the "daq" account has been set-up:

  - Connect on dxcalc machine (the only one where at the moment ROOT v1.02 is installed) as "daq" user.

  - Go to your favorite scratch area (for instance /scrtch1/kloedaq/daq/myarea )

  - Give the command: source ~/root/root_example_setup.csh

  This script creates a subdirectory "root" under the one where you stay & creates there all the necessary links and setup to run the presenter

  - Start the root application typing: root

  - Type: .x CalSysTest.C a control bar appears

  - Push the "Input data" button to open the memory map file

  - Push one of the "Wedge # Histo" . A new menu appears. From here you can display 15 histograms selecting one of the buttons.

  ***** HOW TO RUN IT ONLINE *********

  The procedure to run online from "daq" account is:

  a) Start a receiver/builder/recorder procedure on dxcalc

  b) Start a collector & sender procedure on axrt02

  c) Start a spy-daemon process on dxcalc

  d) Finally, go in your favourite scratch1 area and type:

  source ~/root/hisprod_startup_OSF1.csh

  e) Start the online ROOT presenter typing:

  source ~/root/root_setup_OSF1.csh

• B) Online spying
  • Template Process .. to make Murtas_like_monitoring. A simple proposal is to write all the old goodies of emctest inside the template standard accessing information directly from the spy. We can both calculate pedestals and calculate t0s, mean for mips, occupancies and so on.
  • A_C process (it is not yet existing but it is possible to be implemented). Let us create one Input Module called SPYMODULE to get data from one or more remote spy daemons.

• C) Online display

  Here the best of mixing between Online & Offline can really be done since it is working today. Unfortunately works only from file .. still is a work in progress.

  ---

  Online/Offline programs for DIDONE:

  ---

  **** HOW TO RUN IT OFFLINE *******

  If you want to taste how the DISPLAY looks like, a procedure to run it offline from the "daq" account has been set-up:

  - Connect on dxcalc machine (the only one where at the moment ROOT v1.02 is installed) as "daq" user

  - Move to a scratch area (for instance /scrtch1/kloedaq/daq/ )

  - Give the command: source ~/didone/didone_startup_XXX.csh (XXX= OSF or HP-UX)

  This script starts the display

  - select in A_C botton Vis-AC-Vis ... a window A_C control appear.

  - Open file: /kloe/soft/monitor/db/spy0000000.raw and see in the main window if the file is succesfully open.

  - go in A_C control window.

  • A_C>> @didone_online.uic
  • A_C>> beg
  • (answer to ped file) $CALIB/ped100hz.dat
  • (answer to online or offline) 1
  FINALLY the Displays one window or 4 windows appear.

  Play around with event botton using /next/automatic. Play with Windows botton.. and learn to Zoom/Rotate and so on.

• emchisprod
• raw2cele
• systestmon library

• Open Online Histo file
• Main Emc Menu
• Histogram Presenter

• emcspy process
• emcspy all
• emcspy library

AH AH .. Igor prepared for you a simple GUIDE in the iper-word of the KLOE daq ... HAVE FUN.