Datareader home Runlist Pilot File Stage6 Template Spectrum
For each run, a TTree with all the event parameters could be created and saved in root file. The TTrees names are run0, run1, run2 ... etc in the order of the run list.
One can study this file with root:> root data.rootSee http://root.cern.ch/ for more information about root.
root run0->Print() : provide the list of parameters
root run0->Draw("ut") : trigger rate
root run0->Draw("len","on"): image length in telescopes 2 for event reconstructed in the ON region
The summary file contain the results of the analysis with datareader. The format of the file is ascii and is wiki compatible.
A First part (DATA used) shows information concerning the data. It is composed of global information (duration,observation direction, background mode) and of a table of quality check run by run.
The table provides the following informations:
Date and run number (set the path length in the pilot file if that does not appear correctly) Duration used for the rate and the result of the check during the analysis. They should be the same. If not check the run quality or change the duration in the run list. Average elevation of the run (camera center). Oservation direction of the run as define in the first part (DATA). Number of telescope used in the analysis (should be 4 in good data) Mean pedestal standard deviation in dc (related to the NSB) Number of events of the run (problem occurred if it is abnormally low) Number of events which pass the cuts (problem occurred if it is abnormally low) Ratio of events which pass the cuts (problem occurred if it is abnormally low)
A second part gives the results for the tracked source direction or for the target source positions if they are defined in the pilot file. It is composed of a summary which combine the result of the whole run list and of a run-by-run detailed table. There is a summary and a table for each target defined in the pilot file.
The tables provide the following informations:
Date and run number (set the path length in the pilot file if it does not appear correctly). Duration of the run (used for the rate). Average elevation of the run (camera center). Oservation direction of the run as define in the first part (DATA). ON events number OFF events number and the number of OFF regions (or Rg if the ring background method was used) Excess (ON - beta OFF) Rate per min Significance
The Summaries before the tables provide about the same informations for the all run combined. They give also the sensitivity in sigma per hours (useful for the crab) and an upper limit of the rate (compare this limit to the crab rate at the same elevation to estimate the flux upper limit).
If the R.A./Decl. positions in the run list are not all the same (for instance for a sky survey) the result for the tracked direction does not make sens. In this case a target list have to be provide in the pilot file.
Figures showing the Excess and the significance as a function of the observation time is also produced with the summary output file. If there is no target these figure shows the result for the tracking direction. If there targets are defined, they shows the result for the first target source direction. This figure is useful to detect variability of the source.
c)Sky maps and histogram
The 2D maps show the result of the analysis in the field of view observed by the runs.
The provided figures are:
ON map: distribution of the direction of the events which pass the cuts OFF map: estimation of the cosmic-ray background Excess map: ON-OFF Significance map: Excess significance according the theta square cut. Rate map: Excess rate (per min) estimated with a Gaussian PSF define in the pilot file and corrected according the acceptance (calibrated for a 0.5 deg offset). Acceptance map: acceptance express in equivalent hours of observation at 0.5 deg from the camera center according to the acceptance fit. Acceptance fit: Shows the distribution of the events which pass the cuts as a function of the distance of the camera center and the fit of this distribution used for the acceptance. Theta square distribution. From the tracked source position or from the first target if targets are defined in the pilot file. Theta square distribution from OFF-source position is also shown if the background mode makes it possible. A fit with the point-like source function is also shown (parametres defined in the pilot file). Significance distribution: shows the histogram of significances represented in the map. A histogram without the region around the tracked source (or the first target if targets are defined) is also shown.
This distribution should be a Gaussian centered on 0 with a standard deviation of 1 (shown in green dashed line). The fit of the background distribution with a Gaussian is also shown (in black).
The output ".gle" file contains informations regarding the events which pass the cuts (gamma-rays like events). For each run it provides:
Modified Julian Day (int) Number of events which pass the cuts (int) E-W offset in degree (float) N-S offset in degree (float) analysis mode (int) : cf. run list R.A. and Decl. of the camera center in radian (float) Duration of the run in min (float)
The line with the run info start with a "R" and the following line are the events info:
Coordinate X and Y of the reconstructed direction in the camera coordinate (0,0 is the camera center) with the north up. (in deg) Reconstructed energyb in GeV (float) Elevation in rad (float) Time in hour of day (float)
The ".gle" file contain all the informations to produce maps (see Satge 6). It could be also used to create light curve and all kind of more deep analysis. This file is very light and enable to save time when one want change the maps settings without reprocessed everything.
Two ".gle" files can be also concatenated to create a big file with data of both run list.
The energy file are used to produce the spectrum of the source. (See section "spectrum".)
_on.els files contain the list of energy of events in the ON region which pass the cuts. _off.els files contain the list of energy of events in the OFF regions which pass the cuts. _simu.rcs files contain the list of reconstructed and simulated energy of simulation.