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

tracking_type #57

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

tracking_type #57

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

Comments

@alle-ira
Copy link
Member

Sect. 4.5 -
The parameter tracking_type as defined in ObsLocTAP pertains more to observation planning and execution that to data discovery. Additionally, its scope is wider than the radio extension since it pertains data irrespectively of their energy/frequency domain. Moreover, as it is defined now tracking_type does not comprise all the values needed to describe the variety of tracking modes associated to the sky scan modes (for instance: skydip, on the fly/raster maps).

@BaptisteCecconi
Copy link
Contributor

Anyhow, this kind of list of terms should go into a vocabulary in Semantics... especially since it is used in 2 recommendations (ObsLocTAP and this one).

@Bonnarel
Copy link
Collaborator

Bonnarel commented Apr 3, 2024

I agree with Baptiste here. the parameter name should be the same whatever the situation : observation planning or description of achieved observations. this is good for interoperability. And if terms are missing they should be added in the external generic vocabulary

@alle-ira
Copy link
Member Author

alle-ira commented Apr 4, 2024

Apologies, what we intended is that we are not sure this parameter should be listed in the ObsCore radio extension given its (more) general scope. Is there a use case motivating its inclusion in the radio extension?

@loumir
Copy link
Collaborator

loumir commented Apr 4, 2024

Agreed with Alexandra .
Will users query an archive using this term?
Is this term tracking_type really designating the same concept between ObsLocTap and the tracking into a radio instrument ?
Expanding, and standardizing vocabularies takes time to build consensus , so is it really a key parameter ?

@mservillat
Copy link

mservillat commented May 22, 2024

Note that tracking_type is indeed used in different contexts, including in our current High Energy discussions. Cherenkov telescope arrays could use this concept, as well as other ways to scan the sky (we discuss a convergent or divergent mode for example) or run observations sequences (where wobbling between 2 or 4 positions around a source in one special technique). So the High Energy domain could benefit from those descriptions for discovery purposes as well, or for observations characterisation (which to me is also a use case for ObsCore)

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

5 participants