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.
I have noticed more lately that I am getting a weird pattern at some corners. It doesn't matter if it is a mosaic or a normal integration. Any idea what is behind this?
@imnewhere Which version of APP are you using? If a 2.0.0-betaX version, can you try with 2.0.0-beta9?
@imnewhere What kind of data are you integrating? OSC, mono or combined? What calibration data? I think the images you show are for a mosaic. Does this also happen in de individual panels? If yes, can you post an image that shows that?
@wvreeven it only happens on mono, and then I have only noticed it on shorter sets of subs regardless of total integration, for instance the following example has 2x 600s each of LRGB. Sometimes turning off MBB and LNC keeps it from happening, but not always. OSC is fine no matter how few subs there are. It will happen on a mosaic with a panel that happens to be a lower number of subs, but that same panel will do this when set as a normal integration of just that object. I have had this happen on multiple integrations and between light pollution removal and Photoshop I can make it not very noticeable, but on other things I have to crop it down past the pattern.
If you want I can upload the calibrated subs for a few different cases where this happens.
Hi @imnewhere,
What kind of normalization parameters are you using? And which settings for MBB and LNC ?
We fixed a bug a bug with the adaptive pedestal which was responsible for some normalization issues. In this case it seams that maybe enabling LNC is causing it, which is a known problem in the current implementation. Does your problem happen with LNC disabled and advanced normalization ?
Mabula
@mabula-adminÂ
For normalization I leave things as default on regular integrations and advanced on mosaics. I found that some would end up fine if I turn off MBB and LNC, though I normally run 10% MBB and 2nd degree 3 iterations on LNC. This one I left everything at defaults for the whole run other than checking the boxes for hot pixels, cold columns, and hot columns at default.
Okay, Can you upload the data on which this occurs and give me instructions exactly on how I should process it to reproduce this problem?
https://upload.astropixelprocessor.com/
username : upload
password : upload
Please make a folder with your new like ImNewHere-normalization-issue and let me know once uploaded, I will investigate as soon as possible.
Mabula
@mabula-adminÂ
I have uploaded what gave me the attached result. It was with 2nd degree LNC 3 iterations and with MBB enabled at 10%
I did testing to see if I could get it with LNC off, MBB off, or both off and I got results that were good.
