These are chat archives for astropy/astropy
ccacheisn’t installed by ananconda so if you put it in
/opt/local/binit should still be found even after anaconda prepends its path
Modelat the top, with
ParametricModelbelow, so I think that would lead do confusion. Also
astropy.parametric_modelis pretty awkward to type.
astropy.model, but re-work the docs to always use the phrase “parametric model” or “physical model” or “mean model”, and avoid wherever possible using the word “model” without qualifiers
coordinateis a similarly overloaded term)
clangon the conda path
/opt/local/libexec/ccachein the front on my default path, and that has
clangexecutables that conda is perfectly happy to work with
bindir with a symlink to the ccache version
alias pyb="CC="ccache gcc" python setup.py build"
Wcsprmfrom parsing more of the keywords from a fits header. Specifically, the keywords describing a physical coordinate system by keywords like CDELT1P or CRVAL2L.
astropy.wcsis the right place for this, since the keywords are describing a transformation between coordinate systems, but currently I don't see how to access these keywords from a
astropy.wcsis that most of the real work is done by the c library
libwcs, which is based on the published WCS standards. So if
libwcsis supposed to know about those keywords, it should already be accounted for.
WCSobject, too, although I can’t remember offhand what the exact syntax is). The above comment is more for if you want to actually use them as part of the WCS transform.
astropy.wcsis intended as a place for the code that is for the WCS standard
SIPdistortion scheme, which wasn’t in wcslib initially but eventually got moved in), but not more major changes that are very different from the standard.
wcsshould stay fairly limited in scope to stuff defined in the FITS-WCS standard (which I thought did include physical<->image coordinates in some sense, although I could be wrong about that)
astropy.wcsis pretty tightly integrated with the C
wcsliblibrary, which makes it somewhat harder to hack on)
CDELT1Ptaken care of as “alternate” WCSs? I.e., you can have a
CDELT1band so on? Or is the
Pa non-standard thing?
det2imis about the distortion stuff from the WCS paper IV. So while the terminology seems similar, I think it’s not related to the ds9 physical/image terms
pyregionmay have been doing it wrong, and the LTM/LTV keywords from IRAF are what define the coordinate system
.wcs.crvalhas the values for the physical coordinates