[INSTRM-1767] OBJECT key value incorrect for certain visits Created: 25/Oct/22  Updated: 25/Oct/22

Status: Open
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: hassan Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-1737 Set OBJECT card a bit more carefully. Open
relates to INSTRM-1727 fixing pfilamps header keys for septe... Done
Story Points: 1

 Description   

A few of us have noticed inconsistencies between the value of the OBJECT keyword and the actual data taken for certain visits during the Sep 2022 Engineering Run. These are copied from comments in ticket INSTRM-1727:

Visits 79990..79997, which are scienceArc s, have been accidentally assigned OBJECT=NGC6633.

From Yabe-san:

... for visit=80842 (and probably other visits) OBJECT in the header looks M39 despite we observed NGC1980.

A scheme for interpreting the OBJECT card is the subject of another ticket, INSTRM-1737 but the above are simply errors that should be fixed, by correcting the headers using the obs_pfs mechanism.


Generated at Sat Feb 10 16:39:12 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.