Changes between Version 73 and Version 74 of Processing

Timestamp:

Jul 2, 2010, 9:23:58 AM (16 years ago)

Author:

rhenders

Comment:

--

Processing

@@ -194 +194 @@
 }}}
 
-
-
-= Finding and dealing with errors =
-
-As shown above, the "{{{pantasks: status}}}" command will display failures for a particular processing stage. A handy script also exists for monitoring all stages for a particular label (basically a shortcut for using the 'Night summary' page of the {{{ippmonitor}}} (see above)). It is found in {{{/tools}}} under the build directory. Example usage is shown below.
-
-{{{
-./processing_quick_check.pl --label SweetSpot.20100409
-}}}
-
-This provides the following output.
-
-{{{
-chip stage 
-SweetSpot.20100409 full 149 
-
-cam stage
-SweetSpot.20100409 full 149 
-
-fake stage
-SweetSpot.20100409 full 149 
-
-warp stage
-SweetSpot.20100409 full 149 
-
-stack stage
-
-diff stage
-SweetSpot.20100409 full 66 
-SweetSpot.20100409 new 1 
-
-magic stage
-
-magicDS stage
-
-dist stage
-
--------------------
-faults and log files
-
-diff new 4 neb://ipp034.0/gpc1/SweetSpot.20100409/2010/04/12/RINGS.V0/skycell.1500.091/RINGS.V0.skycell.1500.091.dif.50316.log  
-}}}
-
-The output highlights a problem at the diff stage, and in the "{{{faults and log files}}}" section, the relevant log file is listed, which can be viewed using {{{neb-tail}}} as below.
-
-{{{
-neb-tail neb://ipp034.0/gpc1/SweetSpot.20100409/2010/04/12/RINGS.V0/skycell.1500.091/RINGS.V0.skycell.1500.091.dif.50316.log
-}}}
-
-Another script in the {{{/tools}}} directory can be used to probe errors more thoroughly for a particular stage and label. The chip, camera, warp, stack, diff, magic and destreak stages are currently supported, as well as the use of multiple labels (wildcards are allowed). You can also search by a specific fault code (see table below), or limit the query. The output is the appropriate id and component, the machine it was run on, and the particular problem (e.g., a file that failed to be found, otherwise the resolved name of the processing log), all grouped into categories.  With such a list, it's easy to identify patterns, e.g., a few warps are failing because of a single corrupt camera mask file, or machine 'X' can't read files on machine 'Y'. For example, using the same label as above:
-
-{{{
-./errors.pl --dbhost ippdb01 --dbuser ipp --dbpass ipp --dbname gpc1 --label 'SweetSpot.20100409' --stage diff
-}}}
-
-Will produce
-
-{{{
-Total: 1
-
-Assertion failures: 1
-50316.skycell.1500.091(ippc08): /data/ipp034.0/nebulous/61/ef/244153882.gpc1:SweetSpot.20100409:2010:04:12:RINGS.V0:skycell.1500.091:RINGS.V0.skycell.1500.091.dif.50316.log
-}}}
-
-The 'fault codes' mentioned above are as follows.
+= Finding and dealing with {{{stdscience}}} errors =
+
+== Finding log files ==
+
+On the main [http://ipp004.ifa.hawaii.edu/ippMonitor/czartool_labels.php Czartool] display, if there are any faults, they are shown in parenthesis. These in fact form links that will take you to the relevant {{{ippMonitor}}} page for the processing stage and label in question. Here a table will list details of the offending exposures, one column of which is 'state' (which should be 'new'). Linking from these will display the log for that particular exposure (or chip) from which the error may be diagnosed.
+
+== Reverting ==
+
+Another column in the same tables is 'fault', which are populated with integer values with the following definitions:
 
 || '''Code''' || '''Description''' ||
@@ -270 +214 @@
 Note that {{{magic}}} has fault states greater than 6.
 
+The faults are often of value '2', which is more often than not an NFS error and can be resolved by 'reverting'.
+
 == Common issues ==