If you could post a link to one of the the failing files (in full resolution .xisf format) it might be possible to offer some suggestions. The errror reports are not enough to help diagnose the problem.
We really need to see one of the calibrated, debayered ..._c_d.xisf files that are causing the crash (it is not the raw .fits file that is being processed).
The link has all 19 subs debayered. My Pixinsight stopped working so I have uninstalled it and now I am restarting the computer. Something obviously has gone wrong not only with the latest version of my installed PI but the script Weighted Batch Pre- Processing.
Because you selected such a high gain, your images consist mostly of highly amplified noise and saturated stars. This is upsetting the subframe weighting analysis, which fails to weight the frames. Without weights, alignment can't auto-select a reference frame, and fails. If you unselect subframe weighting and provide a manual registration reference image (I used the uncalibrated debayered image of the first raw frame), then you can persuade the WBPP script to run to completion (see image below - with a bit of polishing). There is no problem here with PI or WBPP. The error messages really pointed out the problems with the data.
The main problem, however, is that the exposures are too short. It is tempting to try and use increased gain to compensate for this, but since you are not increasing the sensitivity, you are just amplifying the noise. If you had used lower gain you would not have saturated the few objects that are bright enough to be detected!
It's actually "0'dan kahramana", which is "zero to hero" in Turkish. "Zero-to-hero" is just the anime-fan name for the genre of anime plots where an initially weak character becomes superhuman. (No I'm not an anime fan!).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.