IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 238 and Version 239 of ippToPsps


Ignore:
Timestamp:
Apr 2, 2012, 5:56:00 PM (14 years ago)
Author:
rhenders
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ippToPsps

    v238 v239  
    145145|| P2 || cam_id from gpc1 database ||
    146146|| ST || stack_id from gpc1 database ||
    147 || OB || INDEX from SkyTable.DAT file in DVO database ||
     147|| OB || INDEX from !SkyTable.DAT file in DVO database ||
    148148
    149149Each config requires an entry in the '''{{{epoch}}}''' column.  An ''epoch'' in the context of {{{ippToPsps}}} is the date that we count as ''the beginning''. If we loaded IPP data to PSPS once and only once, this would not be necessary: we would queue up all available exposures and stacks and simply load them. However, the early stages of the project have required multiple re-loads of data while the IPP perfects the science, necessitating that the same exposures and stacks are loaded more than once. Because {{{queue.py}}} queues available items by taking into account those that have already been published to PSPS, we have to give it an epoch date from which to accurately determine those exposure that have been loaded or not. Generally speaking, the epoch is reset every time we delete the main PSPS database.