<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:42:35 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-2059] Allowing short exposure time in the first three FPS iterations</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-2059</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;To optimize the FPS sequence, it is requested to use shorter exposure time in the first three iteration.  FPS actor needs to address the requirements.&lt;/p&gt;</description>
                <environment></environment>
        <key id="23798">INSTRM-2059</key>
            <summary>Allowing short exposure time in the first three FPS iterations</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="chyan">chyan</assignee>
                                    <reporter username="chyan">chyan</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Thu, 17 Aug 2023 03:36:45 +0000</created>
                <updated>Wed, 30 Aug 2023 09:14:55 +0000</updated>
                            <resolved>Wed, 30 Aug 2023 09:14:55 +0000</resolved>
                                                                    <component>ics_fpsActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="34378" author="yuki.moritani" created="Thu, 24 Aug 2023 06:48:27 +0000"  >&lt;p&gt;(Recording)&lt;br/&gt;
At ICS/PFI+MCS telecon on 18 Aug 2023, it was pointed out that Cobras should not stop (i.e., not be flagged as converged) until MCS image is taken with longer exposure.&lt;/p&gt;</comment>
                            <comment id="34380" author="chyan" created="Thu, 24 Aug 2023 17:31:49 +0000"  >&lt;p&gt;After thinking carefully, I decide not to implement Cobra-not-stop strategy because of few evidences.    &lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;We have used short exposure time in many convergence runs and diagnostic plots show that the converged cobras reported from FPS and MCS at first three iterations are very consistent.  That means our strategy is correct in first place.&lt;/li&gt;
	&lt;li&gt;This evidence is also observed in longer exposure time convergence run.&lt;/li&gt;
	&lt;li&gt;In another aspect, implementing the  cobra-not-stop strategy will changed the strategy that has been working for many engineering runs.&lt;/li&gt;
	&lt;li&gt;Therefore, implementing the  cobra-not-stop at first three iteration strategy introduces another uncertainty and it should be another ticket.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Giving that, let&apos;s make it simple.  We solve this ticket first.  Then creating another ticket to address Jeniffer&apos;s suggesting. &lt;/p&gt;</comment>
                            <comment id="34581" author="chyan" created="Wed, 30 Aug 2023 09:14:55 +0000"  >&lt;p&gt;This ticket is tested on the Unit Selector, close the 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|02qpjd:00r20060i200186403g</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>