Changes between Version 5 and Version 6 of NightlyScienceV2

Timestamp:

Dec 21, 2010, 4:41:07 PM (16 years ago)

Author:

watersc1

Comment:

--

NightlyScienceV2

@@ -6 +6 @@
  1. An exposure is observed at the summit.
  1. The {{{summitcopy}}} pantasks populates the summitExp/summitImfile tables with the list of exposures available at the summit. It then downloads the fits files to MHPCC, and populates the newExp/newImfile tables.
- 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 {{{pending_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 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}}}.