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 tried doing my first 4x4 Mosaic, but somehow one of the four panels wont stack properly.
here are my settings:
i also tried checking the dynamic distortion correction, didnt change anything, except that the problem panel was the one opposite to M110.
and here a link to all my lights and callibration frames
https://1drv.ms/u/s!Ata7MsvIUtf3gcVgjQ2SHzHGKrt31A?e=gp1IxB
any ideas on what the problem could be??
I am doing my first mosaic in App also. I watched some video’s and just went ahead loading about 170 frames, made with an L-eNhance filter on a Rasa 8.
Great expectations... But, very disappointing: I got a nullPointerException in the module “Integrator”. Cause: null. pj.a (Unknown Source); pj.a (Unknown Source); pj.doInBackground(Unknown Source); java.swing.SwingWorker$1.call(SwingWorker.java:295)
A nullPointer in Swing... this implies it is not in the “background” processing, not in the “functional” processing, not in the “real APP stuff”, but only in the presentation on the screen. Therefore I think this is an example of a NullPointerException that could easily have been caught, but isn’t!
Mmm, well the registration mode should be "mosaic" and not "normal" for instance. Tab 5 normalize mode should be set to "advanced". Could you try that?
@vincent-mod I downloaded the latest APP release and did what you asked. I entered about 170 frames, divided over four panels of Pelican nebula and North America nebula. I gave APP 12 Gbytes of RAM memory. When APP was integrating I left the notebook (an HP Omen, 2 years old) alone. When I came back after 4 hours the notebook looked like hybernating. Perhaps that is the reason that the total integration took about 6 hours.
Anyhow, I am glad it works. I will try to find out why it took so long. Perhaps you have a tip for me.
The Mosaic-file is about 750 MBytes....
My conclusion is CrystalClear: APP does a great job here!
Excellent. In the future it's faster to first make the panels, then do the mosaic. Just FYI. 😉
