Hi Yuriy,
I have fully identified and fixed this bug, even before you reported it, in fact, as I have been working on the ImageIntegration tool a couple weeks ago
The bug happens upon the following conditions:
- Min/max pixel rejection algorithm selected.
- Most of the integrated frames have black borders at the same side of the image.
The explanation of this bug is as follows. The min/max rejection routine generates some pixels with non-finite values (NaN). The ScreenTransferFunction tool computes image statistics to calculate automatic stretch parameters, and the NaN or infinite values are not being properly handled by these routines, leading to a crash.
This bug is now fixed in the next version of the ImageIntegration module, which I'll publish during the next week. By the way, the new version provides excellent scalability and performance on multiprocessor/multicore machines.