Changes between Version 2 and Version 3 of ippToPspsSa10Vacation

Timestamp:

Oct 29, 2012, 11:03:31 AM (14 years ago)

Author:

bills

Comment:

--

ippToPspsSa10Vacation

@@ -200 +200 @@
 I generally build the cam stage first and then the staticsky stage. For simplicity you can do both simultaneously (I don't think it matters):
 
+Bill edits: We are using the skycal stage not staticsky. I have updated the following to reflect that
+
 to queue the minidvodb stuff:
 {{{
-  survey.add.addstar SAS.cam SAS_v8 SAS.20121027 SAS.20121027 cam
-  survey.add.addstar SAS.staticsky SAS_v10 SAS.20121027 SAS.20121027 staticsky
-  add.minidvodb  SAS.20121027 SAS.20121027.MINI SAS.20121027 1 GPC1
-  add.label SAS.20121027
-}}}
-once you are satisfied that staticsky is working properly and doing the right stuff, you can turn on creation/merge of the merge dvodb:
-{{{
-  add.mergedvodb SAS.20121027
-  survey.add.mergedvodb SAS.20121027 SAS.20121027 SAS.20121027
-}}}
-Note that once the staticskys have completed, there will still be that last minidvodb that is in 'active', since it kicks to be merged after a day. If all the staticskys have been addstarred, you can set the state (with mysql) of the current active minidvodb for this to the state 'to_be_merged'  which will cause it to go get merged (wait for it...)
+  survey.add.addstar SAS.cam SAS_v8 SAS.20121029 SAS.20121029 cam
+  survey.add.addstar SAS.skycal SAS_v10 SAS.20121029 SAS.20121029 skycal
+  add.minidvodb  SAS.20121029 SAS.20121029.MINI SAS.20121029 1 GPC1
+  add.label SAS.20121029
+}}}
+once you are satisfied that skycal addstars are working properly and doing the right stuff, you can turn on creation/merge of the merge dvodb:
+{{{
+  add.mergedvodb SAS.20121029
+  survey.add.mergedvodb SAS.20121029 SAS.20121029 SAS.20121029
+}}}
+Note that once the skycals have completed, there will still be that last minidvodb that is in 'active', since it kicks to be merged after a day. If all the skycals have been addstarred, you can set the state (with mysql) of the current active minidvodb for this to the state 'to_be_merged'  which will cause it to go get merged (wait for it...)
 
 Once the merge dvodb is built, it needs to be 'spiffed':
 
-These are what I used last time (change SAS as needed)
-{{{
-relphot -averages -reset -update -boundary-tree ~ipp/RINGS.V3.tree.fits -D CAMERA gpc1 -D CATDIR /data/ipp005.0/gpc1/catdirs/SAS/20120901
-relastro -update-objects -reset -update -D CAMERA gpc1 -D CATDIR /data/ipp005.0/gpc1/catdirs/SAS/20120901
+These are the commands to use. (Edited to use the corrected tree file and to use the v10 catdir name
+{{{
+relphot -averages -reset -update -boundary-tree ~ipp/RINGS.V3.tree.v1.fits -D CAMERA gpc1 -D CATDIR /data/ipp005.0/gpc1/catdirs/SAS/20121029
+relastro -update-objects -reset -update -D CAMERA gpc1 -D CATDIR /data/ipp005.0/gpc1/catdirs/SAS/20121029
 }}}