2023-03-15: APP 2.0.0-beta14 has been released !
IMPROVED FRAME LIST, sorting on column header click and you can move the columns now which will be preserved between restarts.
We are very close now to releasing APP 2.0.0 stable with a complete printable manual...
Astro Pixel Processor Windows 64-bit
Astro Pixel Processor macOS Intel 64-bit
Astro Pixel Processor macOS Apple M Silicon 64-bit
Astro Pixel Processor Linux DEB 64-bit
Astro Pixel Processor Linux RPM 64-bit
on the left I have integrated 36 panels only loading hydrogen into APP. On the right, I have loaded my Ha and Oiii frames and gotten a bad result. My oxygen mosaic also looks bad. Settings remained constant in each case, the only change was loading my oxygen files, which somehow messed up my hydrogen image. I think APP is not choosing an integration reference per filter, messing up the result. I am using the new beta version. If I can't process all filters at once then how will I be able to register each narrowband channel to each other?
@astrofalls Hi!
on the left I have integrated 36 panels only loading hydrogen into APP. On the right, I have loaded my Ha and Oiii frames and gotten a bad result. My oxygen mosaic also looks bad.
Did you try loading the OIII frames and integrate those into a mosaic without loading the Ha frames? Does that improve the OIII mosaic or do you still see that round glow just right of the center? If this solves the issue then we may want to have a look at your data to see what may be causing this. If the latter then you may want to check your OIII data to see what causes that round glow. To me it suggests an issue with your flats but I could be wrong.
If I can't process all filters at once then how will I be able to register each narrowband channel to each other?
You can process the Ha frames into an Ha mosaic. Then process the OIII frames into an OIII mosaic without loading any Ha frames. Then you can load both mosaics as Light and assign them to their corresponding filters. Don't load any calibration frames. Then go to tab 4 and register the mosaics. This will take APP through the first 4 steps and calibration (step 2) will leave the mosaics untouched since you didn't load any calibration frames. Once done, save the registered frames and use them for further processing.
It is recommendable to process all the way up to normalization instead of registration so the frames are normalized as well. That may save hassle during post-processing. In that case, save the normalized frames instead of the registered frames. Or save both (once normalization is finished you can go to tab 4 and save the registered frames as well) to see which works best for your data.
HTH, Wouter
Integrating the o3 mosaic on its own also improves the result. I pre integrate all panels with the WBPP script in Pixinsight since it is faster, then I stitch in APP, so every panel looks good I don't think its a flat fielding problem.
I will try registering the big mosaics together!
