-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle WCS with galsim instead of Astropy #99
Comments
I think the point of implementing WCS feature in BTK was to be able to manage the celestial projection if needed ; using a simple pixel scale is not much work anyway and do not really require a WCS. I do not use the feature myself so I do not know how important it is though ; I suppose it would be important if one where to draw blends from real blends in the catalog for instance. I notice that you use TanWCS which corresponds to the TAN projection ; the astropy WCS supports a bunch of other projections https://docs.astropy.org/en/stable/wcs/supported_projections.html (which the user should be able to specify but I am not sure if this is the case right now) ; are those useful to anyone ? Otherwise using the galsim feature seems fair to me ; anyway we definitely need to take a look at the feature to check if it is working correctly with all the updates BTK had in the meantime. |
We discussed about using Galsim WCS instead of Astropy, here is a simple function I have (from this code) to create CelestialWCS with Galsim (no optical distortion here):
The reason why it is done this way and not using PixelScale or ShearWCS is to have a celestial projection which might preferable in some cases.. This should give you the equivalent of what you get with astropy.
The text was updated successfully, but these errors were encountered: