Hi,
I've just added an RdoModule class for the Silicon and Tile detectors.
The modified (M) and new (N) files are:
(M) mult/src/BrRdoMult.cxx
(M) mult/src/Makefile
(N) mult/src/BrRdoModuleMult.cxx
(M) mult/inc/BrMult_LinkDef.h
(M) mult/inc/BrRdoMult.h
(M) mult/inc/LinkBratMultINC.h
(N) mult/inc/BrRdoModuleMult.h
(N) params/ActiveMultDet_0.dat
(N) params/ActiveMultDet_1761.dat
(N) params/MultRefPedistals.dat
Some of the code should be changed to use the database stuff. This is
planned, but may take a few weeks to accomplish. (I'm not sure what
the current status of the database is...) In the interim, we are using some
parameter files in the params directory. The ActiveMultDet... files indicate
where detectors are physically located in the array and the corresponding
DAQ parameter mapping. Much of this changed with the recent reconfiguration
of the mutiplicity array. The _0 file gives the active locations before the
changes, and the _1761 file gives the current configuration. The
MultRefPedistals file give the pedistals and pedistal widths for the Si
segments and the tiles, and also the ADC gap location for the tiles. The
file that I committed is appropriate for the earlier runs. This will be
changed shortly for the more recent configuration.
Two standalone ROOT programs have be written to use the new RdoModuleMult
class. These are located in the Kansas account on the piis under
/home/kansas/analysis. The sources and Makefile are also located there.
multNtuple - Reads a raw data file and creates an ntuple of most of the
quantities available using the BrRdoMult, BrRdoBB, and BrRdoZDC classes.
If you want to play around with the global detector data, this might be a
place to start. The program takes three optional command line arguments:
runno seq# #seq
with defaults runno=1554, seq#=0 (replays first sequence), # seq = 1
(replays only one seq.). To replay all of run 1554, one would enter
multNtuple 1554 -1 0
The program stores the generated ntuple in the ntuples directory (there
should be a link to this in the same directory from which you run
multNtuple). The program assumes the raw data is located in the data
directory--again, you need a link.
pedistals - This program runs through all of the tile and Si detectors to
determine the pedistal locations and widths. The results are compared to
the reference pedistal data and a summary of differences is generated. The
program takes one optional command line argument--the run number (it looks
for the ntuple created by the multNtuple program). If no arguments are
given, run 1554 is assumed.
To replay run 1761 with new pedistals, you would use the following sequence
of three commands:
mutlNtuple 1761 -1 0
pedistals 1761 (answering "y" to the "save as ref.." question)
multNtuple 1761 -1 0
Two final notes:
Looking over the tile data, I think there MAY be significant problems with
the gain calibrations. These need to be explored further, but at the moment
I would be cautious about assuming the relative calibration of the detectors
is much better than 30%, if that.
The BrRdoModuleMult constructor needs to know the run number in order to
set up the appropriate files. I am passing this as an argument to the
constructor. The multNtuple and pedistals programs show how this is being
done.
Regards, Steve
This archive was generated by hypermail 2b29 : Tue Jul 18 2000 - 10:58:31 EDT