Changes between Version 2 and Version 3 of NightlyScienceCode

Timestamp:

Mar 5, 2010, 2:23:17 PM (16 years ago)

Author:

watersc1

Comment:

--

NightlyScienceCode

@@ -28 +28 @@
 
 {{{automate_stacks.pl --date YYYY-MM-DD --check_chips}}}
+
 {{{automate_stacks.pl --date YYYY-MM-DD --queue_chips}}}
 
@@ -33 +34 @@
 
 {{{automate_stacks.pl --date YYYY-MM-DD --check_stacks}}}
+
 {{{automate_stacks.pl --date YYYY-MM-DD --queue_stacks}}}
+
 {{{automate_stacks.pl --date YYYY-MM-DD --queue_stacks --force_stack_count}}}
 
@@ -39 +42 @@
 
 Both chip and stack mode options support the --this_target_only and --this_filter_only which allow a specific target or filter to be queued without checking the rest.  This is safe because previously queued runs will not be duplicated.
+
 == automate_stacks.pl config file == 
 
+Each target in ippconfig/recipes/nightly_science.config has the following required known parameters:
+
+|| NAME  || STR || Target name. Used as the base of the data_group variable. ||
+|| TESS  || STR || Tessellation ID. ||
+|| OBSMODE || STR || obs_mode value from rawExp. This is a LIKE search, so % wildcards are supported. ||
+|| OBJECT || STR || object from rawExp.  This was not populated, so although it is supported, none of the current target uses it.||
+|| COMMENT || STR || comment from rawExp. Also a LIKE search. ||
+|| STACKABLE || BOOL || This flag determines whether or not nightly stacks can be made of this target. ||
+
+The known filters are also stored in this file, although this is only used while queueing stacks.
+
+The RETENTION_TIME value stores the number of days data should be stored before being marked for cleanup.  This is commented out (it is part of ns.initday.load), but is fully implemented.