[Solved] Error message: java.lang.Float cannot be cast to java.lang.Double

Hi @chris-pa , Could you describe when exactly you get this error and if it's repeatable?

Hi Vincent,

I only started using the program today so forgive me if I get this wrong, but it happens as soon as I hit normalize under step 5. It is repeatable - it's happened three times and I can't seem to get past it.

Thanks,

Chris

Sorry for that inconvenience, it seems to happen with specific data now and again. It's known and will be fixed in the next release. Mabula has gotten your message as well and will come back to it asap.

What an introduction! Oh well - I'm glad at least it's not something I was doing wrong.

If this is fixed, try a mosaic in the next try, you'll be amazed. 😉

Posted by: @chris-pa

I just downloaded APP today and keep getting this error message. Does anyone have an idea of what I might be doing wrong?

Hi Christopher @chris-pa & Vincent @vincent-mod,

First of all, Christopher, thank you for sharing this issue and welcome to the APP forum 😉

Can you please provide more information on what kind of data you are loading into APP ?

Which camera?

Which file format? FITS, or ?

Which bitdepth (8,16,32 ?  )

Are you using calibration frames, if so which types?

And also, is the issue happening with and without calibration frames loaded?

The issue very likely has to do with your particular data, perhaps you can share a small subset of your data so Vincent and I can investigate why you get this error message and solve it at the same time?

Kind regards,

Mabula

Happened to me twice today and I had to close the program, then reopen and use the master calibration frames to fix it.

Hi Christopher @chris-pa & @vincent-mod,

I have all your data now 😉 thanks for uploading it directly to our infrastructure.

I will run the data now myself in APP and will let you know my findings later today or tomorrow..

Mabula

Posted by: @imnewhere

Happened to me twice today and I had to close the program, then reopen and use the master calibration frames to fix it.

@imnewhere,

Can you be more clear about what happened? Do you mean that after a restart and a re-process, all went fine ?

Mabula

I figured out that this happens if you are using a reference file and click Normalization without the reference file being checked.

My story is that I used DSS for this project and got 5 stacks that came out great, but for some reason, DSS couldn't handle the red. I even did an extra session, but it got all smeared at the bottom and any iteration of data (half from session 1, half from session 2, only session 3, etc.) just failed in the same way. Anyway, I had aligned everything with an OIII sub and didn't see any reason to restack the other five stacks (over 700 lights!) so I tried loading just the reds into APP and used the OIII as a reference. It appears you can uncheck it prior to integration and everything will work as intended, but it will crash if you normalize with the reference unchecked.

Hi @chris-pa, @vincent-mod & @imnewhere,

I have found the issue and it is now fixed ;-). The next release will contain this bug fix.

Kind regards,

Mabula