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 encountered a
Encountered error in module:
LightFrameCalibration
Error message:
java.lang.ArrayIndexOutOfBoundsException: 1
Cause:
1
dK.a(Unknown Source)
dK.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
Any idea what I can do, might point towards the error topic (memory, java, bug ...)
I happens during the "ANALYSE STARS" process. Version APP 1.082
Thanks
Marco
Can you give some details on the system you use? And does this happen as well if you try it on just a few subs for instance?
What I figured out so far is that it is related to the dark frames. If I don't add those in the mix, I don't have the problem.
What kind of detail of were you thinking about? The subs are Ha/O3 created with an ASI160MM.
Ah ok, so that's good progress. APP does have exceptions if there is an issue with the calibration data. Could you try to take a few new ones, carefully watching what settings you use and try again?
@vincent-mod
(funny)
Already on it - Replacing dark and bias library (flats not in play). Just to be on the safe side, came up with the same idea.
M
Well, the bias at least worked so keep the old master as well just in case. 🙂
Still stuck at not getting the darks to work, despite new set created just after the Ha and O3 subs. I am new to smallband so maybe there is "more to do" then during OSC camera workflows...?
Mm, not really for the darks as they are independent of filters. Maybe I should take a look at some lights and darks?
Go to https://upload.astropixelprocessor.com and use upload2 as username and upload2 as password.
Create a directory named “mgralike-darksissue” and upload in there. Thank you
Thanks for the offer.
But while attempting to create a decent test set for you, it seems that it is still the darks that aren't correct.
From left to right, Ha sub using 20 darks of 10 minutes each, Ha sub using 10 darks of 10 minutes each and the last on the right, which is almost decent, 3 darks of 10 minutes each...
It seems that I am introducing light spill somewhere in my created darks... I am going to try to fix that first.
In the meantime without using any darks for Ha and OIII - https://www.astrobin.com/iamutq/
Ok, that might be the issue, any light pollution in a dark will throw off the calibration indeed. I hope you can get that sorted!
