HOW TO LOOK AT DATA
Login into the Offline PC (pcglast37) as:
User = online
Password = ***** (ask someone)
Download data from SLAC:
Done automatically (M. Kuss).
Data available in the directory /data30/glast/pipelineData with same subdirectories as at SLAC.
You can check which runs have been reprocessed at SLAC by pipeline:
- go to go tohttps://confluence.slac.stanford.edu/display/BeamTest/Home (SLAC confluence page)
- go into "Operations" part of the page, and click into Data Monitoring
- click on GetData of the required RUN
- from the Root Files column save the merit and svac ntuples
a. click on merit/svac with the right button of the mouse and save the files in:
/home/online/OfflineMonitor/data/slac/standard_name_merit.root
_svac.root
(example: recon-v1r030603p4_700000684_merit_merit.root and svacTuple-v1r030603p4_700000684_svac_svac.root)
...
- where you find a list of runs.
- Deatailed informations about a given run can be found going back to the confluence page,
...
- down in the Data Analysis part, in the line Data Access click on Summary of Run Types
...
Run the OfflineMonitor
Shifters should run the OfflineMonitor version on pcglast37 in the directory /home/online/OfflineMonitor_Shift
The macro RunIt.C reads merit and BTtuple for a given run receiving in input the run information coded as following:
runnumber(5 digits)energy(6 digits)theta(2 digits)particle type(2 digits)magnetic_filed_current(3 digits)xposition(3 digits)
where: energy in MeV, theta in deg, current in Amp, xposition in mm
and the particle type is coded as: 01=e- 02=e+ 03=pions 04=all particles 05=muons 06=protons 07=Full brems 08=tagged photons
THEN PROCEED WITH THE FOLLOWING COMMANDS:
Create
Energy (in MeV)
Particle type (01=electron, 02=positrons, 03=pi-, 04=pi+, 05=muons, 06=protons, 00=tagged gammas)
x position (in mm only the integer part)
theta (in deg)
magnetic field (not available at the moment)
Creates a link to the downloaded data with the correct name:
Go to the directory /home/online/OfflineMonitor
...
_Shift and run the script link.pl with the online run number as argument, e.g. for run 1181
> ./link.pl 700001181
that creates a link in the directory /home/online/OfflineMonitor_Shift/data to the downloaded merit and BTtuples with the correct names
ln -s slac/recon-v1r030603p4_700000684_merit_merit.root "new file name_merit.root" ln -s slac/svacTuple-v1r030603p4_700000684_svac_svac.root and "new file name_BTtuple.root"
...
runnumber(5 digits)energy(6 digits)theta(2 digits)particle type(2 digits)magnetic filed current(3 digits)xposition(3 digits)
Example for the run downloaded (700000684)run 700001181: 706840010000001000120 711810025000007600201
The links (done by the script) will be:
ln -s slac/data30/glast/pipelineData/rootData/700001181/v4r0909p7/recon/recon-v1r030603p4v1r030603p5_700000684700001181_merit_merit.root 706840010000001000120root 711810025000007600201_merit.root
ln -s slac/data30/glast/pipelineData/rootData/700001181/v4r0909p7/svacTuple/v1r0p7/svacTuple-v1r030603p4v1r030603p5_700000684700001181_svac_svac.root 706840010000001000120711810025000007600201_BTtuple.root
To run the macro:
1 3. Open the file RunIiRunIt.C in /home/online/OfflineMonitor_Shift/ and put the encrypted name as
main("706840010000001000120711810025000007600201");
42. Run the macro
root > .x RunIt.C
...
- if MC data for that run configuration exist, histograms are compared to the corresponding MC
- otherwise only data distributions are shown
Results are saved in in /home/online/OfflineMonitor_Shift/output/Histos6840010000001000120Histos711810025000007600201.root
/home/online/OfflineMonitor_Shift/output/Report....70706840010000001000120.psBTtuple 711810025000007600201.ps
Report Result
On Confluence , in the "Operations" part of the page, in the section Data Taking edit and fill the Offline Monitor Logbook.
LIST OF VARIABLES IN THE PLOTS
For more details refer to descritpion of merit and BTtuple ( svac) tuples .
============= 1D Histo List ===================
// Tracker
\ Wiki Markup
// Tracker
--------------------------\-
TkrNumTracks Number of tracks found (Maximum is set by TkrRecon, currently 10)
Tkr1FirstLayer First layer in track (layer 0 is the bottom of the tracker)
Tkr1Gaps Total number of gaps in track
Tkr1\-
TkrNumTracks Number of tracks found (Maximum is set by TkrRecon, currently 10)
Tkr1FirstLayer First layer in track (layer 0 is the bottom of the tracker)
Tkr1Gaps Total number of gaps in track
Tkr1[X/Y/Z\]Dir Track \]Dir Track [x/y/z\] direction cosine
Vtx\cosine
Vtx[X/Y/Z\]Dir \]Dir [x/y/z\] direction cosine of the (1st) vertex
Vtx\vertex
Vtx[X/Y/Z\]0 \]0 [x/y/z\] coordinate of vertex; if the two tracks making up the vertex are nearly parallel, the coordinates of the vertex may become very large
Vtx\large
Vtx[X/Y/Z\]in \]in [x/y/z\] coordinate of entry point in the CU
DirErr PSF (only for tagged gammas)
// \CU
DirErr PSF (only for tagged gammas)
TkrNumDigis Number of TKR digis. A digi is produced whenever there is at least one strip hit in a silicon plane
// ------------------------\-
// Calorimeter
-
// Calorimeter
//------------------------\-
CalEnergyCorr Cal Energy corrected -
CalEnergyCorr Cal Energy corrected layer-by-layer for edges and leakage
Cal\leakage
Cal[X/Y/Z\]Ecntr Energy centroid in \]Ecntr Energy centroid in [x/y/z\]
CalMipRatio Ratio of measured energy to that expected from a minimum-ionizing particle
Cal\]
CalMipRatio Ratio of measured energy to that expected from a minimum-ionizing particle
Cal[X/Y/Z\]Dir \]Dir [x/y/z\] direction cosine of CAL "track"
CalTrackDoca Distance between the projected vertex (or track if only one track) and the energy centroid, evaluated at the z of the centroid
EnergyErr Error on photon reconstructed energy (only for tagged gammas)
CalTrackDoca Distance between the projected vertex (or track if only one track) and the energy centroid, evaluated at the z of the centroid
EnergyErr Error on photon reconstructed energy (only for tagged gammas)
CalTransRms rms of transverse position measurements
//------------------------\-
// ACD
-
// ACD
//-----------------------\-
AcdTotalEnergy Total energy deposited in ACD
AcdTileCount Number of tiles fired
-
AcdTotalEnergy Total energy deposited in ACD
AcdTileCount Number of tiles fired
//------------------------\-
// Trigger
-
// Trigger
//------------------------\-
GEM Conditions Summary word Trigger Summary word ROI = 0x01 CNO = 0x10
TKR = 0x02 PERIODIC = 0x2
CALLE = 0x04 SOLICITED = 0x4
CALHE = 0x08 EXTERNAL = -
GEM Conditions Summary word Trigger Summary word ROI = 0x01 CNO = 0x10
TKR = 0x02 PERIODIC = 0x2
CALLE = 0x04 SOLICITED = 0x4
CALHE = 0x08 EXTERNAL = 0x80
GEM Condition arrival times time distance in 50 ns ticks from the condition that opened the trigger window (30 ticks wide).
See section 4.13 in the GEM document for a detailed description.
GEM Condition arrival times for events with the corresponding ConditionSummary true
//-------------------------
// EVENT
//-------------------------
EvtEnergyCorr Event energy formed by adding the corrected tracker energy (TkrEnergyCorr) to the layer-by-layer corrected cal. energy CalEnergyCorr
//--------------------
// Ancillary
Wiki Markup
// Ancillary NO CORRECT INFO FROM ANCILLARY IN BTtuple YET
//--------------------
positiony\[0\] vs positionz\[0\]
positiony\[1\] vs positionz\[1\]
positiony\[2\] vs positionz\[2\]
positiony\[3\] vs positionz\[3\]
TAG_XYZ[3,4] X,Y,Z coordinates of highest cluster in each of the four silicon tagger station