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 am using a trial licence, using the Yesterday night, I used my ZWO S50 and capture IC1795. I have 1 mosaic FIT from S50 and 1209 mosaic FITS.
I encountered this error while integration. I have integrated other mosaic FITS before but with fewer mosaics. Can anyone help?
Hi @madmax,
Welcome to the APP forum and thank you very much for your question.
Can you explain what you mean with mosaic FITS? Are this already created mosaics/panorama's? Or are these FITS directly from the Seestar S50?
Did you try different datasets as well? Or did you only try this big task with your new Trial license?
The error seems to indicate that one of the images can't be normalized and I suspect, this is because the image has a registration problem somehow. Can you run the same task, but run it only until 4) Register. So load your data like yesterday and then go to 4) Register and click on register. Once registration has finished, can you show me the output of the analytical details in the frame list? You the star counts, and registration precision specifically?
Thanks,
Mabula
Mosaic sub FITS are the individual image files that make up the entire mosaic picture.
Yes. There were registration issues with some FITs. This is my 1st time having registration issues. Based on what I understand from what you said, I should remove FITs with registration issues. I will try that and see what happens.
Thank you.
Hi @madmax,
Since this is your first time running Astro Pixel Processor, please check out the mosaic video tutorial here:
https://www.astropixelprocessor.com/mosaic-tutorial-milky-way-to-rho-ophiuchi-by-mabula/
To get the best and most robust results with a mosaic, a certain workflow is strongly advised. This has to do with how the actual mathematics work for a mosaic calculation where optical distortion also needs to be corrected in almost all mosaic cases.
The following notes are important, especially the first bullet point. Do not try to make the mosaic from all the individual subs directly. First make the separate mosaic panels. For example, if you have a 10x10 mosaic, where each mosaic panel has 20 individual exposures/subs. Then first stack the 10x10=100 mosaic panels first by loading each 20 exposures and stack them. Once you have stacked the 100 mosaic panels. You can then load those 100 panels as lights and perform the mosaic calculation. The result is much more robust and also definitely faster, since the mosaic calculation becomes simpler with more accurate data.
- The most efficient and most robust way to register any data set as a mosaic is to first integrate the individual mosaic panels. Then register the mosaic using only the individual integrated panels.
- This holds for other mosaics as well. Don’t try to create a mosaic out of 100s of indivdual frames. First create the mosaic panels.
- To prevent integration/stack artefacts at the borders of the mosaic panels, use both Multi-Band Blending (MBB) & Local Normalization Correction (LNC) to reduce the amount of integration artefacts considerably.
- The actual Mosaic integration needs to be done, using MBB & LNC as well to correct illumination differences and to prevent the well-known mosaic seams.
- Regarding: Dynamic Optical Distortion Correction.In most cases, you can leave this disabled for the individual mosaic panel integrations. Only enable it if registration RMS is higher than 0.5 pixels and registration is visibly not correct. In the mosaic registration, you really need to have this enabled always.
Please let me know if this helps. If it doesn't, I will be happy to look at your data to see what the problem is.
Mabula
