Changes between Version 3 and Version 4 of NightlyScienceV2

Timestamp:

Dec 21, 2010, 4:09:57 PM (16 years ago)

Author:

watersc1

Comment:

--

NightlyScienceV2

@@ -61 +61 @@
 
 These rules define how the detrend verify runs are queued.  Each has a {{{NAME}}} and use {{{DETTYPE,EXPTYPE}}} to determine the type of verify run to generate.  The reference detrend is set using the {{{REF_ID,REF_ITER}}} values.  If a {{{FILTER}}} value is set, then only exposures in that filter are used for the verification.  The number of exposures to use in the verification process is set by {{{MAX_EXP}}}.
+
+== State Values ==
+
+Nightly science v2 is less state dependent than v1, and the old state parameter {{{nsState}}} is no longer used to control processing. The main state to monitor is {{{nsObservingState}}}.  This shows whether nightly science believes we are {{{OBSERVING}}} or at {{{END_OF_NIGHT}}}.  While the state is {{{OBSERVING}}}, new exposures should be registering, burntooling, and automatically queuing to chip stage.  Once this changes to {{{END_OF_NIGHT}}}, stacks and diffs start checking to see if they are finished.
+
+Both stacks and diffs start in the states {{{nsStackState,nsDiffState = TOWARP,TOWARP}}}.  These signify that they are waiting for warps to finish.  The standard nightly science task only runs the {{{--queue_X}}} versions of the nightly_science.pl code, as these suitably block multi- and premature queuing.  The states will change to {{{STACKING,DIFFING}}} once they have attempted something.  After {{{END_OF_NIGHT}}}, these will switch to {{{FINISHED_STACKING,FINISHED_DIFFING}}} when all suitable stacks and diffs have been constructed.
+
+The ns.show.dates prints out the following values:
+{{{ YYYY-MM-DD nsState nsStackState nsDiffState nsObservingState }}}
+
 
 == Manual Operation Modes ==