Repository navigation
Issue with unit 'HZ' in FITS files (astropy.wcs) - #36
Conversation
|
Units in FITS are case-sensitive by definition. Look at "s" (seconds) vs. The relevant FITS standard can be downloaded here: I don't think it's a great idea to relax the standard within astropy.wcs -- wcs.wcs.unitfix() This was not very well documented in the latest release of pywcs, but (I hope to get a new release of pywcs out soon, so this improved Mike Michael Droettboom |
|
An alternative (though a diversion from wcslib behavior), may to add a kwarg to the WCS() constructor "fix=True", then when True would call all of the fixers. The user could set this to False if they know they don't want any fixing. I would also like to emit a warning when any fixers are performed so that deviations-from-the-standard are known and reported back to the producing software. |
… called on the wcsprm object upon construction. Warnings are emitted if any non-standard content was found and changes were made.
|
Thanks! Using |
… error message. This needs to be maintained until it is accepted upstream.
|
Looks fine for merging to me as well - @mdboom, I see you recently made a change, though... I'll leave it to you to merge if you're done with changes. |
Issue with unit 'HZ' in FITS files (astropy.wcs)
Issue with unit 'HZ' in FITS files (astropy.wcs)
…ite branch to master
Fixes Issue astropy#36 fixes broken link and missing image from old_site branch to master
It seems that astropy.wcs (and more specifically wcslib) has issues with the unit 'HZ'. For example, the following header:
parsed with:
gives the error:
Does the WCS standard really forbid the uppercase HZ? If so, could you point me to where this is defined, so I can report a bug with the software that produced this file? And do we want to relax astropy.wcs so that it catches that since I've found a number of 'real' datasets that use `HZ``?