<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:35:52 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-1473] Investigate performance of sep for centroiding.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1473</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The performance of sep (the wrapper for sextractor) produced some unexpect results during the engineering run, with very poor performance in some frames. This needs to be investigated further, and better input parameters determined.&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="22537">INSTRM-1473</key>
            <summary>Investigate performance of sep for centroiding.</summary>
                <type id="5" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10516&amp;avatarType=issuetype">Sub-task</type>
                            <parent id="22535">INSTRM-1471</parent>
                                    <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="karr">karr</assignee>
                                    <reporter username="karr">karr</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Wed, 8 Dec 2021 02:31:22 +0000</created>
                <updated>Fri, 10 Jun 2022 20:22:30 +0000</updated>
                            <resolved>Fri, 28 Jan 2022 05:28:39 +0000</resolved>
                                                                    <component>ics_actorkeys</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="28818" author="karr" created="Fri, 17 Dec 2021 04:44:34 +0000"  >&lt;p&gt;This works best when the data are cropped to the useable region and the two sides processed separately, to avoid artifacts in the background subtraction and in the boundary between the two halves of the image.&#160;&lt;/p&gt;

&lt;p&gt;I want to use the background noise image calculated during the background subtraction for variable thresholding across the image; this isn&apos;t performing as I expected from the sep documentation and needs to be investigated further.&lt;/p&gt;</comment>
                            <comment id="30295" author="karr" created="Fri, 7 Jan 2022 01:29:00 +0000"  >&lt;p&gt;I checked sep for better input parameters, and modified the code to process the two sides of the image separately. This is linked to 1479, and reading the useable regions from the yaml file.&#160;&lt;/p&gt;</comment>
                            <comment id="30316" author="karr" created="Thu, 13 Jan 2022 07:09:05 +0000"  >&lt;p&gt;Current values for sep: threshold of 15, minarea=10 (the default is too small), and the defaults for filtering, etc. The over scan correction, background subtraction and centroiding are done separately for the two sides of the image.&#160; Bad columns have a very&#160; simple interpolation at the moment.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="30317" author="karr" created="Thu, 13 Jan 2022 07:09:22 +0000"  >&lt;p&gt;Pushed to 1479&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|02qpik:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="129">PreEngRun05 B</customfieldvalue>
    <customfieldvalue id="133">PreEngRun05 C</customfieldvalue>
    <customfieldvalue id="135">PreEngRun05 D</customfieldvalue>
    <customfieldvalue id="136">PreEngRun05 E</customfieldvalue>
    <customfieldvalue id="139">PreEngRun05 F</customfieldvalue>
    <customfieldvalue id="152">preEngRun07Sep</customfieldvalue>

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