HOW TO LOOK AT DATA
Login into the Offline PC as:
User = online
Password = ***** (ask someone)
Download data from SLAC:
- 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)
5. go back to the confluence page, go down in the Data Analysis part, in the line Data Access click on Summary of Run Types to get for the given run numer:
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/data
- creates the links:
ln -s slac/recon-v1r030603p4_700000684_merit_merit.root "new file name_merit.root"
ln -s slac/svacTuple-v1r030603p4_700000684_svac_svac.root "new file name_BTtuple.root"
where new file name is:
runnumber(5 digits)energy(6 digits)theta(2 digits)particle type(2 digits)magnetic filed(3 digits)xposition(3 digits)
Example for the run downloaded (700000684): 706840010000001000120
The links will be:
ln -s slac/recon-v1r030603p4_700000684_merit_merit.root 706840010000001000120_merit.root
ln -s slac/svacTuple-v1r030603p4_700000684_svac_svac.root 706840010000001000120_BTtuple.root
3. Open the file RunIi.C in /home/online/OfflineMonitor/ and put the encrypted name as
main("706840010000001000120");
4. Run the macro
root > .x RunIt.C
at the beginning check the output messages in the root window
run numer, energy, angle .... number of events in the file merit
It will open a ghostview window showing results:
- 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 /home/online/OfflineMonitor/output/Histos6840010000001000120.root
/home/online/OfflineMonitor/output/Report....70706840010000001000120.psBTtuple
LIST OF VARIABLES IN THE PLOTS
For more details refer to descritpion of merit and BTtuple (svac) tuples .
============= 1D Histo List ===================
// 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[X/Y/Z]Dir Track [x/y/z] direction cosine
Vtx[X/Y/Z]Dir [x/y/z] direction cosine of the (1st) vertex
Vtx[X/Y/Z]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[X/Y/Z]in [x/y/z] coordinate of entry point in the CU
DirErr PSF (only for tagged gammas)
// -------------------------
// Calorimeter
//-------------------------
CalEnergyCorr Cal Energy corrected layer-by-layer for edges and leakage
Cal[X/Y/Z]Ecntr Energy centroid in [x/y/z]
CalMipRatio Ratio of measured energy to that expected from a minimum-ionizing particle
Cal[X/Y/Z]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)
//-------------------------
// ACD
//------------------------
AcdTotalEnergy Total energy deposited in ACD
AcdTileCount Number of tiles fired
//-------------------------
// Trigger
//-------------------------
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
//--------------------
positiony[0] vs positionz[0]
positiony[1] vs positionz[1]
positiony[2] vs positionz[2]
positiony[3] vs positionz[3]