Testing

First Runs    Second Set of Runs    IVTE Runs    Plots    Number of Events per File

First Runs

What is this format?
The subsystem subpackets should be the same as those defined for the 1999 GLAST testbeam:  CAL in 4 range mode where each range is stored in a separate subpacket, ACD same as testbeam, TKR is the same EXCEPT that the EOF bits have been modified to those that will be used for the balloon flight (0xbff) and only cables 0,3,5,6 are used to transmit data.  Also note that the controllers for planes 11 and 12 (layers 23, 24, 25) are different than they were for the test beam.  Here are the cable and controllers for these layers:

Plane Layer Cable Controller
11 23 (Y11) measures Y 5 6
12 24 (Y12) 1 7
12 25 (X12) 3 7

The ROOTWriter was modified in 2 ways to process these "special" data files:
1.  The EOF bits for the TKR were updated.
2.  The file readout/DataWord.h was modified to handle the layers mentioned above in a special manner so that the proper cable/controller pair would be assigned to the layers.  Here are the modifications.

NOTE:  The unphysical strip id 2047 on cable 0 was NOT masked out for these runs.  Strip Ids are offset by 64, just as they were for the BTEM.

Current List of Runs: (5, 10, 40, 41, 42)
The Original Raw data files are located at /nfs/farm/g/glast/u02/bfem/data
and available via ftp from:  ftp-glast.slac.stanford.edu/glast.u02/bfem/data

The Root Files are located at:  /nfs/farm/g/glast/u04/bfem/test/rootfiles
and available via ftp ftp-glast.slac.stanford.edu/glast.u04/bfem/test/rootfiles

Run Number

Original Raw File

Raw Root File

Plots

5 g00cos_r000005_20010425_110745_siue.dat g00cos_r000005_20010425_110745_siue.root here
10 g00cos_r000010_20010425_221908_siue.dat g00cos_r000010_20010425_221908_siue.root
40 g00cos_r000040_20010427_212254_siue.dat g00cos_r000040_20010427_212254_siue.root here
41 g00cos_r000041_20010427_224548_siue.dat g00cos_r000041_20010427_224548_siue.root
42 g00cos_r000042_20010427_234814_siue.dat g00cos_r000042_20010427_234814_siue.root

Second Set of Runs

TKR: Using cables 0, 3, 4, 5, 6 (picture of layers and cables) since controller 3 on cable 5 is bad.  But note, that is seems that the command to use Cable 4 and controller 3 on layer 15 (Y7) failed - there does not appear to be any TKR data for this layer in these runs - this is understood by Dave L. and company...

NOTE:  Fixed the mask used to ignore the "dummy strip id" 2047 on cable 0...so there should no longer be "unphysical" strip Ids in the Root files...
Strip Ids are offset by 64, just as they were for the BTEM.

Current List of Runs: (50, 51, 52, 53, 58, 64, 67)
The Original Raw data files are located at /nfs/farm/g/glast/u02/bfem/data
and available via ftp from:  ftp-glast.slac.stanford.edu/glast.u02/bfem/data

The Root Files are located at:  /nfs/farm/g/glast/u04/bfem/test/rootfiles
and available via ftp ftp-glast.slac.stanford.edu/glast.u04/bfem/test/rootfiles

Runs 50 through 67:

Run Number Original Raw File

Raw Root File

50 g00cos_r000050_20010505_140912_siue.dat g00cos_r000050_20010505_140912_siue.root
51 g00cos_r000051_20010505_142700_siue.dat g00cos_r000051_20010505_142700_siue.root
52 g00cos_r000052_20010505_143822_siue.dat g00cos_r000052_20010505_143822_siue.root
53 g00cos_r000053_20010505_154109_siue.dat g00cos_r000053_20010505_154109_siue.root
58 g00cos_r000058_20010505_182801_siue.dat g00cos_r000058_20010505_182801_siue.root
64 g00cos_r000064_20010505_200419_siue.dat g00cos_r000064_20010505_200419_siue.root
67 g00cos_r000067_20010505_201110_siue.dat g00cos_r000067_20010505_201110_siue.root

 

IVTE Runs

These runs are in the IVTE data format that will be used for the balloon.

Test Runs taken 5/3/2001

The Original raw data files are available on the SLAC /afs:  /afs/slac.stanford.edu/g/glast/flight/dat 
The Root Files are located at:  /nfs/farm/g/glast/u04/bfem/test/rootfiles
and available via ftp ftp-glast.slac.stanford.edu/glast.u04/bfem/test/rootfiles

Original IVTE Raw Data File Root File # of Events Plots
0988927629_0000.evt 0988927629_0000_ivte.root 2089

see here

