Changes between Version 14 and Version 15 of ippToPsps_ScratchDatabase

Timestamp:

Apr 17, 2012, 9:34:21 AM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps_ScratchDatabase

@@ -50 +50 @@
 Whenever connecting to a scratch database, {{{ippToPsps}}} programs first check that the DVO database you plan to use (as defined in the [wiki:ippToPsps#Loadingconfigs config]) correspond to the one currently ingested into the scratch database. If not, the user will be prompted and asked to confirm whether he or she wishes to switch. Care must be taken as you may have ingested many gigabytes of DVO data into a scratch database and all will be lost if you switch to a different DVO.
 
-The first three rows in the table above detail three DVO metadata files, {{{SkyTable.fits}}}, {{{Photcodes.dat}}} and {{{Images.dat}}}, which are detailed [below]. Following this are DVO detection files, eg {{{cpm}}}, {{{cpt}}} or {{{cps}}} files. By maintaining file modified dates of all files ingested, the [browser:trunk/ippToPsps/jython/dvo.py Dvo] class is able to operate a little like rsync and update any DVO files that may have changed on disk since the last time the scratch database was synchronized with DVO.
+The first three rows in the table above detail three DVO metadata files, {{{SkyTable.fits}}}, {{{Photcodes.dat}}} and {{{Images.dat}}}, which are detailed [wiki:ippToPsps_ScratchDatabase#dvoImagesdvoPhotcodesdvoSkyTable below]. Following this are DVO detection files, eg {{{cpm}}}, {{{cpt}}} or {{{cps}}} files. By maintaining file modified dates of all files ingested, the [browser:trunk/ippToPsps/jython/dvo.py Dvo] class is able to operate a little like rsync and update any DVO files that may have changed on disk since the last time the scratch database was synchronized with DVO.
 === {{{dvoDetection}}}/{{{dvoDetectionFull}}} ===