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.
[Solved] Error message: java.lang.Float cannot be cast to java.lang.Double
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.
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.
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?
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.
