IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links
wiki:ippToPsps_Detections

Version 2 (modified by rhenders, 16 years ago) ( diff )

--

The input for the detection batch is one IPP camera-stage smf file for a given exposure, as well as an associated DVO database from which to retrieve object, and other, IDs. One FITS file is generated for each exposure. The extensions are:

1 Primary extension
1 FrameMeta extension
1 ImageMeta extension per chip
1 Detection extension per chip
1 SkinnyObject extension per chip
1 ObjectCalColor extension per chip

So, 242 extensions in all, including the obligatory primary header. The 'object ID' is featured in the last three tables, and must remain unique across the exposure (it is generated within DVO). In the merged PSPS database, the primary key on the detections table is both the object ID and detection ID, meaning the the same object can appear in multiple, overlapping exposures as they will have different detection IDs.

Unresolved fields

PSPS field PSPS type PSPS Description Comments
FrameMeta
cameraIDSHORTcamera identifier 1?
cameraConfigID SHORT camera configuration identifier
analysisVerSTRINGIPP software analysis release need added to smf?
p1RecpSTRINGIPP phase 1 MD5 Checksum need added to smf?
p2RecipSTRINGIPP phase 2 MD5 Checksum need added to smf?
p3RecipSTRINGIPP phase 3 MD5 Checksum need added to smf?
numPhotoRefLONGnumber of photometric reference sources
calibModNumSHORTcalibration modification number for future
dataReleaseBYTEData release for future
ImageMeta
photoCalIDLONGphotometry reduction code identifier will use IPP dvo.photcodes in PSPS init batch
biasFLOATdetector bias level (unit = ADU) need added to smf?
biasScatFLOATscatter in bias level (unit = ADU) need added to smf?
numPhotoRefLONGnumber of photometric reference sources
psfModelIDLONGPSF model identifier need from smf?
detectorIDSHORT identifier for actual CCD chip
calibModNumSHORTcalibration modification numberfor future
dataReleaseBYTEData release for future
Detection
psfLikelihoodFLOATPSF likelihood need in smf
crLikelihoodFLOATLikelihood the source is a cosmic ray need added to smf?
historyModeNumSHORTmodification number in the O-D association historyfor future
dataReleaseBYTEData release when this detection was originally taken. Recalibrations do not affect this value.for future
SkinnyObject
projectionCellID LONGprojection cell identifier at discovery time ???
ObjectCalColor
calColorFLOAT color adopted for magnitude calculation (unit = mag) for future
calColorErrFLOAT error in calibrating color (unit = mag) for future




Note: See TracWiki for help on using the wiki.