2023-09-16: APP 2.0.0-beta23 has been released !
Improved performance again, CMD-A now works in macOS File Chooser, big improvement for bad column cosmetic correction, solved several bugs
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
I am not sure how this happened, but running a mosaic using the settings I normally do has given me a very strange result. I have ran 4 different mosaics in the past couple weeks using the settings I did on this one, and those all turned out fine. I am using APP 2.0.0-beta4. Any idea what happened?
Here was the integration and registration settings
Here was the result
If I need to I can upload the files used for this. I did each panel as an individual normal integration, then used the master lights as lights for the mosaic so I only had 4 each of SHO to do the integration, so a total of 12 lights.
@imnewhere Hi,
You need to increase the "scale start" to at least 5 and "scale stop" to at least 12 and probably 15 in tab 4. Also, in tab 3 you probably need to up the number of stars to 2500 or more. In tab 5 you need to enable advanced more. Try that please and let us know the result.
Wouter
It took me redoing each panel again one at a a time for it to finally work with those settings. Got some interesting errors in the meantime.
@imnewhere Sorry to read about the errors. Without more info about what data you were processing and in which stage APP was when those errors popped up, it will be impossible to explain what caused the error popups. I think the popup about the image dimensions speaks for itself, though.
@wvreeven the first image shows the dimensions of the images, the second happened right at registration, and the last 2 at the start of integration and in that order, though how it got confused with the dimensions I don't know since you can see they are definitely within a normal range and I wasn't using drizzle. I've done a drizzle integration on larger images than this before, and in fact most of my recent integrations were with a 2x drizzle on each panel because of major undersampling.
Here is the image I was working on: https://www.astrobin.com/m7zveu/
Each panel was in the 16mp range since the camera was an FLI ML16200, and I worked each panel to where I had a master Ha, Sii, and Oiii, so a total of 12 lights for 4 panels, each panel in one session. It ended up working, but it was strange that it didn't like the initial masters for each panel.
For instance, I did these using the same settings I posted in the first one. I didn't know about the advanced part on normilization.
https://www.astrobin.com/j50bmq/ https://www.astrobin.com/4ecd4t/ https://www.astrobin.com/k7trgh/ https://www.astrobin.com/qsjcwx/
@imnewhere When imaging it is normal to have a slight drift that causes the final integration to have different dimensions than the raw lights. More so if you shoot mono images of the same target with different filters on different nights. The mount will never exactly return to the same position so the object will be displaced each night, causing the final registered integration results to have different dimensions again.
As for the popup, it doesn't indicate that APP got confused with the dimensions. It shows that APP has detected that your image is so large that it cannot be processed and needs to be scaled down.
Could you also try by switching off dynamic distortion correction?
@vincent-mod
I ended up closing out APP, then reopening it again and everything went well. Done a few more images since then and those turned out good too.
Ah, well that is weird for sure. If it happens again, please let us know.
