<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:39:45 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-1815] Prepare Gen2 abstract commands and operation tools for the Feb 2023 run</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1815</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Development and update of the Gen2 commands for engineering observation in &lt;del&gt;Dec. 2022&lt;/del&gt; Feb 2023. Concrete action items are&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="23155">INSTRM-1815</key>
            <summary>Prepare Gen2 abstract commands and operation tools for the Feb 2023 run</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="skoshida">Shintaro Koshida</assignee>
                                    <reporter username="skoshida">Shintaro Koshida</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Tue, 6 Dec 2022 02:58:06 +0000</created>
                <updated>Wed, 1 Mar 2023 09:27:59 +0000</updated>
                            <resolved>Wed, 1 Mar 2023 09:23:59 +0000</resolved>
                                                                    <component>EngRun</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="32314" author="skoshida" created="Tue, 28 Feb 2023 23:03:50 +0000"  >&lt;p&gt;This branch has been merged to master on Feb. 28 (Hawaii time). The status at the time of merge is as following.&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;The Gen2 status item for the groupName &quot;PFS.GROUPID.NAME&quot; appeared on the status list called by a command &quot;get_status PFS&quot; . On skeleton side, the item seemed not to be implemented to control the groupName. The GroupID itself is treated properly in those skeleton files when one is given via command line manually.&lt;/li&gt;
	&lt;li&gt;AG related skeleton files were checked and updated for the AG sequence via MLP1.
	&lt;ul&gt;
		&lt;li&gt;When &quot;DRY_RUN&quot; option is &quot;no&quot;, AG Actor commands used in the skeleton files are executed without &quot;dry_run&quot; option.&lt;/li&gt;
		&lt;li&gt;When &quot;DRY_RUN&quot; option is &quot;no&quot;, the command &quot;exec TSC AG_TRACKING CALC_REGION=PFS MOTOR=ON ;&quot; is executed to set the telescope to &quot;Autoguide Ready&quot; status. The order is &quot;AG Actor command on&quot; -&amp;gt; &quot;TSC Command on&quot; -&amp;gt; &quot;TSC Command off&quot; -&amp;gt; &quot;AG Actor command off&quot;.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;As an additional work, AGRECONF.sk is updated to accommodate the switching function of &quot;DRY_RUN&quot; during AG loops. PFS launcher was also updated to provide the control GUI of this function.&lt;/li&gt;
	&lt;li&gt;As another additional work, AGEXP.sk and PFS_STARTAG.sk are updated to accommodate the AG actor command option of &quot;fit_dscale&quot; by which the fitting parameter for the image scaling in the AG loop is controlled.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;For the further update of the Gen2 commands for the next PFS engineering observation in April. 2023 will be managed in the another branch.&lt;/p&gt;</comment>
                            <comment id="32320" author="yuki.moritani" created="Wed, 1 Mar 2023 09:23:59 +0000"  >&lt;p&gt;The ticket branch was merged, so I close this ticket.&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|02qpgs:</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>