<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:40:04 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-1830] Prepare Gen2 abstract commands and operation tools for the Feb 2023 Run 10</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1830</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;This ticket replaces &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1815&quot; title=&quot;Prepare Gen2 abstract commands and operation tools for the Feb 2023 run&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1815&quot;&gt;&lt;del&gt;INSTRM-1815&lt;/del&gt;&lt;/a&gt;, which was applicable for the Dec 2022 run 09.&lt;/p&gt;

&lt;p&gt;Please develop and update the Gen2 commands for engineering observation run 10 in Feb 2023. Concrete actions include (&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=skoshida&quot; class=&quot;user-hover&quot; rel=&quot;skoshida&quot;&gt;Shintaro Koshida&lt;/a&gt;&#160;please edit as appropriate):&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Adjustment of the IIC command option to deal with the groupId and groupName properly with raster scan data, both in the Cobra raster mode and in the telescope raster mode.&lt;/li&gt;
	&lt;li&gt;Check all the AG related actor commands used in Gen2 skeletons so that they work with AG loop through MLP1, not through AG loop by Gen2 functions. AG loop by Gen2 functions should be left as an available option, and&lt;/li&gt;
	&lt;li&gt;Update Gen2 skeleton to have an option to read the groupId from PFS status on Gen2 when this function get implemented.&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="23185">INSTRM-1830</key>
            <summary>Prepare Gen2 abstract commands and operation tools for the Feb 2023 Run 10</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="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="skoshida">Shintaro Koshida</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Tue, 3 Jan 2023 20:52:15 +0000</created>
                <updated>Tue, 3 Jan 2023 23:35:49 +0000</updated>
                            <resolved>Tue, 3 Jan 2023 23:34:04 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="32054" author="hassan" created="Tue, 3 Jan 2023 23:34:04 +0000"  >&lt;p&gt;As Yuki pointed out, best to drop this ticket re-open &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1815&quot; title=&quot;Prepare Gen2 abstract commands and operation tools for the Feb 2023 run&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1815&quot;&gt;&lt;del&gt;INSTRM-1815&lt;/del&gt;&lt;/a&gt;.&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|02qpjd:00r3000k0010k</customfieldvalue>

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