IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 11 and Version 12 of ippToPsps


Ignore:
Timestamp:
Feb 12, 2010, 4:22:53 PM (16 years ago)
Author:
rhenders
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ippToPsps

    v11 v12  
    88= Introduction =
    99
    10 {{{ippToPsps}}} is the interface between IPP and PSPS. It generates FITS files from IPP data that are suitable for consumption into the PSPS database. In short, {{{ippToPsps}}} creates FITS files from data found in IPP {{{smf}}} and {{{cmf}}} files, as well as relevant DVO databases, then publishes them to a datastore in the form of ''jobs''. On the PSPS side, the DXLayer polls the datastore, collects jobs when they become available, converts the contents to {{csv}} files then sends them on to special MSSQL loader software, which inserts them into the PSPS database. Ultimately there will be feedback from PSPS regarding errors in the received data, to which {{{ippToPsps}}} will need to respond.
     10{{{ippToPsps}}} is the interface between IPP and PSPS. In short, {{{ippToPsps}}} creates FITS files from data found in IPP {{{smf}}} and {{{cmf}}} files, as well as relevant DVO databases, then publishes them to a datastore in the form of ''jobs''. On the PSPS side, the DXLayer polls the datastore, collects jobs when they become available, converts the contents to {{csv}} files then sends them on to a special MSSQL loader software, which inserts them into the PSPS database. Ultimately there will be feedback from PSPS regarding errors in the received data, to which {{{ippToPsps}}} will need to respond.
    1111
    12 It is intended that the binary tables in the FITS files generated by {{{ippToPsps}}} match the PSPS database schemas perfectly, the consequence being that any alterations to the PSPS database schema will require changes to {{{ippToPsps}}} code.
     12It is intended that the binary tables in the FITS files generated by {{{ippToPsps}}} will match the PSPS database schemas perfectly, the consequence being that any alterations to the PSPS database schema will only require changes to {{{ippToPsps}}} code, and not the DXLayer. A certain amount of data validation will be performed by {{ippToPsps}} before publication
    1313
    1414= {{{ippToPsps}}} products =
     
    1919 * '''Diffs'''
    2020 * '''Stacks'''
     21
     22= Architecture =
     23
     24{{ippToPsps}} is a C program within the IPP build. When given the correct arguments it will generate a single FITS for the specified product (above). The program is run from a perl script, which itself is provided ... in order to generate the arguments necessary to run {{ippToPsps}}.
     25
     26= Input and output =
     27
     28== Detections ==
     29
     30'''Input'''
     31
     32Input is one {{smf}} file for a given exposure and an associated DVO database from which to retrieve object IDs.
     33
     34'''Output'''
     35
     36 A FITS output file is generated with the following extensions:
     37
     381 {{{'''FrameMeta'''}}} extension
     391 {{{'''ImageMeta'''}}} extension per chip
     401 {{{'''Detection'''}}} extension per chip
     41
     42'''Validation'''
     43
     44Some validation is performed to aid the data's insertion into the PSPS database.
     45
     46== Diffs ==
     47
     48'''Input'''
     49
     50A set of {{cmf}} files, one for each skycell covered by a particular exposure.
     51
     52'''Output'''
     53
     54A FITS output file is generated with the following extensions:
     55
     56...
     57
     58'''Validation'''
    2159
    2260= Unresolved fields =