Skip to content
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

make PolarizationState more flexible #18

Open
pdowler opened this issue Jul 26, 2024 · 3 comments
Open

make PolarizationState more flexible #18

pdowler opened this issue Jul 26, 2024 · 3 comments
Labels
2.5 enhancement New feature or request

Comments

@pdowler
Copy link
Member

pdowler commented Jul 26, 2024

ObsCore and FITS WCS allow a limited set of states

actual data files often use combinations that better describe the polarization axis (even if degenerate aka 1 pixel)

CAOM-2.4 allows an extended set of values from https://listmgr.nrao.edu/pipermail/fitswcs/2008-March/thread.html

Recent metadata requests include additional things like Q + iU...

@pdowler
Copy link
Member Author

pdowler commented Jul 26, 2024

The only viable solution appears to be to define a vocabulary that can evolve over time and define Plane.polarization.states as a set of those vocabulary terms.

@pdowler pdowler added enhancement New feature or request 2.5 labels Jul 26, 2024
@pahjbo
Copy link

pahjbo commented Sep 4, 2024

It is an irony that the FITS polarisation codes were rather dominated by what was done in radio interferometers - and yet there are still missing states - but I think the real conclusion of that thread is that it is rather difficult to come up with a vocabulary that covers the possible cases - I think that this https://listmgr.nrao.edu/pipermail/fitswcs/2008-March/000425.html contains that insight - however it is not an easy problem to solve as no-one has done it yet - it should be solved upstream of CAOM though....

@pdowler
Copy link
Member Author

pdowler commented Sep 4, 2024

I agree that it should be solved upstream. From the CAOM point of view, I want to refer to an external resource and for technical reasons that is best served by a vocabulary. The IVOA vocab could be the place where the community discussion actually comes together, or it could be more like the UAT where IVOA simply endorses/integrates something from elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.5 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants