Changes between Version 3 and Version 4 of update_versus_magic

Timestamp:

Jan 7, 2010, 12:24:44 PM (16 years ago)

Author:

bills

Comment:

--

update_versus_magic

@@ -14 +14 @@
 When a Run (chipRun, warpRun, or diffRun) is cleaned it's state in the database is set to 'cleaned'. The run is queued for update by changing it's state to 'update'. After the run has been updated it's state is set to 'full'.
 
-When a run has dependencies for example a warpRun needs the dependent chipRun's to be in full state. The 'pending' queries for the various ippTools enforce this.
+When a run has dependencies for example a warpRun needs the dependent chipRun's to be in full state. The various pending queries of the ippTools enforce this.
 
-We assume that the update is being performed because some user wants to see the pixels. For example the postage stamp server will need to queue update processing when stamps are requested from cleaned images. This means that the resulting images must have been destreaked, i.e. detected satellite streaks must be masked.
+We assume that the update is being performed because some user wants to see the pixels. For example the postage stamp server needs to queue update processing when stamps from cleaned images are requested.  This means that the resulting images must have been de-streaked, i.e. detected satellite streaks must be masked.
 
-There are two ways that the
+There are two ways that the de-streaked requirement can be met.
 
+ * A. By performing the update processing on input images that have been de-streaked
+ * B. By re-running the destreak program on images containing the streak pixels
+
+Plan A is much easier to implement in the context of normal IPP operations.
+
+
+