AIJ V5.0.0.0 Java exception reading solved FITS

[Tim Haymes]

I am attempting to solve images with Astrometry.net local server.  The FITS file is solved and then saved (with overwrite), but AIJ cannot read the file it created. (no problem with AstroArt or irfan view etc). What might be causing this?  The AIJ error is:
[ Unable to Open FITS file  IO error: java.io.IOException : Invalid FITS Header]

I have the following setup
AIJ 5.0.0.0, Java 64 bit,  Ansvr 0.22,  W10,  AIJ not in Windows folder.  AIJ run as administrator.

[keastrid]

Hi Tim,

Please try updating to the latest daily build (Help > Update AstroImageJ)

[Tim Haymes]

Thanks, I updated to 5.0.2.00 and this has fixed the difficulty. There is now another message:  
[Failed to open image with norm.tam.fits, attempting with Legacy mode ]

What does this message mean, and can it be ignored (it disappears after a short while) ?

Cheers

[keastrid]

Yes, that message can be ignored. AIJ has moved to using a different library for reading in FITS images, and it is more strict about what it excepts. So if the file has any violations for the format (you can test here), then it fails. "Legacy reader" is just imagej's custom reader.

AIJ shouldn't be outputting something invalid, so I will look into that. Would it be possible for you to provide a copy of the image?

[Tim Haymes]

Hi Karen,
Thank you for your help. I find the program goes through to the plot stage but there are some oddities.

1) The Fits file i send does show a Byte error after the last HDU
2) When i save the radec file, there are no magnitudes for the stars. They are all place holders 99.999
even though magnitudes were entered.
3) There are 8 lines in the radec but only 4 are displayed.  I expect 4.  Why the eight lines even though the radec was deleted and re-created?

I am using AIJ 5.0.2.01

The fitsverfy log reports for the solved file (from ansvr local server) the following:
Error: File has an extra byte(s) after the last HDU at byte 46116640.

I will send you the file Karen.

Kind regards

[karenacollins]

Hi Tim,

This error reporting problem should be fixed in the latest daily build (5.0.3.01 after update). We are still working on a better implementation of fits file writing that will be released soon, which will correct the extra byte after the last HDU.

Karen

[Tim Haymes]

Hi Karen,
Thank you for fixing the FITS reader warnings.  Work flow is improved considerably now with 5.0.3.01
Tim

[karenacollins]

Hi Tim,

For items 2 and 3 above, are you entering the magnitude values as the apertures are being placed in the images, or are you adding the magnitudes after multi-aperture has been run by using the reference star panel?

If you are entering magnitudes in the reference star panel, press <enter> after typing in each number. That will cause the measurements table to update and the magnitudes should then be output correctly in the radec file.

If you were entering the magnitudes as you placed apertures, but before you run multi-aperture, an update has been added to the current "Daily build" that should fix the problem.

If it is a different scenario, please let us know.

Karen

[Tim Haymes]

Hi Karen,
"are you entering the magnitude values as the apertures are being placed in the images ?"
Yes, i was adding magnitudes and saving the radec before multi-aperture analysis. I subsequently found they were saved follow the photometry, but i have not tried adding them to the reference star panel.

I now have the daily build, thanks

Tim