The processing is in three steps
Time is (temporarily) measured from launch at JDStart. (It should be mission start time.) The history of course includes a pointing strategy, rocking by 35 degrees. See the TDS class Event::Exposure for a definition of the quantities.
The package DataChallenge is used to implement the above strategy. It "uses" Gleam, and contains the basic job options files for each of the three steps. The test_DataChallenge application is run automatically by the release manager, and is set to process step #3 on a file (src/test/incoming_99.9.root) containing 0.1 orbit-sec of incoming protons, from CrProtonMix at t=99.9 sec. I summarize the timing and results from running v0r1 (GR LATEST 1.167) on a Linux and a Windows 2000 server, both 2 GHz processors (I think for the former). There are 2737 incoming protons, producing 656 triggers. (So, 6.6 kHz.)
Machine | glast02.slac.stanford.edu | glast.phys.washington.edu |
---|---|---|
Operating system/compiler | rh7.2/gcc 2.95 | Window 2000 server/ vcc 7.0 |
Total CPU time (sec) | 708 | 185 |
Events passing the filter | 37 | 44 |
G4Generator CPU (sec) | 588 (83%) | 148 (80%) |
OnboardFilter CPU (sec) | 3.4 | 3.7 |
Output Files |
87026 digi_99.9.root 1430787 mc_99.9.root 51829 merit_99.9.root 653717 recon_99.9.root |
95,670 digi_99.9.root 1,527,178 mc_99.9.root 53,519 merit_99.9.root 725,145 recon_99.9.root |
Observations:
Notes:
Last updated: 08/31/2003 13:43:39 -0700
Toby Burnett