Changes between Version 6 and Version 7 of NightlyScienceV2

Timestamp:

Dec 21, 2010, 4:45:12 PM (16 years ago)

Author:

watersc1

Comment:

--

NightlyScienceV2

@@ -8 +8 @@
  1. The {{{registration}}} pantasks examines the downloaded fits images, and (using {{{register_imfile.pl}}}) registers an entry in the rawImfile table for each imfile (setting {{{data_state}}} to {{{check_burntool}}} and {{{burntool_state}}} to {{{0}}}).  It then examines the series of previous exposures, and determines if this newly registered imfile can be run through {{{burntool}}}.  This requires all previous imfiles known at the summit with the same {{{class_id}}} as the one under examination to have been registered and burntooled.  If {{{burntool}}} cannot be run at this time (most likely due to a previous imfile not being downloaded yet), {{{register_imfile.pl}}} sets the {{{data_state}}} to {{{pending_burntool}}} and exits.  If {{{burntool}}} can be run, it runs {{{ipp_apply_burntool_single.pl}}} and continues as below.
  1. The {{{registration}}} pantasks periodically runs {{{regtool -pendingburntoolimfile -date YYYY-MM-DD -valid_burntool 14}}} to examine the imfiles with {{{data_state = pending_burntool}}} and decide if they can now be burntooled.  If so, the appropriate {{{ipp_apply_burntool_single.pl}}} command is constructed and run.
- 1. {{{ipp_apply_burntool_single.pl}}} takes the uris for the imfile under consideration and the previous uri, runs {{{burntool}}} and if successful, sets {{{data_state = full}}} and {{{burntool_state = -14}}}.
+ 1. {{{ipp_apply_burntool_single.pl}}} takes the uris for the imfile under consideration and the previous uri, runs {{{burntool}}} and if successful, sets {{{data_state = full}}} and {{{burntool_state = -14}}}. If unsuccessful, there should be no change to the database entry and burntool should be retried automatically.  Some camera settings (32bit mode) are known to crash burntool, and will likely require manual intervention.
  1. {{{regtool -pendingexp}}} refuses to complete the registration of the full exposure and populate rawExp until all component imfiles have {{{data_state = full}}}.  This blocks the exposure level registration until all imfiles have been burntooled. {{{register_exp.pl}}} constructs the {{{regtool}}} command to populate rawExp, and decides if this exposure is a science exposure, based on the rules defined in the nightly_science.config file.  If it is not a science exposure, then the {{{end_stage}}} is set to {{{reg}}}, and nightly science is finished with it.  Science exposures have the appropriate values defined for the {{{label, data_group, dist_group, end_stage, tess_id, workdir, and reduction}}}, and after populating rawExp, an entry is written in chipRun queuing science processing on that exposure.
  1. While exposures are taken, the nightly science tasks periodically run to examine whether stacks and diffs can be created.