Can't save calibrat...
 
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.

[Solved] Can't save calibration files: "Invalid FITS keyword [SIGMAnull]"

3 Posts
1 Users
0 Reactions
1,696 Views
(@jerelsmith)
White Dwarf
Joined: 5 years ago
Posts: 6
Topic starter  

APP newbie: I load the Flat and DarkFlat images, then calibrate. The analysis seems to run, but is unable to save the results with the error message: "Invalid FITS keyword [SIGMAnull]" This stops APP and I have to quit. Per other fora that I've seen I'm not using non-ASCII characters in filenames or running my Virus software.

Output:

image

Tech Details:

MacBook 16-in 2021 (w/ M1 Max chip)
OS Sonoma 14.5
APP 2.0 Beta 29
(system rebooted, no other apps. running)
Canon SL2
For processing, files were converted using Pixillion from CR2 to Tiff

This topic was modified 2 years ago by Jerel Smith

   
ReplyQuote
(@jerelsmith)
White Dwarf
Joined: 5 years ago
Posts: 6
Topic starter  

This problem has not been solved. In a week, it has not even been answered. I don't know how the "solved" label got on it or how to get the "solved" label off of it. I am very frustrated by the lack of any response.



   
ReplyQuote
(@jerelsmith)
White Dwarf
Joined: 5 years ago
Posts: 6
Topic starter  

I found that inputting data as CR2 avoided the error. Apparently APP does not handle Tiff files.



   
ReplyQuote
Share: