|
|
 |
STAR SSD
|
- Pulser Run procedures
|
1 Take a pulser run
2 Analyze the pulser run
3 Run 7 pulser runs
|
1 Take a pulser run
Bring the SSD up for acquisition (RDO, HV and RDO ON) do a "Start SSD" and take a pedestal run.
- switch to Full Control (after the pedestal run, the SSD is still in Acquisition mode)
- Launch the pulser script :
> cd /home/ssd/scripts/
>./set_calibration_pulser #1 #2
while #1 is the strip offset and #2 is the level of the pulse (40 or 100). This script also sets to pulse 4 strips/chip by default.
The script will also bring the SSD from the Full Control mode, to the Calibration mode and one should see "Loading parameters" messages.
Finally it will bring the SSD in the Acquisition mode. This may take few minutes.
- When the SSD is in acquisition mode, take a "Pulser" (in the run configuration) run with Trigger, DAQ and SSD subsystems (1000 events).
NB : After taking the run, and if other pulser runs are needed, one have to switch back to Full Control mode before launching the script (set_calibration_pulser).
NB : It is recommended to take a pulser run with pulse level = 0 in order to quantify the noise.
2 Analyze the pulser run
To analyze the pulser, one has to run the BigFullChain in order to produce root files containing NTuples.
Then we used the maker written by Jerome Baudot to plot the total charge on p/n side and their relative gain( ratio) between them.
Choose the pulser you wan to analyse
in 2007 we took 32 pulsers with for the most part of them, a pulser amplitude = 100.
These pulsers were also set up with 4 strips per chips.
Final list of run : here
Run the BFC chain
As you find the path to hpss to the run you want to analyze, type :
- root4star -b
- .x bfc.C(event_begin,event_end,"2007a alltrigger ittf -emcDY2","my_run")
where :
- event_begin, event_end : set the number of events you want to analyze with this pulser
- my_run : path the daq file
ex : /star/data03/daq/2007/*/*.daq
- Change the pointmaker in order to write histograms
(see procedure to change the pointMaker to write NTuples )
Use StSsdReadMaker
In this maker, you have explicitely to set the id of the 4 strips fired by the pulser, for the p-side and n-side :
example :
- selectedStrip[0][0] = 14; // P side
- selectedStrip[0][1] = 30;
- selectedStrip[0][2] = 110;
- selectedStrip[0][3] = 126;
- selectedStrip[1][0] = 3; // N side
- selectedStrip[1][1] = 19;
- selectedStrip[1][2] = 99;
- selectedStrip[1][3] = 115;
Then to run this maker, you have to use another macro :
root4star -b
.x readPulserCluster.C
(you have to set up properly the name of the root file produced by the pointMaker here)
Plot and get the ratio
As a result , it creates a root file with extension .root_histos.root
In this file, the plot with the ration of the n over p side is :
h2RatioPerWafer
To dump the values in a text file , use this macro :
here
3 Run 7 AuAu Pulser run summary
List of pulser runs taken for Run 7 AuAu.
For this year, we don't see any pulser on :
- ladder 2
- ladder 6
- ladder 7
- ladder 11
- ladder 13
- ladder 16
Last updated by Jonathan Bouchet on