Starting and Stopping the MIDAS Clients

From tigwiki

Jump to: navigation, search

Contents

[edit] Introduction and Background

This page describes how to start the various MIDAS system components for the main TIGRESS experiment. These instructions assume you are a little bit familiar with Linux and Midas.

[edit] Setting up the Terminal Window

In order to give the on-call DAQ experts half a chance to diagnose things from home, all the MIDAS Components should be launched from interactive sessions on the main display of the MIDAS back-end server, midtig02. This terminal window should already exist, unless the tigress@midtig02 account has been logged out for some reason (e.g. crash).

If you cannot find a terminal window with about 10 tabs in it, you will have to start a new one

[edit] Setting up a new terminal window from scratch

  1. Start a new Terminal window. Either a Konsole or a Terminal (/usr/bin/gnome-terminal) will work.
  2. For each Component in the MIDAS Components list in the order from Top to Bottom:
    1. Open a tab: Session → New Session
    2. Name the tab with the client name. Right-click on the tab at the bottom, select Rename Session, and type in the client name.
    3. ssh to the correct user@machine.
    4. If a working directory is specified, cd to it.
  3. Open more tabs:
    1. One called midtig01: ssh to tigress@midtig01. This one will be used for compiling codes if needed.
    2. One called odbedit: cd to /home/tigress/tigcol2/frontend, and use this one to run odbedit sessions if needed.
    3. At least one more: for generic work.

[edit] Starting Konsole using a profile

If a single Konsole window already exists somewhere, you can launch a new Konsole session using the --profile option:

  • konsole --vt_sz 192x48 --profile daq-gh &

The daq-gh may not be the most up-to-date. Make sure you verify all sessions.

[edit] Verify sessions

If the terminal window already exists, go through and verify that all the appropriate tabs exist, and that they are logged in to the correct machine and cd'd to the correct working directory.

[edit] Starting the Components

Go through the list of components from top to bottom, and do the following:

  1. Go to the tab on the main terminal window with the same name. Verify that you are logged into the same machine and cd'd to the correct working directory.
  2. Start the program using the listed command line.

[edit] Restarting individual clients

Occasionally, one or more clients will crash and will need to be restarted. Usually this is indicated by a red cell somewhere on the main status page. Other symptoms include things not working right. (This description sucks. Someone should fix it.)

To restart an individual client:

  1. Although it is not mandatory,it is recommended to stop the run now. You'll want to make an e-log entry anyway.
  2. Find the appropriate line for this client on the MIDAS Components list. Use the entries in this line for the "appropriate" Konsole window, machine, etc. as described below.
  3. If client is an auxilliary client, try to shut it down with "exit" from a pull-down menu.
  4. If client is a regular MIDAS client, try to stop client from within MIDAS.
    1. From the main control window, hit the Programs button.
    2. See if the client in question is on the Programs page.
    3. If it is, click the Stop client
  5. Find the appropriate Konsole window. If the program hasn't stopped yet, hit Ctrl-C twice.
  6. Do an ODB cleanup.
    1. Start odbedit on midtig02.
    2. Type cleanup.
    3. Type quit.
  7. Go to the appropriate tab on the main Konsole window. Verify that you are still logged into the appropriate machine, user, and directory.
  8. Start the program using the listed command line.

[edit] Stopping all clients

If the DAQ crashed you may want to completely stop all components and then restart them all.

  1. Stop the run. If this fails, don't worry -- you're about to fix it.
  2. Shut down all the Auxilliary (Aux.) clients. First try it in an orderly fashion, either by selecting "exit" from a pull-down menu or by closing the window, if any. If this doesn't work, go to the tab where it is running, and hit Ctrl-C twice.
  3. Do an ODB cleanup.
    1. Start odbedit on midtig02.
    2. Type shutdown all.
    3. Type cleanup.
    4. Type quit.
  4. For each component:
    1. Find a terminal tab logged in as the correct user on the correct machine. You might have to ssh.
    2. Do a killall component. Use the Program Filename for the component.
    3. Do a killall -9 component.
  5. Repeat the above ODB cleanup steps.

[edit] SHEREKHAN MIDAS Components

Program Name Type Client Name[1] Working Directory[2] Compiles On[2] Runs As User@Machine Command Line (from working directory)
mserver Server sherekhan@midtig06 mserver
mhttpd Client mhttpd sherekhan@midtig06 mhttpd -p 8081
mlogger Client mlogger sherekhan@midtig06 mlogger
fetigcol Client FeTigCol /home/sherekhan/tigcol3/frontend lxdaq17 sherekhan@lxdaq17 ./fetigcol -i 1
analyzer Client Analyzer /home/sherekhan/tigcol3/iAnalyzer midtig06, midtig04, or mastodon sherekhan@midtig06 ./analyzer -h midtig06 -e sherekhan -s 9091[3]
event builder Client event builder /home/sherekhan/tigcol3/EventBuilder/src_cpp midtig06 sherekhan@midtig06 ./eventbuilder
Masks Script tigenable /home/sherekhan/tigcol3/frontend midtig06 sherekhan@midtig06 ./tigenable 1 2 3 4 5 6 (7 8 9)[4]
fe_epics Client Epics /home/sherekhan/tigcol3/epics[5] midtig02 tigress@midtig02 ./fe_epics -h midtig06 -e sherekhan
femcs Client Femcs /home/sherekhan/tigcol3/femcs lxdaq19 sherekhan@lxdaq19 ./femcs -h midtig06 -e sherekhan
roody Aux.

