Changes between Version 5 and Version 6 of MOPS.dailytestset

Timestamp:

May 2, 2018, 11:25:03 AM (8 years ago)

Author:

Mark Huber

Comment:

--

MOPS.dailytestset

@@ -66 +66 @@
 
 
-Initial run description (until script finished) for daily test to run in the current nightly processing account and ops tag  -- normal chip/cam/warp, WWdiff v12,v34 and publishing
+Initial auto-run description (until script finished) for daily test to run in the current nightly processing account and ops tag  -- normal chip/cam/warp, WWdiff v12,v34 and publishing
  * chip-cam-warp commands --
 {{{
@@ -79 +79 @@
 }}}
  
- * WWdiffs to queue -- o6370g0351o-o6370g0373o, o6370g0395o-o6370g0417o (warp_id - template_warp_id)
+ * WWdiffs to queue -- o6370g0351o-o6370g0373o, o6370g0395o-o6370g0417o (warp_id - template_warp_id) -- until setup to queue like nightly science
 {{{
 difftool -dbname gpc1 -definewarpwarp -warp_id 1615271 -template_warp_id 1615273 -backwards -set_workdir neb://@HOST@.0/gpc1/MOPS.dailytestset.20150815 -set_dist_group NULL -set_label MOPS.dailytestset -set_data_group MOPS.dailytestset.20150815 -set_reduction SWEETSPOT -simple -pretend
@@ -91 +91 @@
 }}}
 
- * publication location on datastore -- IPP-MOPS-dailytestset, client_id 16 -- was lost in the move to ITC and needs to be restored, likely needs to just point to ipp113 in db
+ * publication location on datastore -- IPP-MOPS-dailytestset, client_id 16 -- was lost in the move to ITC and needs to be restored, likely needs to just point to ipp113 in db, should not be auto-run until MOPS is ready to use and checks activated on IPP side before/after publishing
 {{{
 pubtool -dbname gpc1 -definerun -set_label MOPS.dailytestset -data_group MOPS.dailytestset.20150815 -client_id 16 -simple -pretend