Changes between Version 68 and Version 69 of STS.refstack.20120510

Timestamp:

Jun 21, 2012, 1:02:08 PM (14 years ago)

Author:

Mark Huber

Comment:

--

STS.refstack.20120510

@@ -960 +960 @@
 
 Distribution to MOPS via publishing - 
- * setup? how to associate label to particular datastore location for this run for IPP-MOPS-TEST-2
+ * setup -- how to associate label to particular datastore location for this run for IPP-MOPS-TEST-2
 {{{
 
@@ -984 +984 @@
 }}}
 
+{{{
+pubtool -h -definerun
+
 -definerun:
   -set_label      set label
-  -client_id      search by client_id     -- should this be set client_id??
+  -client_id      search by client_id     -- should this be set client_id or is search include set to use this client_id??
   -label          set and search by label
   -data_group     search by data_group
@@ -998 +1001 @@
   -simple         use simple output format?
   -limit          limit result set
-
- * should simply be 
+}}}
+
+ * simply just  
 {{{
 pubtool -dbname gpc1 -definerun -label STS.mopsdiff.mehtest -simple -pretend
 
---> but how to make only to only go to client_id=12?
-}}}
-
-{{{
---> will need to add label to publishing + add info to stdscience to tell where to put out too -- this is what needed.. similar for distribution --
---> so what has used client_id 12? nothing
---> should add comment line for each entry field.. -- see survey.pro --  <tag>  <label>  <client_id>  <comment> 
---> so what does <tag> do? allows multiple entries per label and is a unique key, ie for the .ds for example to be able to push out to other locations being magicked, so not important now? still needs to be different so call STS.test
-
+--> but how to direct only to go to client_id=12?
+}}}
+
+ * survey.pro pantasks module in stdscience
+  * will need to add label to publishing + add info to stdscience to tell where to put out too -- this is what needed.. similar for distribution --
+  * what has used client_id 12? nothing permanent in the ~ipp/stdscience/input file.
+  * format to use in stdscience from survey.pro:   <tag>  <label>  <client_id>  <comment> 
+   * what does <tag> do? allows multiple entries per label and is a unique key. The .ds for example, to be able to push out to other locations being magicked (though not implemented now). Still should be different, so call STS.test
+
+{{{
 survey.add.publish STS.mopsdiff STS.mopsdiff.mehtest 12 NULL
 
 survey.del.publish STS.mopsdiff
-
---> careful STS.nightlyscience already defn to go to 5 --  survey.add.publish STS  STS.nightlyscience 5 NULL
---> faults! why is it trying to put to LAP?? and not just LAP, MOPS and MOPS-TEST too..
+--> to remove if needed
+}}}
+  * careful, STS.nightlyscience already defined to go to 5 --  survey.add.publish STS  STS.nightlyscience 5 NULL
+
+ * faults! why is it trying to put to LAP? and not just LAP, but MOPS and MOPS-TEST too..
+{{{
 system failure for: publish_file.pl --pub_id 422412 --camera GPC1 --workdir neb://any/gpc1/IPP-MOPS-LAP --product IPP-MOPS-LAP --stage diff --stage_id 242192 --output_forma
 t 2 --redirect-output --need-magic --dbname gpc1 --verbose
 }}}
 
- * run manually 
+ * run manually and see what is happening
 {{{
 publish_file.pl --pub_id 422376 --camera GPC1 --workdir neb://any/gpc1/IPP-MOPS-TEST-2/ --product IPP-MOPS-TEST-2 --stage diff --stage_id 242198 --output_format 2 --redirect-output --dbname gpc1 --verbose
 
-
 neb://any/gpc1/IPP-MOPS-TEST-2/
---> loads of things in this dir - and why reports many not found because cleaned?
-}}}
-
- * should be careful running pubtool and using survey task, pubtool generically loaded for all then..
-
- * fault from log -- could this astrom issue be because STS fields or improper run?
+--> many things in this directory -- and why reports many not found because cleaned?
+}}}
+
+'''-- MISTAKE -- should be careful manually running pubtool and loading into survey task'''
+
+ * fault from specific log -- could this astrom issue be because STS fields or improper run?
 {{{
 neb://any/gpc1/IPP-MOPS-TEST-2//IPP-MOPS-TEST-2.422401.log
@@ -1042 +1049 @@
 Running [/home/panstarrs/ipp/psconfig/ipp-20120404.lin64/bin/pubtool -add -pub_id 422401 -path_base neb://any/gpc1/IPP-MOPS-TEST-2//IPP-MOPS-TEST-2.422401 -dtime_script 2.99998372793198 -hostname ippc10 -fault 2 -dbname gpc1]...
 
-astrom is sqrt($comp->{sigma_ra_2}**2 + $comp->{sigma_dec_2}**2)
-}}}
-
-{{{
+--> note astrom is sqrt($comp->{sigma_ra_2}**2 + $comp->{sigma_dec_2}**2)
+
+--> the diffim this is for 
 neb://ipp007.0/meh/STS.mopsdiff.mehtest/STS.V4/skycell.1.02/STS.V4.skycell.1.02.WS.dif.242223
 meh/STS.mopsdiff.mehtest/STS.V4/skycell.1.02/STS.V4.skycell.1.02.WS.dif.242223.cmf
@@ -1053 +1059 @@
 /data/ipp007.0/nebulous/14/91/2095815037.meh:STS.mopsdiff.mehtest:STS.V4:skycell.1.02:STS.V4.skycell.1.02.WS.dif.242223.inv.cmf
 
-neb://ipp008.0/meh/STS.mopsdiff.mehtest/STS.V4/skycell.1.03/STS.V4.skycell.1.03.WS.dif.242223 
-
---> publish_file.pl called from publish.pro - 
+--> and publish_file.pl called from publish.pro - 
 $run = publish_file.pl --pub_id $PUB_ID --camera $CAMERA --workdir $WORKDIR --product $PRODUCT --stage $STAGE --stage_id $STAGE_ID --output_format $OUTPUT_FORMAT --redirect-output        
                                              
@@ -1061 +1065 @@
 }}}
 
- * attempt to revert - 
+ * attempt to revert - not going to fix 
 {{{
 pubtool -dbname gpc1 -revert -fault 2 -pub_id 422401
 }}}
-  * does it still need to be added to distribution so that it ends up on the datastore? no looks like in the log that pubtool is run
-
- * publish cleanup/drop - 
+
+ * publish cleanup -- drop all the extra runs trying to publish to the other client_id
 {{{
 pubtool -dbname gpc1 -updaterun -set_state drop -label STS.mopsdiff.mehtest -client_id 1
@@ -1073 +1076 @@
 pubtool -dbname gpc1 -updaterun -set_state drop -label STS.mopsdiff.mehtest -client_id 13
 --> leaves 27 with client_id=12 are all valid? look at stage_id
+
 select pub_id,diff_id,diffRun.data_group from publishRun join publishDone using (pub_id) join diffRun  where publishRun.label like "STS.mopsdiff.mehtest" and publishRun.state="new" and diff_id=stage_id;
---> missing 110918 oddly, they've ended up in another client_id.. ugh..
+--> missing 20110918 oddly, they've ended up in another client_id.. 
 }}}