Changes between Version 6 and Version 7 of update_versus_magic

Timestamp:

Jan 7, 2010, 1:31:39 PM (16 years ago)

Author:

bills

Comment:

--

update_versus_magic

@@ -35 +35 @@
  * excised pixels from destreaking would need to be saved at all stages (deleted during cleaning)
  * psModules would need the ability recreate the original image by merging the excised pixels with the de-streaked image
+ * 
+
+This solution is interesting and we can implement it later if we find that Plan A doesn't meet our requirements.
 
 === Specific Implementation Tasks ===
@@ -69 +72 @@
 }}}
 
-This allows runs which have been cleaned but not yet magicked to updated.
+This insures that the updated images will be restored to the state they were in before cleanup. Allowing processing with magicked == 0 allows runs which have been cleaned but not yet magicked to updated. (It also allows update to work transparently for cameras that don't require magic de-streaking without a lot of tedious SQL editing by the ipp tools)
+
+
+==== chipRun update when rawExp has not been de-streaked ====
+
+Once we get into operations the raw images will be de-streaked and the excised pixels saved.
+Since we want to be able to easily reprocess data as the IPP analysis software evolves we have not been de-streaking the raw images.
+
+In order to fit in with the processing flow outlined in this note we will apply the streak mask after
+the chip processed images have been updated. The mask images with the destreak mask bits are saved in the camera stage. The camera stage files are relatively small and are not cleaned up.
 
 
 
-
-