FLIGHT RUNS

Run 53    Flight Runs 54 and 55    Rescued Data

ROOT files of the two telemetry ivte files from the balloon flight are available, plus one ivte file generated while on the ground before the flight.  The original binary data files are available from SLAC FTP:  ftp-glast.slac.stanford.edu/glast.u02/bfem/data/rlf
The most recent version of these runs were rooted using ROOTWriter v5r9, and v2r9p1 of digiRootData.  

There were earlier versions of these ROOT files, here is a page describing the versions and the additions/changes made with each version.

The data files are available from SLAC NFS or via FTP:
/nfs/farm/g/glast/u05/bfem/data/flight/RWv5r9_DIGIv2r9_BFEMAPPv1r10
OR
ftp-glast.slac.stanford.edu/glast.u05/bfem/data/flight/RWv5r9_DIGIv2r9_BFEMAPPv1r10

There is an additional column in the following tables, denoting whether there is Reconstruction data available.  If so, the files are located in the same directory where you can obtain the raw ROOT file.  For each file, there is are 2 associated reconstruction files, one called *-ntuple.root and the other called *-rec.root.  The ntuple file contains summary information about the run, including some useful items used for background rejection.  This is the same collection of ntuple elements being used for the PDR.  The rec.root file contains the full Recon ROOT tree, including all details about the reconstruction - including all of the tracks found by TkrRecon.

Taken while on the ground:

Original EVT file Root file Number of Events Integrity 
Check
Recon
Available?
nsbf_r000053_20010804_072159_ivte.dat nsbf_r000053_20010804_072159_ivte-raw.root

30529

here

YES

Flight data:

Here is the command history as reported by Tony Waite (note on-board files were limited to 1 Gbyte...not 2 Gbytes)

Note that Run 54 contains data from the beginning of the balloon flight, both while the disks were on, and after the disks were turned off.  There are multiple runs in these files - where I have arbitrarily assigned the run numbers as 5400..5401..5402.. etc.  Similarly for runs 53 (5300...5301)  and 55 (5500..5501).  Now that run numbers are in the files...it is easy to determine which events were associated with the time where the disks were still on.  I may divide run 54 into separate files, denoting those events that were taken with the disks on, and those taken after the disks were off.  Run 55 was taken after the disks were powered down.

 

Original EVT file Root file Number of Events Integrity 
Check
Recon
Available?
nsbf_r000054_20010804_104748_ivte.dat nsbf_r000054_20010804_104748_ivte-raw.root 109866 here YES
nsbf_r000055_20010804_143059_ivte.dat nsbf_r000055_20010804_143059_ivte-raw.root 104819 here YES