You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having keyword DET.DIT, where identifies each detector, is not necessary. DET.DIT is sufficient because it always comes with DET.ID in the header that already determines which detector is used. Having suffixes like DET1.DIT or DET2.DIT can give issues when designing databases, etc.
Or there could be both DET.DIT and DET.DIT in the headers. DET.DIT would allow quick identification, while DET.DIT could be used for other general purposes.
Answer:
Yes you are correct. DET.DIT is sufficient for the pipeline and should be used; we'll update the document to reflect that. Same for DETi.NDIT.
It might be useful to also include the DETi.DIT for the parallel mode observations. Multiple detectors are used at the same time in these modes, and having all three DETi.DIT in the header would allow the full observing template to be reconstructed from a single raw file. However, this is optional/irrelevant as far as the pipeline is concerned; the pipeline should only use DET.DIT. We might keep the DETi versions for completeness with the above explanation.
The text was updated successfully, but these errors were encountered:
https://jira.eso.org/browse/MET-2158
Answer:
The text was updated successfully, but these errors were encountered: