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-1696 Instrument control development <p>When any gen2 script makes an offset, that should be recorded in some MEMORY slots. These will be relayed into the PFS system and recorded at the start of each AG/SPS exposure. Among other things, this means that the MEMORY values should be <b>cleared</b> when the actual offsets are cleared by slewing, etc.</p> <p>The "dither offsets" are by far the most important.  Rotator and focus "guide offsets" are also desirable, but any other applied moves (az and alt) should be stored if possible.</p> <p>All keys should go into the <tt>MEMORY.PFS</tt> table space. Under that, I think we can just use a flat namespace, with <tt>DITHER_RA</tt> and <tt>DITHER_DEC</tt>, etc. for the dithers, and <tt>AG_IR</tt>, <tt>AG_FOCUS</tt>, etc. for guide offsets.</p> <p>If we ever expect to make user offsets for other reasons (i.e. not just dithering), I propose we use <tt>USEROFFSET_RA</tt>, etc. instead of <tt>DITHER_RA</tt>.</p> INSTRM-1696

Store offset values in gen2 MEMORY status dict

Task Normal Done Done Yoshida, Hiroshige cloomis EngRun Tue, 13 Sep 2022 17:27:04 +0000 Tue, 11 Oct 2022 19:15:38 +0000 Tue, 11 Oct 2022 19:15:38 +0000 PFS_kansoku 0 4 <p>Following the proposed design, for dithering offsets, at least the AG actor wants</p> <p><tt>DITHER_RA</tt> (arcsec) : offset to the RA coordinate, not angular separation on the tangent plane<br/> <tt>DITHER_DEC</tt> (arcsec)<br/> <tt>DITHER_INST_PA</tt> or <tt>DITHER_PA</tt> (arcsec)</p> <p>For field acquisition and auto-guiding, </p> <p><tt>AG_RA</tt> (arcsec) : cumulative guide offset to the RA coordinate, not angular separation on the tangent plane<br/> <tt>AG_DEC</tt> (arcsec)<br/> <tt>AG_INSROT</tt> or <tt>AG_INSTROT</tt> or <tt>AG_INR</tt> (arcsec) : correction to INSROT made by offsetting INST_PA</p> <p>The longest key among the proposed above is <tt>MEMORY.PFS.DITHER_INST_PA</tt></p> <p>So, can we fix the names?  How about DITHER_PA and AG_INR instead of the alternate spellings?</p> <p>I am OK with your suggestion.</p> <p>Agreed: </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>DITHER_{RA,DEC,PA} </pre> </div></div> <p>and </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>AG_{RA,DEC,INR} </pre> </div></div> <p>To clarify:</p> <p>DITHER_RA : user offset in RA "on the sky" (arcsec)</p> <p>AG_RA : cumulative value of applied RA offsets (errors) sent from the AG actor, which is a change in the RA coordinate value, without projection on to a tangent plane (arcsec)</p> <p>Please use the table in <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1702" title="Relay gen2 MEMORY.PFS status to MHS/opdb" class="issue-link" data-issue-key="INSTRM-1702"><del>INSTRM-1702</del></a> to find the official keyword names.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro" class="user-hover" rel="hiro">Yoshida, Hiroshige</a>, so I am summing -1 * offset for every ra, dec, rot offset....correct?  This is easy to change if later you decide otherwise.</p> <p>Please give us the sum of values that are sent from the PFS side and actually applied to the telescope command position, without any scaling <del>or sign flipping</del>. Cumulative guide offsets are not something regular observers or support scientists have to deal with.</p> <p>To clarify: we are applying the negation of the values you are sending for guide offsets. This seemed to be working in the last engineering. BUT, you want me to sum the non-negated values, is that right?  Just want to make sure...</p> <p> </p> <p>Sorry, negated values (errors -&gt; offsets) are what I initially proposed. So please sum up <b>negated</b> values that were actually applied to the telescope command position.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro" class="user-hover" rel="hiro">Yoshida, Hiroshige</a> is it OK to close this, as MEMORY statuses were stored correctly during the last run?</p> <p>It can be closed as the gen2 MEMORY statuses were passed to agActor as MHS statuses in the last run. (If a bug/missing item is fount, it will be addressed under a new ticket.)</p> Blocks INSTRM-1702 Relates INSTRM-1703 Development Rank 0|02qpio:fi Sprint preEngRun07Sep Story Points 1.0