P115 Reprocessing
status: In Progress Complete
last update: 8 15 July 2010
This page is a record of the configuration for the P115 reprocessing project, motivated by the Pass 7.2 event classification. This project involves reprocessing with Pass7 classification trees and (ultimately) new IRFs. The name "P115" derives from the word "processing" and the initial file version to be used for the output data products, e.g., r0123456789_v115_merit.root.
...
- 9 Jul 2010 - Assemble task
- 12 Jul 2010 - After a 20-run test, begin production processing
- 15 Jul 2010 - Task complete
Configuration
Task Location | /nfs/farm/g/glast/u38/Reprocess-tasks/P115-LEO-FT1 | |||
Task Status | http://glast-ground.slac.stanford.edu/Pipeline-II/index.jsp![]() | |||
Input Data Selection | MERIT (from P106-LEO-MERIT), FT2 (from P110-FT2) | |||
Input Run List | ftp://ftp-glast.slac.stanford.edu/glast.u38/Reprocess-tasks/P115-LEO-FT1/config/runFile.txt![]() | |||
evtClassDefs | 00-16-00 | |||
meritFilter | pass7_FSW_cuts, | |||
eventClassifier | Pass7_Classifier.py | |||
ScienceTools | 09-17-00 (SCons build) | |||
Code Variant | redhat4-i686-32bit-gcc34 or redhat5-i686-32bit-gcc41 | |||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7ae8256c454fb03b-bfcea8c5-461d4f6d-ae5a93c1-0fa940c10087562bfb113851"><ac:plain-text-body><![CDATA[ | Diffuse Model | /afs/slac.stanford.edu/g/glast/ground/releases/analysisFiles/diffuse/v2/source_model_v02.xml [[Ref | https://confluence.slac.stanford.edu/display/SCIGRPS/Diffuse+Model+for+Analysis+of+LAT+Data]] | ]]></ac:plain-text-body></ac:structured-macro> |
Diffuse Response IRFs | P7_v2_diff, P7_v2_extrad, P7_v2_datac | |||
IRFs | implemented as 'custom irf', files in /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/IRFS/Pass7.2 | |||
Output Data Products |
...
Wiki Markup |
---|
Timing is dominated by the gtdiffrsp steps in the mergeClumps job step. This app is called three times to handle the event classes of interest. There is a wide range of processing times due to: different classes of batch machines; different numbers of events to process; batch jobs being temporarily put into system suspend (SSUSP) states \[due to pre-emptive queues\]; or, possibly, due to processing dependencies in the data. Elapsed processing time for a single run ranges from 4 to 12+ hours (assuming no shortage of batch machines). The average CPU time per clump is 360 min +/- 160 min. |
Thirteen of 200 jobs required xxl batch queue and then took >30 hours to complete.