IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 204 and Version 205 of ippToPsps


Ignore:
Timestamp:
Mar 9, 2012, 2:49:51 PM (14 years ago)
Author:
rhenders
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ippToPsps

    v204 v205  
    121121
    122122The master list of items to be processed comes from the gpc1 {{{addRun}}} table, which lists all items currently merged into the DVO database we are using. From this list, {{{queue.py}}} subtracts items that have already been successfully loaded to the datastore already, as well as items that have routinely failed to process, and queues up the remainder.
     123
     124Each 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.
    123125== loader.py ==
    124126