Changes between Version 1 and Version 2 of NightlyScienceCode

Timestamp:

Mar 1, 2010, 6:11:27 PM (16 years ago)

Author:

watersc1

Comment:

--

NightlyScienceCode

@@ -1 +1 @@
 == Nightly Science: pantasks utilities ==
 
-ns.add.date YYYY-MM-DD
-
-ns.show.dates
-
-ns.del.date
-
-ns.set.date YYYY-MM-DD STATE
+||{{{ ns.add.date YYYY-MM-DD }}}||Add a date to be processed.||
+||{{{ns.show.dates}}}||List the dates currently in the book, along with their associated states.||
+||{{{ns.del.date}}}||Remove a date from processing (dates that make it to stack are automatically removed).||
+||{{{ns.set.date YYYY-MM-DD STATE}}}||Set the state for a given date.||
 
 == State values: ==
@@ -24 +21 @@
 == automate_stacks.pl script ==
 
+Useful modes for manually checking and queueing data:
 
+{{{automate_stacks.pl --date YYYY-MM-DD --check_registration}}}
+
+Confirm that registration is complete, and all needed exposures are available.  If exposures are missing (due to an incomplete download or registration error), they are listed along with a note stating whether they are important to the automation or not.
+
+{{{automate_stacks.pl --date YYYY-MM-DD --check_chips}}}
+{{{automate_stacks.pl --date YYYY-MM-DD --queue_chips}}}
+
+The first checks the chips to see if they're ready to be queued (confirms that burntool has finished for all exposures), and the second issues the appropriate chiptool commands.  
+
+{{{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}}}
+
+Similar to the chip mode options, check the number of warps against the input exposures to determine if all the warps for a stack are finished, and queue them if so.  The --force_stack_count allows this counting to be skipped if an exposure is known to have a uncorrectable error.
+
+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 ==