<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:38:19 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-1685] Arrange for agccActor to call `gen2 updateTelStatus` for each exposure</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1685</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;We need to trigger updates of the telescope tables and MHS keywords for each agc exposure. That is done by commanding gen2Actor with `gen2 updateTelStatus caller=agcc` to record the latest gen2 status information.&lt;/p&gt;

&lt;p&gt;For an example, see mcsActor&apos;s McsCmd.py:getNextFileIds, but we need to handle subvisits differently.&lt;/p&gt;</description>
                <environment></environment>
        <key id="22919">INSTRM-1685</key>
            <summary>Arrange for agccActor to call `gen2 updateTelStatus` for each exposure</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="cloomis">cloomis</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Fri, 19 Aug 2022 13:59:37 +0000</created>
                <updated>Tue, 20 Sep 2022 13:53:20 +0000</updated>
                            <resolved>Tue, 20 Sep 2022 04:36:14 +0000</resolved>
                                                                    <component>ics_agccActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="31278" author="hiro" created="Fri, 2 Sep 2022 14:43:31 +0000"  >&lt;p&gt;Did you mean agActor - it makes that call already.&lt;/p&gt;</comment>
                            <comment id="31287" author="hassan" created="Wed, 7 Sep 2022 17:04:18 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis&quot; class=&quot;user-hover&quot; rel=&quot;cloomis&quot;&gt;cloomis&lt;/a&gt; so is this ticket still valid?&lt;/p&gt;</comment>
                            <comment id="31336" author="cloomis" created="Wed, 14 Sep 2022 16:32:35 +0000"  >&lt;p&gt;The &lt;tt&gt;agActor&lt;/tt&gt; does call &lt;tt&gt;updateTelStatus&lt;/tt&gt; correctly on behalf of the &lt;tt&gt;agccActor&lt;/tt&gt;. But when the &lt;tt&gt;agccActor&lt;/tt&gt; is called directly it needs to call gen2. Figure out a way for the &lt;tt&gt;agccActor&lt;/tt&gt; to distinguish this case, then call &lt;tt&gt;gen2 updateTelStatus&lt;/tt&gt; itself. &lt;/p&gt;</comment>
                            <comment id="31417" author="cloomis" created="Tue, 20 Sep 2022 04:36:14 +0000"  >&lt;p&gt;Actually, the agccActor already does this last bit: if an &lt;tt&gt;expose visit=&lt;/tt&gt; argument is not passed in from the agActor, the agccActor then gets its own visit, with &lt;tt&gt;gen2 getVisit caller=agcc&lt;/tt&gt;. &lt;tt&gt;getVisit&lt;/tt&gt; always calls &lt;tt&gt;updatetelStatus&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="31419" author="hassan" created="Tue, 20 Sep 2022 13:53:20 +0000"  >&lt;p&gt;This ticket has been closed with status &apos;DONE&apos; but no corresponding ticket branch. What was the actual change between the June 2022 run and now, that actually addresses the problem? &lt;/p&gt;

&lt;p&gt;I understand that if the &lt;tt&gt;iicActor&lt;/tt&gt; had been used during the June run, the telescope tables would have been updated fine. And I understand that during the June run, the &lt;tt&gt;agActor&lt;/tt&gt;, rather than the IIC, had been used. So presumably the &lt;tt&gt;agActor&lt;/tt&gt;, at the time of the June run, had not been updating the telescope tables. &lt;/p&gt;

&lt;p&gt;Yoshida-san mentions in an earlier comment in this ticket that the &lt;tt&gt;agActor&lt;/tt&gt; makes the gen2 &lt;tt&gt;updateTelStatus&lt;/tt&gt; call already. So had that feature been added to &lt;tt&gt;agActor&lt;/tt&gt; after the June run?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|02qpio:h</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="152">preEngRun07Sep</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>