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

scan_mode #56

Open
alle-ira opened this issue Mar 20, 2024 · 2 comments
Open

scan_mode #56

alle-ira opened this issue Mar 20, 2024 · 2 comments

Comments

@alle-ira
Copy link
Member

Sect 4.5 -
From the IVOA perspective of keeping separate time, space and energy domains, should we adopt two parameters: one for scanning in spatial coordinates (for instance sky_scan_mode) and the other for frequency scanning (for instance freq_scan_mode)?

@Bonnarel
Copy link
Collaborator

Bonnarel commented Apr 3, 2024

Can we imagine some vocabulary rule which allows combination of two terms ? So that we may use the same FIELD for either axis scan exclusively or combination of both ? This to avoid too much empty FIELDS in case.

@alle-ira
Copy link
Member Author

alle-ira commented Apr 4, 2024

We agree on the proposal of keeping one parameter, accompanied by a vocabulary and its rules. We could imagine scan_mode as composed by two terms, the first one (always present) defining the sky scanning mode and the second (optional) describing the frequency scanning mode if present. As an example, a frequency switching observation could have scan_mode='on, freq_switch' while an on-the-fly map could have scan_mode='otf_map' only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants