Online, General Information/Help

polling fServer ... pollresult: 1 fServer[0].revents:0
done.
Writing Run 6390, Event 111639
TrgProcMod(TPhSuperModule): ::Process() 
....

However, it is now reasonably user-proof and will run even if you crash the X server.  Due to instability in the raw data format, the distributor may crash. If it does, the symptoms:

1. The EvtDistrib on the master alarmer will turn orange and alarm.
2. Some of the online clients will turn orange and the date/time in the lower left of their status bar will not be updating

When this alarm has occurred, the distributor is probably just fine, but the DAQ has hung up.  When you recover from the DAQ crash by restarting the GUI, the distributor will once again be happy.  If that's not it: to restart the distributor in case all hell has broken loose (this will kill any online clients running on phonl1 as well -- so you'll need to restart them afterwards.)

1. Call Burt.  He wants to know about this.
2. Open an xterm on phonl1.
3. Type: 

killall -USR1 rootn.exe
dist

Checking the silicon pedestals on shift

Checklist Instructions

Process the data taken, to see how to do this see Procedure for getting standard Trigger Plots

Running Online Display PHEVER

• Go to PHONL1 machine. Change directory to $PHAT2HOME/macros/online/pro, and run phever.C, ie,

> cd $PHAT2HOME/macros/online/pro

> rootn.exe -q  phever.C

        (In principle, this action is enough for everyday. By default phever will try to access the port 9000, where the event is produced by Burt's TPhOnDistModClient. The event has TrgEventData, PCALEventData, T0EventData, TOFEventData, so phever run fast with this standard mode)

Running PHEVER in expert mode

• There are several other modes to run phever.C. Each mode act differently. For example,

> rootn.exe 'phever.C("7373")' 

        (This will access the port 7373. Since the default event distributor process only TrgEventData, so Phever will  process PCAL, T0, TOF, data unpacking, and produce PCALEventData, T0EventData, TOFEventData. In this mode, phever will be very slow)

> rootn.exe 'phever.C("/data/RAWDATA/PhoRaw0012345s000.pdaq")"

        (This will process a RAW data, and produce a summary plot and a root file with all histograms. The output file names are "Phever0012345s000.root" for histograms and "Phever0012345s00.ps" for the summary plot. It's a good idea to do this job with batch mode, ie, rootn.exe -b, when you need only the summary plot. You can stop at anytime to exit the job and to get the summary plot)

> rootn.exe 'phever.C("")'

        (If you like much phever and want some more fun, try this at your cost)

Running Vertex Display

• Vertex display is currently supposed to be run on phogen3.
• It can be run standalone or in client-server configuration

• Starting standalone version (use this for now)
  - Logon to phogen3 as shift
  > rootn.exe -q $PHAT2HOME/macros/online/dev/onlvertex.C
  Display should appear processing events after first initializations from database

  when it appears hanging and you want to restart it
  - use Ctrl_c and upper arrow to recall starting command

• Starting client-server (not yet commissioned for PR05) (assuming port connections are established well)
  - On one terminal logon to phogen1 as shift
  > cd /home/shift/andrzej
  > source .login.andrzej
  > rootn.exe -q 'onlvertex_cluster.C("clusterserver")'
  - On another terminal logon to phogen3 as shift
  > cd /home/shift/andrzej
  > source .login.andrzej
  > rootn.exe -q 'onlvertex_cluster.C("clusterclient")'

  when it appears hanging and you want to restart it
  - use Ctrl_c and upper arrow to recall starting command on terminal with started server
  - use Ctrl_c and upper arrow to recall starting command on terminal with started client
  - in this order
  
  when terminals that started vertexing are not available
  - find process number for either standalone or cluster processes on both phogen1 and phogen3
  > ps -efw | grep onlvertex
  - select processes started by rootn.exe and kill them
  - continue with starting online vertex display along the instructions given above
  
  when restarting does not help revive display this may be an issue with network connections
  - you have to call Burt or Andrzej or wait for update of these instructions

• Tips
  You can use all the ROOT GUI facilities (recalled by right mouse click) to interact with histograms and pads. Printing individual pads, changing statistic box properties, fitting etc. Best used when program is paused.

       Hanging display is actually not hanging but processing some huge silicon events that happen right after the silicon is turned on. We are working on software modifications to skip such abnormal events in the future.

Old (as of PR03): Procedure for getting standard Trigger & Silicon Plots

Now and forever, this will be done on phucsia.phobos.bnl.gov in the shift account. 
Furthermore, we have combined this with the silicon analysis.

All that is needed is to go to the $PHATHOME/macros/trg
directory and type 

.x trgsi_analyze.C(run, seq)

where
run = the run number of the recently finished data
seq = the sequence number
This will place two files TrgTree_RUNsSEQ.root and TrgAnalyze_RUNsSEQ.root into a directory specified by the environmental variable TRGTREE. This should be set up in the shift account already.
After this, you should run two other macros:

.x trg_rhicplots_calibrated.C(run, seq)
.x si_analyze_plot.C(run, seq)

The first will analyze all of the events and place a page or two (under development) of standard plots back in $TRGTREE as .ps files. The second will analyze the TrgSiAnalyze_RUNsSEQ.root file and make two pages of silicon plots.
If there are problems over the weekend, ask peter.