Changes between Version 33 and Version 34 of ippToPsps
- Timestamp:
- Mar 9, 2010, 12:07:08 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ippToPsps
v33 v34 10 10 = Introduction = 11 11 12 {{{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, then converts the contents to {{{csv}}} files before sending them on to special MSSQL loader software, which insertsthem into the PSPS database. Ultimately there will be feedback from PSPS regarding errors in the received data, to which {{{ippToPsps}}} will need to respond.12 {{{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, then converts the contents to {{{csv}}} files before sending them on to special MSSQL loader software, which ''merges'' 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. 13 13 14 14 It 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 affect {{{ippToPsps}}} code, and not the DXLayer. A certain amount of data validation will be performed by {{{ippToPsps}}} before publication. … … 18 18 == ippToPsps == 19 19 20 {{{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 generates a list of exposure IDs based on arguments provided by the user (label etc). An instance of {{{ippToPsps}}} is run per exposure ID. 20 {{{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 generates a list of exposure IDs based on arguments provided by the user (label etc). An instance of {{{ippToPsps}}} is run per exposure ID. Upon completion, the calling script publishes bundles the resultant FITS files up as a ''job'', then publishes it to the datastore, ready for the DXLayer to pick it up. 21 21 22 22 == Configuration == … … 26 26 === FITS table shapes === 27 27 28 XML files detailing PSPS database tables are used to automatically generate equivalent FITS tables. Because the PSPS schema can change, and we want to avoid code changes as much as possible, these XML files are created using a script ({{{pspsSchema2xml.pl}}}), so that whenever the schema changes, new configs can easily be created. The table shape configs are: 29 28 XML files detailing PSPS database tables are used to automatically generate equivalent FITS tables. Because the PSPS schema can change, and we want to avoid code changes as much as possible, these XML files are created using a script ({{{pspsSchema2xml.pl}}}) so that whenever the schema changes, new configs can easily be generated. The table shape configs are: 30 29 31 30 {{{tables_init.xml}}}[[BR]] … … 38 37 Most data to be loaded into the FITS tables comes from {{{smf}}} files. For many columns, there is a direct mapping between the the {{{smf}}} and the PSPS database column. These mappings are held, in XML format, in ... 39 38 40 The initialisation batch contains metadata that describes valid contents for the other batch types. Because these values may also change, these are held in an editable XML file as...39 The initialisation batch contains metadata that describes valid contents for the other batch types. Because these values will be in a state of flux for awhile, these are held in an editable XML file as... 41 40 42 41 == DXLayer ==
