Changes between Version 51 and Version 52 of Processing

Timestamp:

May 5, 2010, 4:04:56 PM (16 years ago)

Author:

watersc1

Comment:

--

Processing

@@ -294 +294 @@
 If some of the data has already been processed (i.e. state!={{{new}}}), then {{{cleanup}}} must be employed. TODO more here
 
+== Running the microtest scripts ==
+
+The microtest data should be correctly automated, but still requires a script to be manually run. The basic pantasks tasks to reduce the microtest data are included in the stdscience/input file, in the add.microtest macro:
+
+{{{
+macro add.microtest
+  add.label microtestMD07.nightlyscience
+  add.label microtestMD07.noPattern.nightlyscience
+
+  survey.add.WSdiff microtestMD07.nightlyscience MD07.refstack.20100330 microtestMD07 neb://@HOST@.0/gpc1
+  survey.add.WSdiff microtestMD07.noPattern.nightlyscience MD07.refstack.20100330 microtestMD07.noPattern neb://@HOST@.0/gpc1
+  
+  survey.add.magic microtestMD07.nightlyscience /data/ipp050.0/gpc1_destreak
+  survey.add.magic microtestMD07.noPattern.nightlyscience /data/ipp050.0/gpc1_destreak
+end
+}}}
+
+Once the two labels have made it through magic, the microtest.pl script can be run. You'll need to have ppCoord built and in your path.  This isn't built by
+psbuild.  You just need to go into the ppViz directory and do {{{psautogen --enable-optimize && make && make install}}}. This script relies on VerifyStreaks having been run on the data as part of Magic (and being in the proper place).  Note that if the !VerifyStreaks binary could not be found in the course of the Magic processing, this will have be skipped.  The script is then run as:
+
+{{{
+microtest.pl --dbhost ippdb01 --dbuser ipp --dbpass XXX --dbname gpc1 --label microtestMD07.nightlyscience --data_group microtestMD07.20XXYYZZ --verbose
+}}}
+
+
+
 = Finding and dealing with errors =