https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-1767 Instrument control development <p>A few of us have noticed inconsistencies between the value of the <tt>OBJECT</tt> keyword and the actual data taken for certain visits during the Sep 2022 Engineering Run. These are copied from comments in ticket <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1727" title="fixing pfilamps header keys for september22 engRun" class="issue-link" data-issue-key="INSTRM-1727"><del>INSTRM-1727</del></a>:</p> <p>Visits <tt>79990..79997</tt>, which are <tt>scienceArc</tt> s, have been accidentally assigned <tt>OBJECT=NGC6633</tt>. </p> <p>From Yabe-san:</p> <blockquote> <p>... for visit=80842 (and probably other visits) OBJECT in the header looks M39 despite we observed NGC1980. </p></blockquote> <p>A scheme for interpreting the OBJECT card is the subject of another ticket, <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1737" title="Set OBJECT card a bit more carefully." class="issue-link" data-issue-key="INSTRM-1737">INSTRM-1737</a> but the above are simply errors that should be fixed, by correcting the headers using the <tt>obs_pfs</tt> mechanism. </p> INSTRM-1767

OBJECT key value incorrect for certain visits

Task Normal Open Unresolved Unassigned hassan Mon, 24 Oct 2022 16:34:23 +0000 Mon, 24 Oct 2022 16:34:23 +0000 0 1 Relates INSTRM-1737 INSTRM-1727 Development Rank 0|zzsvaf: Story Points 1.0