<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:54:58 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>[PIPE2D-569] Certain PSF spots failed in the last analysis run </title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-569</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;As seen in &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-551&quot; title=&quot;Create PSF solutions - focused step&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-551&quot;&gt;&lt;del&gt;PIPE2D-551&lt;/del&gt;&lt;/a&gt;, certain high signal-to-noise Neon data produces abysmal solutions. Investigate and identify the problem.&#160;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="14355">PIPE2D-569</key>
            <summary>Certain PSF spots failed in the last analysis 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="ncaplar">ncaplar</assignee>
                                    <reporter username="ncaplar">ncaplar</reporter>
                        <labels>
                    </labels>
                <created>Tue, 28 Apr 2020 15:07:39 +0000</created>
                <updated>Mon, 4 May 2020 13:37:46 +0000</updated>
                            <resolved>Mon, 4 May 2020 13:37:46 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="17106" author="ncaplar" created="Tue, 28 Apr 2020 16:15:22 +0000"  >&lt;p&gt;The origin seems to happen, at least for some of these spots because:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;The analysis fails because only spots from one side of defocus are analyzed. In that case, we are essentially doing the extrapolation from defocused to focused measurement and that can fail spectacularly.&#160;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;I am showing an example of a bad example (Nez5_bad_spot.png) and a nearby good spot (Nez5_nearby_good_spot.png) that illustrates this.&#160;&lt;/p&gt;</comment>
                            <comment id="17109" author="ncaplar" created="Wed, 29 Apr 2020 13:33:04 +0000"  >&lt;p&gt;I have added in my analysis module (internal version 0.24a) a requirement that for the analysis to be successful, there need to be 2 large images from each side of defocus (where the large image is defined as the image taken when the movement of the slit is larger than 1.5 mm )&lt;/p&gt;</comment>
                            <comment id="17115" author="ncaplar" created="Mon, 4 May 2020 13:37:23 +0000"  >&lt;p&gt;Additionally, some spots have relatively bad solutions even though there are images available at both sides of the focus. All of these defocused images have areas that are saturated. It turns out that during the reduction of the data, when one uses the option&#160;&lt;tt&gt;isr.doSaturationInterpolation=False&lt;/tt&gt;&#160;the code does not ``grow&apos;&apos; the mask covering the saturated areas, i.e., it flags the pixels just next to saturated pixels as ok. A large number of such pixels with wrong values that are deemed to be acceptable for my analysis leads to wrong solutions. This has been discussed in #drp-2d channel and I am posting the most relevant part of the conversation as an image here.&lt;/p&gt;

&lt;p&gt;Short terms solution is to remove such images from my analysis. Medium-term solution would be to reanalyze and manually grow the mask. Long term solution is for the ISR pipeline to capture this problem.&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="14322">PIPE2D-551</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="12671" name="Example of bad spot.png" size="106547" author="ncaplar" created="Tue, 28 Apr 2020 15:09:19 +0000"/>
                            <attachment id="12672" name="Nez5_bad_spot.png" size="80953" author="ncaplar" created="Tue, 28 Apr 2020 16:10:03 +0000"/>
                            <attachment id="12673" name="Nez5_nearby_good_spot.png" size="83944" author="ncaplar" created="Tue, 28 Apr 2020 16:10:03 +0000"/>
                            <attachment id="12674" name="Screenshot 2020-05-04 09.35.40.png" size="281315" author="ncaplar" created="Mon, 4 May 2020 13:37:35 +0000"/>
                    </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|zzs1eo:</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>