Mihai Cara
Mihai Cara
For a detailed discussion, please see #3113, #3230, and #3304. In general, it seems to me that when people want a single pixel scale value, everyone has their own need...
> Many of the use cases that I skimmed through _rely_ on the pixels being square for the subsequent code to make sense. The "recommended" patterns: > > ```python >...
> `wcslint` calls an underlying function here: > > https://github.com/astropy/astropy/blob/8c0581fc68ca1f970d7f4e6c9ca9f2b9567d7b4c/astropy/wcs/wcs.py#L3430 > > Looks like all it does is tries to create a `WCS` object with the header and report warnings,...
Maybe things have changed: I used an old file lying around my file system while yours is likely a fresh baked one with some HAP stuff.
Try running `updatewcs.updatewcs(filename, use_db=False)` from `stwcs`.
> Not having a checksum is an error, harsh 😛 Why is this _an error_?
So should we have a warning for every thing that is recommended but not required? That is, if an observatory chooses not to write checksums, should users of those files...
> I think there is actually potentially a small astropy issue here. > > From the look of those warnings, what JWST have produced is fully standard compliant, but it...
> I would not be so bold to claim this ... ~if you have a better understanding of the standards~ `->` ... if you are courageous enough 😄
I think we need to understand whether these messages are useful, helpful, and/or informative. For example, if someone has a header with `DATE` and WCSLIB in `to_header()` _replaces_ `DATE` with...