Error after analyzi...
 
Share:
Notifications
Clear all

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.

Error after analyzing stars

3 Posts
2 Users
1 Reactions
3,546 Views
(@singding)
Neutron Star
Joined: 9 years ago
Posts: 72
Topic starter  

Hi Mabula

 

I sometimes get this error, and the last couple times I simply restarted app and then it worked again  but this time it's not. I get the error every time after star analyzing

Screenshot 20180413 080243

 

Any idea howtoh do fix?



   
ReplyQuote
(@singding)
Neutron Star
Joined: 9 years ago
Posts: 72
Topic starter  

So basically a lot of frames we're clouded over so I assume that is what caused the error. I have more than 400 15second Lum frames, and didn't want to blink through each one, but I had to eventually wincei got an error each time. After I removed the clouded over frames, no more error 😉

 

Adam



   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5379
 
Posted by: singding

So basically a lot of frames we're clouded over so I assume that is what caused the error. I have more than 400 15second Lum frames, and didn't want to blink through each one, but I had to eventually wincei got an error each time. After I removed the clouded over frames, no more error 😉

 

Adam

Hi Adam @singding,

Yes, this bug is known to me, it is already fixed in the upcoming version 1.060. It's caused when there are no stars detected, for instance when you load a flat as light, or if the lights are totally clouded over. In the next version, APP will catch this exception properly en will simply let you know , that no stars were detected 😉

Thank you for reporting this 😉

Mabula



   
ReplyQuote
Share: