MIDAS Clients Overview

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 8pi experiment. These instructions assume you are a little bit familiar with Linux and Midas. They have been adapted from those for TIGRESS.

[edit] MIDAS Components

The NEW system - USE THIS:

Program Name Type Client Name[1] Working Directory[2] Compiles On[2] Runs As User@Machine Command Line (from working directory)
mserver Server grsmid00 eightpi@grsmid00 mserver
mhttpd Client mhttpd grsmid00 eightpi@grsmid00 nice +8 mhttpd -p 8081
mlogger Client mlogger grsmid00 eightpi@grsmid00 mlogger
frontend Client 8pi ~/online lxdaq02 eightpi@lxdaq02 ./8pi
analyzer Client Analyzer ~/online/analyzer grsmid00 eightpi@grsmid00 nice +4 analyzer
fe_epics Client Epics ~/online/fe_epics grsmid00 eightpi@grsmid00 nice +4 fe_epics
roody Aux. GUI ~/online grsmid00 eightpi@grsmid00 roody -r setup.xml
DVM Client DVM ~/online/DVM lxdaq02 eightpi@lxdaq02 ./DVM
Striptool Aux. ssh -X 8pi@isacepics1


The OLD system - DONT USE THIS:

Program Name Type Client Name[3] Working Directory[2] Compiles On[2] Runs As User@Machine Command Line (from working directory)
mserver Server isdaq08 8pi@isdaq08 mserver
mhttpd Client mhttpd isdaq08 8pi@isdaq08 nice +8 mhttpd -p 8081
mlogger Client mlogger isdaq08 8pi@isdaq08 mlogger
frontend Client 8pi ~/online lxdaq02 8pi@lxdaq02 ./8pi
analyzer Client Analyzer ~/online/analyzer isdaq08 8pi@isdaq08 nice +4 analyzer
GUI Aux. GUI ~/online/GUI isdaq08 8pi@isdaq08 ./GUI
Striptool Aux. ssh -X 8pi@isacepics1

[edit] Detailed Description of Each Client

Detailed descriptions of each client or program are outlined in the following pages. Also see Killing Everything.

[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, grsmid00. This terminal window should already exist, unless the eightpi@grsmid00 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 grsmid00: ssh to eightpi@grsmid00. This one will be used for compiling codes if needed.
    2. One called odbedit: cd to ~/online, and use this one to run odbedit sessions if needed.
    3. At least one more: for generic work.

[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 grsmid00.
    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 grsmid00.
    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.
Retrieved from "http://www.triumf.info/wiki/tigwiki/index.php/MIDAS_Clients_Overview"
Personal tools
Experiment Pages