Java error during normalization
using version 1.074.1 Normalisation of a 3 session job bugs out trying to cast a float to a double. have I done something wrong?
. Sorry. Forgot to post attachment
09:06:47 - 2) CALIBRATE: VERIFY CALIBRATION MASTERS: all frames are verified
09:06:47 - FRAME DETAILS UPDATER: starting...
09:06:47 - FRAME DETAILS UPDATER: no new frames to add
09:06:47 - FRAME DETAILS UPDATER: rebuilding all frame details...
09:06:47 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
09:06:47 - FRAME DETAILS UPDATER: adding frame marks...
09:06:47 - FRAME DETAILS UPDATER: updated succesfully
09:06:47 - 5) NORMALIZE: starting...
09:06:47 - 5) NORMALIZE: encountered an execution exception...
09:06:52 - FRAME DETAILS UPDATER: starting...
09:06:52 - FRAME DETAILS UPDATER: no new frames to add
09:06:52 - FRAME DETAILS UPDATER: rebuilding all frame details...
09:06:52 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
09:06:52 - FRAME DETAILS UPDATER: adding frame marks...
09:06:52 - FRAME DETAILS UPDATER: updated succesfully
Multi Session with 3 sessions of lights, Master darks, Master flats and Master dark flats; one shot colour. One session is binned. 2 bad pixel maps. Did calibrate, analyse stars and register. Execution exception occurs at beginning of the normalize step.
there are many reports of Java errors in this latest version of APP if you look through the forum. I assume Mabula is aware & working on a fix, I hope so. 😉
I would imagine that you have just found this error too & it is not something that you have done incorrectly.
If you could provide us with the exact error (maybe a screenshot), that would be handy. Also what kind of data and steps were involved. Thanks!
ps. Mabula is abroad at the moment, APP is getting so successful he's getting busier. I did notify him about these type of errors, if he has access to his laptop he will probably have a look.
Excellent! Let me tag Mabula (@mabula-admin) so he can have a closer look. Might take a while as he's abroad right now.
I just got this error when I'm combining two different fields of view where previously I've used the technique of running through calibrating all my images from one scope, but including a frame from another scope - the idea that the end result is registered according to the same orientation to allow combining.
No matter the combination of selecting, selecting ref frame, unselecting things - I get Java errors on Normalisation.
Previously I made notes on this process and worked great. I assume something changed with Normalisation between 1.073 and 1.074. I tried 1.074 and 1.074.1.
Ok, check (@Mabula-admin). This suddenly seems to be a very specific error that crops up with very specific data, Mabula already told me this should be possible to solve as it points to the data processing part of the program. I hope he gets to it fast.
DMacK, Thank you for reporting the issue, I will test today the issue with the unselected reference frame in normalization. Do you know by any chance if this only happens in multi-session mode ?
And I will do additional tests to make sure there are no more such bugs in the normalization engine.
If any of you have a workflow that always gives a bug, please describe it as precise as possible, I will then be able to sort this out very quickly 😉
Apologies for the long delay in my response 😉
Main developer of Astro Pixel Processor and owner of Aries Productions