We’re actually looking into this right now as part of our high-content screening work. Oftentimes, as images come off the scanner, something goes wrong with a single image and the machine may or may not correct for it. This usually causes the pipeline to fail outright.
Since the images in this case are always named in a consistent manner, we can check for image file naming mismatches or deletions (which is a tell-tale sign that a file is corrupt), and handle them accordingly. Only if there is an apparent naming inconsistency do we actually read the image to check on its integrity.
Right now, we’re testing this out on the front end, during the 1st cycle of LoadImages. However, it’s difficult to check a priori for corruption without reading the whole thing; MATLAB’s imfinfo is not that much quicker. Looking at file size consistency may be another way, but we’re finding that obtaining even that simple information for a large set of images can be very time-prohibitive.