0988937685_0000.evt 0988927929_0000_ivte.root 2092  
0988927929_0000.evt 0988927929_0000_ivte.root 2070  
0988937986_0000.evt 0988937986_0000_ivte.root 2072  

Test Runs taken 5/9/2001

The Root Files are located at:  /nfs/farm/g/glast/u04/bfem/test/rootfiles
and available via ftp ftp-glast.slac.stanford.edu/glast.u04/bfem/test/rootfiles

Notes:    Cable 2 of the ACD subsystem was disconnected, there will be no data seen for tile ids 200 and 210.
These are Cosmic Ray triggers.

Original IVTE Raw Data File Root File # of Events Plots
0989453186_0000.evt 0989453186_0000_ivte.root 1981 see here
0989453786_0000.evt 0989453786_0000_ivte.root 1980  

Test Runs 5/14/2001

Notes:  Still missing at least one cable for the ACD subsystem

Original IVTE Raw Data File Root File # of Events
0989889776_0000.evt 0989889776_0000_ivte.root 1990
0989890376_0000.evt 0989890376_0000_ivte.root 1979
0989890976_0000.evt 0989890976_0000_ivte.root 1986

Test Runs 5/22/2001

Notes:  All ACD cables are in place - there should be data available from all ACD channels.  TKR is using 'configuration 0'. CRC is being generated.  There is a difference in the TKR between these 2 sets of files...

Group 1

Original IVTE Raw Data File Root File # of Events Plots
0990573357_0000.evt 0990573357_0000_ivte.root 2036
0990573957_0000.evt 0990573957_0000_ivte.root 2032
0990574557_0000.evt 0990574557_0000_ivte.root 1995

Group 2

Original IVTE Raw Data File Root File # of Events Plots
0990582502_0000.evt 0990582502_0000_ivte.root 2007  
0990583103_0000.evt 0990583103_0000_ivte.root 2000  

Test Runs 5/25/01

Notes:  
There are 13 files, 12 of which contain 15 minutes worth of data. The thirteenth file contains only 10 minutes worth of data and I suspect was truncated by an error. I'm particularly interested to know the following:
a) Is the short file readable (all the way to the end)
b) Is there any evidence in the short file that the last event(s) are damaged
c) Does the data in the following file show good integrity.

Detector conditions are the same for all files:
            ACD: Nominal configuration, trigger (and veto) disabled.
            CAL: Nominal configuration, trigger disabled.
            TKR: "Standard" configuration=0.
            Noisy strips -not- masked.
            Usual three-in-a-row trigger.
            XGT: All on (including the one that was miswired I believe).

Original IVTE Raw Data File Root File # of Events Plots
0990830933_0000.evt      
0990831833_0000.evt 0990831833_0000_ivte.root 1910  
0990832435_0000.evt 0990832435_0000_ivte.root 1911  
0990833335_0000.evt      
0990834235_0000.evt      
0990835136_0000.evt 0990835136_0000_ivte.root    
0990836036_0000.evt 0990836036_0000_ivte.root    
0990836936_0000.evt 0990836936_0000_ivte.root    
0990837836_0000.evt 0990837836_0000_ivte.root 1915  
0990838736_0000.evt 0990838736_0000_ivte.root    
0990839636_0000.evt 0990839636_0000_ivte.root    
0990840537_0000.evt 0990840537_0000_ivte.root    
0990841437_0000.evt 0990841437_0000_ivte.root    

Test Runs 5/27/01

Notes:  
There are 36 files each containing 15 minutes worth of data.
Detector conditions are the same for all files:
        ACD: Nominal configuration, trigger (and veto) disabled.
        CAL: Nominal configuration, trigger disabled.
        TKR: "Standard" configuration=0.
        Noisy strips -not- masked.
        Usual three-in-a-row trigger.
        XGT: All on (including the one that was miswired I believe).

Original IVTE Raw Data File Root File # of Events Plots
0990987480_0000.evt 0990987480_0000_ivte.root 1942  
0990988380_0000.evt 0990988380_0000_ivte.root 1951  
0990989280_0000.evt 0990989280_0000_ivte.root    
0990990180_0000.evt 0990990180_0000_ivte.root    
0990991080_0000.evt 0990991080_0000_ivte.root    
0990991981_0000.evt 0990991981_0000_ivte.root    
0990992881_0000.evt 0990992881_0000_ivte.root    
0990993781_0000.evt 0990993781_0000_ivte.root    
0990994681_0000.evt 0990994681_0000_ivte.root    
       

 

How do we know the number of events per file?

Well..2 independent ways.  ROOTWriter will report the number of events that it processed.  However, to double check this ..  a modified version of Dave Lauben's ivtxInspect.c routine is used to determine the number of expected ivte packets per file.  Thus far, the number of events that ROOTWriter finds for each file, matches the number of events that ivtxInspect reports.