Last Updated on Wednesday, January 19, 2005 at 22:28:36. by Author: Burt Holzman

Online, General Information/Help

(Expert)

Contents

• Starting the Event Distributor
• Online Monitoring Clients
• Checking the silicon pedestals on shift
• Procedure for getting standard Trigger Plots
• Online/DV phat versioning/tag information
• CheckList Instructions
• How to create reference histograms
• How to print histogram summary 
• Known problems with histograms
• How to Print a Luminosity Monitoring Plot
• How to contact author

Starting the Event Distributor

The event distributor should be running in a window on phonl1.  The output looks something like:

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

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. Open an xterm on phonl1.
2. Type: killall -USR1 phat
3. Type: ~/dist

Checking the silicon pedestals on shift

Checklist Instructions

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

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.

How to create reference histograms

• Take a raw data file of your favorite run
• Start online and run over this file (this will create an output ile called OnlineObjs_runnr.root in 
  the local directory)
• Copy OnlineObjs_runnr.root to OnlineObjs_Ref.root (the next time online gets started it will load this file and  for reference)
• If you want the reference file for the standard shift, copy OnlineObjs_Ref.root to /home/shift on phonl1.phobos.bnl.gov

How to print histogram summary

Type 'phat "OnlineSummary.C(runnr)" from the command line, where runnr is the latest run taken
things to know:
online writes the monitoring histograms out to file every 100 events. This means that you can print the summary even if the job crashed.

Known problems with histograms

• Sometimes clicking on SiliconString brings histogram buttons on top of the FEC buttons

What to do: continue to click down the selection tree (fec, string) until you  reach the histogram buttons. this will then refresh the window and  draw the histogram buttons at the correct place.

• Seg.fault after closing latchup window

What to do: This is a problem related to root problems to detect a closed window.instead of closing it, just shrink the window using the underscore button instead of the "x" button of the window.

How to Print a Luminosity Monitoring Plot

• Pre-requisites : Currently, the Luminosity monitoring program loops over all the analysed data and produces an estimate of the RHIC luminosity. So all the data you want to look at needs to be transferred to HPSS and data validation needs to be run on it. This process is covered as part of the normal shift procedures here.
  

• Goto phucsia on the PHOBOS console and open a new terminal. Logon to one of the rcas machines as yourself : ssh user@rcf.bnl.gov followed by (say) ssh rcas4003. if you donot have an account on RCF you cannot complete the rest of this procedure.
  
  
• make sure the ROOT software environment is setup for your account. A simple method to do this per session is by typing:
    eval `/phobos/common/bin/phobos_setup csh`
    eval `/phobos/common/bin/phobos_alias csh`
  (Note the Back-tics!)
  (substitute csh for bash, if your shell is non-tcsh: in case of problems, refer to this documentation)
  
  
• make sure the DV_OUT environment variable is set:
  setenv DV_OUT /phobos/data02/dv_out
  
  
• go to the directory where the luminosity monitoring class resides.
  setenv SCR /phobos/data01/scratch
  cd $SCR/LumMon
  
  
• start up root
  root

• at the root command prompt type the following commands:
  
  root > .L luminosity.C
  root > t = new LumMon(<Start Run>, <End Run>)
  
  where <Start Run> and <End Run> are to be substituted with the appropriate run numbers you want to range over. You can determine this from the Run LogBook.
  
  For example, if you want to track the luminosity for the whole of PR00 period, you need to specify
  
  root > t = new LumMon(4320, <Latest Run#>)
  since Run 4320 was the first run in PR00
  
  If you just want the luminosity numbers over the last day, you will need to look at the Run Logbook to determine the Start and End Run numbers.
  
  
• On instantiating the LumMon class as above, it will go to $DV_OUT and try to find all the analysed TrgTree's between Start and End Run numbers. Any problems found with specific files will be reported to the screen. Most recent runs may not have come through the analysis process yet, so you may not find the appropriate TrgTree's in $DV_OUT. Also, some old runs had problems with their analyses and will  be automatically dropped.
  
  
• to obtain the Luminosity plot, type:
  root > t.Track()
  
  this will run through the found data and produce a standard plot of the estimated luminosity numbers covering the period from Start Run to End Run. The plot will be saved in $SCR/LumMon and an attempt will also be made to print it directly to the Counting house printer. If the plot is not printed, you need to transfer it back to a local counting house computer and print it locally, by executing (for example)
  
  rcf> scp $SCR/LumMon/<PlotFileName> shift@phucsia.phobos.bnl.gov:~
  phucsia > lpr -Pparrot <PlotFileName>
  
• (Note: To print directly onto transparencies on the Counting house printer from Unix requires the default tray on the printer to be set to 'Middle'. This can be done by toggling through the setup menu on the Printer's control panel, before issuing the lpr command. Please remember to switch the default tray back to 'Lower' after you are done printing on the transparency!)