Subframeselector freezes due to faulty red frame

[robwalkmann]

Hi,
in the attachment you'll find a faulty red subframe, which has been processed through calibration and cosmetic correction without any problems, but finally caused the Subframeselector to freeze Pixinsight. I only could kill the whole process, no way to get out.
I thought of some synchroniziation problems in parallel processing (quad-core was fully enabled) and reduced to one core only, but with the same result.

The whole image has a size of only 8k compressed, no idea, what happened during capturing.
SubframeSelector should help to identify this bad one ...

Thanks for helping.
Robert

[mschuster]

Hi Robert,

Thanks for the bug report, sorry for the trouble.

Your image contains only 172 non-zero pixels, some sort of failure during capture or preprocessing must have occurred.

The script works OK on Mac 10.11.4, although some of the statistical results are undefined, as expected for such a damaged image.

On Win 7 however I confirm the script fails to terminate. After star detection, the script runs the PixInsight process DynamicPSF via a PJSR interface, which fails to terminate for unknown reasons. I will forward this bug report to Juan for investigation.

As a workaround for now I suggest you use Blink to weed out your problematic images.

Thanks,
Mike

Here is the decompressed xisf:
https://dl.dropboxusercontent.com/u/109232477/PixInsight/Test/xM13_FLT%3DRed_BIN%3D1x1_DUR%3D30sec_TEMP%3D-23%2C6C_0005_c_cc.xisf

PS: In addition to the above problem, noise measures zero in this image, due to the many zero pixels. This results in various script problems on all platforms. I will release a new version of the script soon to fix this.

[mschuster]

Robert,

SubframeSelector version 1.10 fixes these problems, it will be available as a PixInsight software auto-update soon.

Regards,
Mike

PS: The new version also supports dialog resizing on all platforms.

[robwalkmann]

Hi Mike,
it's working now.

Thanks for the fast response.
Robert