P116 Reprocessing

status: Under Construction
last update: 1 October 2010

This page is a record of the configuration for the P116 reprocessing project, rebuilding FT1 files (and friends) for all of science data with new, extended event classifications.

• P116-FT1 - this task will read existing (P105+level1) MERIT files and produce FT1 (photons) + LS1 (merit-like FITS file for photons) + electron FITS file

Datafile names, versions and locations

Data file version numbers for this reprocessing will begin with v116.

XROOT location and file naming

Location template:

/glast/Data/Flight/Reprocess/<reprocessName>/<dataType>

Locations for P120:

/glast/Data/Flight/Reprocess/P116/ft1
/glast/Data/Flight/Reprocess/P116/electronft1
/glast/Data/Flight/Reprocess/P116/ls1

File naming:

Note: 'procVer' is a field added to the file name (and the keyword "PROC_VER" in the primary header) added to the FFD 5/12/2010. Ref: http://fermi.gsfc.nasa.gov/ssc/dev/current_documents/Science_DP_ICD_RevA.pdf

Example:

/glast/Data/Flight/Reprocess/P120/ft1/gll_ph_p116_r0239559565_v120.fit
/glast/Data/Flight/Reprocess/P120/electronft1/gll_el_p116_r0239559565_v120.fit
/glast/Data/Flight/Reprocess/P120/ls1/gll_ev_p116_r0239559565_v120.fit

DataCatalog location and naming

Logical directory and group template:

Data/Flight/Reprocess/<reprocessName>:<dataType>

Note that the <dataType> field (following the colon) is a DataCatalog 'group' name, and file names are of the form r<run#>.

Naming examples:

Data/Flight/Reprocess/P116:FT1 r0239557414
Data/Flight/Reprocess/P116:ELECTRONFT1 r0239557414
Data/Flight/Reprocess/P116:LS1 r0239557414

Data Sample

The currently defined data sample for P116 reprocessing includes:

Bookkeeping

1. (This page): Define ingredients of reprocessing (processing code/configuration changes)
2. Processing History database: http://glast-ground.slac.stanford.edu/HistoryProcessing/HProcessingRuns.jsp?processingname=P116
   1. List of all reprocessings
   2. List of all data runs reprocessed
   3. Pointers to all input data files (-> dataCatalog)
   4. Pointers to associated task processes (-> Pipeline II status)
3. Data Catalog database: http://glast-ground.slac.stanford.edu/DataCatalog/folder.jsp
   1. Lists of and pointers to all output data files
   2. Meta data associated with each output data product

P116-FT1

This task is roughly equivalent to the P105-FT1 task but with modernization.

Status chronology

• 10/1/2010 - Begin task construction

Configuration

Task Location	/nfs/farm/g/glast/u38/Reprocess-tasks/P116-FT1
Task Status	http://glast-ground.slac.stanford.edu/Pipeline-II/index.jsp
Input Data Selection	MERIT (from P105 & Level 1)
Input Run List	ftp://ftp-glast.slac.stanford.edu/glast.u38/Reprocess-tasks/P116-FT1/config/runFile.txt
Reprocessing Mode	reFT1
evtClassDefs	00-17-00 (TENTATIVE)
photon cut	TBD
eventClassifier	TBD
eventClassMap	TBD
s/c data	FT2 from P105 (runs 239557414 - 271844560), then from current Level 1 production
ScienceTools	09-18-04 (SCons build)
Code Variants	redhat4-i686-32bit-gcc34 and redhat5-i686-32bit-gcc41 (Optimized)
Diffuse Model	/afs/slac.stanford.edu/g/glast/ground/releases/analysisFiles/diffuse/v2/source_model_v02.xml ( https://confluence.slac.stanford.edu/display/SCIGRPS/Diffuse+Model+for+Analysis+of+LAT+Data )
Diffuse Response IRFs	????????????
IRFs	???????????????
Output Data Products	FT1, LS1, ELECTRONFT1

Processing chain for FITS data products

Note on 'Code Variant': The SLAC batch farm contains a mixture of architectures , both hardware (Intel/AMD 64-bit) and software (RedHat Enterprise Linux 4, and 5, gcc 3.4, 4.1, etc.).

Note on diffuse response calculation: (OBSOLETE)gtdiffrsp is called three times in succession. The first time with IRF P7_v2_diff and evclsmin==8, followed by IRF P7_v2_extrad and evclsmin==9, and finally IRF P7_v2_datac and evclsmin==10. The resulting FT1 file has six columns of diffuse response, two columns (galactic and extragalactic response) for each of the three IRFs. This creates a non-standard FT1 file by FSSC standards as they expect only five diffuse response columns.(OBSOLETE)

Timing