Difference between revisions of "RICH pedestal run"

From Hall A Wiki
Jump to: navigation, search
(Geenerate the pedestal files)
Line 1: Line 1:
How to take a RICH pedestal run, generate the pedestal files and make them visible to the DAQ.
+
Follows the A, B and C procedures to take a RICH pedestal run, generate the pedestal files and make them visible to the DAQ.
  
== Take the RICH pedestal run ==
+
== A) Take the RICH pedestal run ==
  
 
a1. Ask MCC for '''beam OFF'''
 
a1. Ask MCC for '''beam OFF'''
Line 17: Line 17:
 
a7. take 2000 events at least, then stop the run
 
a7. take 2000 events at least, then stop the run
  
== Geenerate the pedestal files ==
+
== B) Generate the pedestal files ==
  
 
b1. login as adaq@adaql6 (or l7)
 
b1. login as adaq@adaql6 (or l7)
Line 33: Line 33:
 
b6. quit analyzer: '''.q'''
 
b6. quit analyzer: '''.q'''
  
== Make them visible to the DAQ ==
+
== C) Make them visible to the DAQ ==
  
 
c1. go back to a-onl@adaql4 (or higher) in the directory '''/adaqfs/home/a-onl/rich/pedestal'''
 
c1. go back to a-onl@adaql4 (or higher) in the directory '''/adaqfs/home/a-onl/rich/pedestal'''
  
c2. do the command: '''./copyped.sh'''  (check the messages about file length)
+
c2. run the script: '''./copyped.sh'''  (check the messages about file length)
  
 
c3. you can now start the production; do not forget to set the prescalers correctly
 
c3. you can now start the production; do not forget to set the prescalers correctly
  
 +
== Additional Information ==
 +
 +
The file ''save/log.txt'' keeps track of the operations of the above scripts '''preped.sh''' and '''copyped.sh''' and therefore of the pedestals used in the data acquisition in each run.
 +
 +
Moreover '''copyped.sh''' backups a copy of the latest pedestal files in a subdirectory in ''save/''; the subdirectory is written in ''save/log.txt''.
  
 
Back to the [[Left RICH]] page
 
Back to the [[Left RICH]] page

Revision as of 01:46, 19 November 2008

Follows the A, B and C procedures to take a RICH pedestal run, generate the pedestal files and make them visible to the DAQ.

A) Take the RICH pedestal run

a1. Ask MCC for beam OFF

a2. login as a-onl@adaql4 (l5, l6 or l7)

a3. go to the directory: /adaqfs/home/a-onl/rich/pedestal

a4. do the command: ./preped.sh

a5. prescale all trigger except T3 and T5

a6. run a standard calibration run in TwoArmRICH (comment as RICH pedestal), deadtime should be araound 15% at 25 Hz

a7. take 2000 events at least, then stop the run

B) Generate the pedestal files

b1. login as adaq@adaql6 (or l7)

b2. go to the directory: /adaqfs/home/adaq/e06010/rich/leftreplay

b3. run analyzer

b4. within analyzer do: .L newdecodeRICH.C+ (note: to speed up the processing, do not forget the + at the end)

b5. then run: newdecodeRICH(####) where #### = number of the pedestal run

b7. check the message about pedestal and noise means at the end of the processing

b6. quit analyzer: .q

C) Make them visible to the DAQ

c1. go back to a-onl@adaql4 (or higher) in the directory /adaqfs/home/a-onl/rich/pedestal

c2. run the script: ./copyped.sh (check the messages about file length)

c3. you can now start the production; do not forget to set the prescalers correctly

Additional Information

The file save/log.txt keeps track of the operations of the above scripts preped.sh and copyped.sh and therefore of the pedestals used in the data acquisition in each run.

Moreover copyped.sh backups a copy of the latest pedestal files in a subdirectory in save/; the subdirectory is written in save/log.txt.

Back to the Left RICH page