[6]

sherekhan@midtig04 roody -H midtig06:9091[7]
Striptool Aux. ssh -X tigsebt3a@isacepics1

Notes:

  1. ↑ Only clients have names -- empty boxes correspond to programs that are not MIDAS clients
  2. ↑ 2.0 2.1 The production (i.e. working) version of any user-written software is normally in this working directory, and should be compiled while logged into the machine listed. Empty entries are not user-written, do not need to be compiled, and can be started in any directory.
  3. ↑ As of the 11Be run of 2011, the analyzer has been broken into four parts with different executable names: analyzer-w for waveforms, analyzer for hit patterns & raw charge, analyzer-a for analyzed spectra e.g. gain-corrected energies times and such. Replace 'analyzer' with 'analyzer-w' or 'analyzer-a' as needed. You can run these on any of our 64-bit machines -- in fact, that is encouraged. The final parameter specifies which port to use for the roody connection below. You need to use a unique port number for each running analyzer -- I recommend 9090 for analyzer-w, 9091 for analyzer, and 9092 for analyzer-a.
  4. ↑ The numbers correspond to the collector cards. 1 through 6 are Ge, 7 and 8 are Silicon, and 9 can be used for RF. To enable silicon only, use './tigenable 7 8'
  5. ↑ Make sure you log in as the correct user at the correct machine, and then cd to the correct path. The Isac-wide Epics system will only talk to specific accounts on specific machines. For this client it is common that the working directory is not the user account home directory.
  6. ↑ The working directory is normally set to the data directory where data is being logged and histograms are being saved.
  7. ↑ This example works with the analyzer example given above, which itself gives the "misc" and "charge" sets of spectra. Change the host (midtig06) and port (9090) to match how you launched the analyzer.See the roody page for more information.

[edit] TIGRESS MIDAS Components

Program Name Type Client Name[8] Working Directory[2] Compiles On[2] Runs As User@Machine Command Line (from working directory)
mserver Server tigress@midtig06 mserver
mhttpd Client mhttpd tigress@midtig06 mhttpd -p 8081
mlogger Client mlogger tigress@midtig06 mlogger
fetigcol Client FeTigCol /home/tigress/daq/frontend lxdaq04 tigress@lxdaq17 ./fetigcol -h midtig06 -e tigress
analyzer Client Analyzer /home/tigress/daq/shk_analyser dixie tigress@midtig06 ./analyzer
fe_epics Client Epics /home/tigress/tigcol2/epics midtig06 tigress@midtig06 ./fe_epics -h midtig06 -e tigress
femcs Client Femcs /home/tigress/tigcol2/femcs laddvme02 tigress@laddvme02 ./femcs -h midtig06 -e tigress
roody Aux.

[9]

tigress@midtig01 roody[10]
Striptool Aux. ssh -X tigsebt3a@isacepics1

Notes:

  1. ↑ Only clients have names -- empty boxes correspond to programs that are not MIDAS clients
  2. ↑ 2.0 2.1 2.2 2.3 The production (i.e. working) version of any user-written software is normally in this working directory, and should be compiled while logged into the machine listed. Empty entries are not user-written, do not need to be compiled, and can be started in any directory.
  3. ↑ As of the 11Be run of 2011, the analyzer has been broken into four parts with different executable names: analyzer-w for waveforms, analyzer for hit patterns & raw charge, analyzer-a for analyzed spectra e.g. gain-corrected energies times and such. Replace 'analyzer' with 'analyzer-w' or 'analyzer-a' as needed. You can run these on any of our 64-bit machines -- in fact, that is encouraged. The final parameter specifies which port to use for the roody connection below. You need to use a unique port number for each running analyzer -- I recommend 9090 for analyzer-w, 9091 for analyzer, and 9092 for analyzer-a.
  4. ↑ The numbers correspond to the collector cards. 1 through 6 are Ge, 7 and 8 are Silicon, and 9 can be used for RF. To enable silicon only, use './tigenable 7 8'
  5. ↑ Make sure you log in as the correct user at the correct machine, and then cd to the correct path. The Isac-wide Epics system will only talk to specific accounts on specific machines. For this client it is common that the working directory is not the user account home directory.
  6. ↑ The working directory is normally set to the data directory where data is being logged and histograms are being saved.
  7. ↑ This example works with the analyzer example given above, which itself gives the "misc" and "charge" sets of spectra. Change the host (midtig06) and port (9090) to match how you launched the analyzer.See the roody page for more information.
  8. ↑ Only clients have names -- empty boxes correspond to programs that are not MIDAS clients
  9. ↑ The working directory is normally set to the data directory where data is being logged and histograms are being saved.
  10. ↑ After starting roody, click Files → Open Online, and give midtig02 as the connection. See the roody page for more information.
Retrieved from "http://www.triumf.info/wiki/tigwiki/index.php/Starting_and_Stopping_the_MIDAS_Clients"
Personal tools
Experiment Pages