v2.0.0-beta1 - "Inv...
 
Share:
Notifications
Clear all

2022-05-29: APP 2.0.0-beta2 has been released !

Release notes

Download links per platform:

windows 2.0.0-beta2

macOS x86_64 2.0.0-beta2

macOS arm64 M1 2.0.0-beta2

Linux DEB 2.0.0-beta2

Linux RPM 2.0.0-beta2

v2.0.0-beta1 - "Invalid FITS value" error message


(@francismoreau)
Brown Dwarf Customer
Joined: 4 years ago
Posts: 13
Topic starter  

Hi,

I just installed v2.0.0-beta1 which I am testing with a dataset that works perfectly with version 1.083.4.
I have the following message:

image

I include the contents of the console

 


ReplyQuote
(@jochen-scharmann)
Main Sequence Star Customer
Joined: 3 years ago
Posts: 46
 

Seems to be a similar problem like I reported yesterday evening... Same error, unkown root cause. Strange thing is, the whole process went 100% fine  from Calinbration through Integration, except the auto-save. Sadly there is no visible Integration in the imae viewer which one could attemt to save manually


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4850
 

Thanks for reporting, we've not seen this before and I'll inform Mabula about it.


ReplyQuote
(@wvreeven)
Galaxy Admin
Joined: 4 years ago
Posts: 1723
 

@jochen-scharmann I see a question mark in the file name in the popup. This may indicate that there is a non-ascii character in the filename and given the location of the question mark I suspect a degrees symbol º. Can you rename the file(s) to not have that character and see if that works? If it does then we will know what to fix in APP. Thanks!


ReplyQuote
(@jochen-scharmann)
Main Sequence Star Customer
Joined: 3 years ago
Posts: 46
 

thanks Vincent,

what would be helpful for such type of error message is providing information to the user, what value exactly is wrong, so as a user I could take appropriate action. "Invalid" can mean anything, from special characters, naming, file size, numbers or other values

Jochen


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4850
 

True, however APP should be able to handle all filename characters, so in this case (if we can fix it) it should not happen again.


ReplyQuote
(@francismoreau)
Brown Dwarf Customer
Joined: 4 years ago
Posts: 13
Topic starter  

I confirm that the problem was the character °.
I renamed my files and everything works fine.


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4850
 

Good, that means it's the same issue. We're working on it, thanks for letting us know!


ReplyQuote
Share: