Explain about EVENTS, GTI and POINTING #127
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 29, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that we have no information really about EVENTS and GTI and POINTING, and the POINTING is located under EVENTS, where really it doesn't have much to do with EVENTS, but rather is part of "observation" information, or what is sometimes called "tech3" in CTA.
I did not go the step to introduce an "IACT obs" top-level folder and move POINTING there now.
Instead, I left it in the "events" folder, but did add a few explanatory sentences about EVENTS, GTI and POINTING. I did also add a recommendation (not a requirement) that EVENTS should be chronologically ordered (will be discussed in #107). And, following other parts of the spec like the EVENTS, made the ALT / AZ optional columns, but required that earth location header keys are given, so that ALT / AZ can be computed from position, time and RA / DEC (same as for EVENTS). POINTING is clearly labeled as very preliminary and not yet in use for IACT DL3 data.