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
Hello guys/girls,
i'm working on my first mosaic. Well i'm about to finish the 1st of 4 panels, the other 3 I will make when weather clears up again. But how far do I process the mosaic?
My general plan is to capture and extract HA with a dual band filter (ASI294 mc pro with Optolong L-eNhance filer) and make a 4 panel mosaic in HA. Then i'm making an OSC RGB mosaic of the same target and separate R,G and B. Finally I will combine the 4 (r,g,b and HA) complete mosaics with the RGB combine tool.
My first question is, would it be better to stitch the RGB mosaic first and then, when it is complete, separate the R,G and B channel. Or is it better to split the R,G and B per panel and stitch them afterwards (so run the mosaic option in APP 3 times)?
Second, how far do I post process a panel before running the mosaic through APP? Do I, after integration of the first panel, take away any stack artefacts and/or light pollution? So I get the cleanest result when stitching all the other panels? Or do I leave it as the original integration and do the lightpollution removal at the complete end after stitching all the panels?
I couldn't find the answers to this on the forum and in the tutorials (since the tutorials are already awesome clean data).
Cheers,
Michel
On your first question, I would say to make the panels first by processing the RGB and NB fully (make them as nice and corrected as possible), add the NB to the R, G, B, do some processing again to make it nice and save the panel as RGB and do this for each panel. Then run the mosaic and post process again in a similar way. There are multiple ways to approach this though like you mentioned. But making the data as nice as possible at each step is, I think, a good idea. It will make the data cleaner for the next step.
