UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Today I tried doing a 2-panel mosaic integration (~10% overlap) for the first time, but when I do the mosaic integration, the result has lot of what I can only describe as hot red, green, and blue artifacts (see attached image), all apparently the same shape. I used dark frames from my library that were done at the same exposure time and temp as my new lights and took flats and dark flats after the session. The only changes to default settings were:
- RGGB
- Ha-OIII Color algorithm (I also see the artifacts on extract Ha and extract OIII, though they're only readily apparent after combining into RGB).
- 32-bit masters
- use dynamic distortion correction
- 10 scale stop (as recommended)
- mosaic registration mode
- 10% MBB (as recommended)
When I go back to normal registration on one panel alone (dropping scale stop back to 5), I do not get these artifacts, so it seems related to doing the mosaic. Should I be trying other settings?
Happy to provide all data for troubleshooting.
When you do the extract algorithms, did you see if the darks were actually applied to the lights? You can check by loading the lights (with the extract algorithm), adding the masterdark, then switching to "l-calibrated" on top of the window and see if that frame is getting calibrated.
Good call. It does appear to get applied because I see hot pixels disappear but it's not getting all of the hot pixels. I guess I need a better BPM that the one automatic produces? That said, if I fully integrate one panel of my lights normally, I see no hot pixels in the final image (outlier rejection?). With mosaic integration, all of those hot pixels not caught by the BPM aren't getting sorted out.
It may help to switch off the automatic setting in the integrate tab to "average" and then the options for rejection can be changed. You can try to lower the kappa high so it rejects more.
Another thing might be the darks, they should contain almost all the hot pixels, so I'm wondering if those are exactly the same iso and such as the lights? For a very good BPM it's a good idea to take a very long dark, like 10 min or so, it will then have as many hot pixels as the sensor might generate and should then correct for those. A BPM is never destructive to your data, so having more pixels in there if your lights are not having them (due to lower exposures) is no problem.
Â
Did you manage to get rid of these artifacts? I got the same problem when integrating with drizzle. Also seem to be there when not drizzling only less prominent. Creating a new BPM helped with getting rid of these artifacts 100% with a lower kappa of 2.0 but it introduced pretty bad artifacts around the stars. So not sure what to do now.
