<!-- 
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-570] Refactor findAndTraceApertures</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-570</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;&lt;tt&gt;findAndTraceApertures&lt;/tt&gt; is a C++ function with lots of branches, which makes it difficult to follow, maintain and debug. It should be replaced using a simpler algorithm, and a more modular implementation that is accessible from python.&lt;/p&gt;</description>
                <environment></environment>
        <key id="14357">PIPE2D-570</key>
            <summary>Refactor findAndTraceApertures</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</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="price">price</assignee>
                                    <reporter username="price">price</reporter>
                        <labels>
                    </labels>
                <created>Wed, 29 Apr 2020 15:54:34 +0000</created>
                <updated>Mon, 4 Jan 2021 20:23:16 +0000</updated>
                            <resolved>Fri, 29 May 2020 19:37:41 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="17135" author="price" created="Wed, 13 May 2020 03:36:46 +0000"  >&lt;p&gt;At the moment we&apos;re measuring the fiber profile from the data, but one could imagine generating it from the known &lt;tt&gt;NevenPsf&lt;/tt&gt; and &lt;tt&gt;DetectorMap&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="17137" author="rhl" created="Wed, 13 May 2020 13:32:20 +0000"  >&lt;p&gt;That would be great, avoiding the need for even/odd flats, but I&apos;m not convinced that it&apos;d work well enough.  The comparison would be very interesting, though.&lt;/p&gt;

&lt;p&gt;As Paul knows, we should integrate the &lt;b&gt;location&lt;/b&gt; of the traces with the detector map, even if we don&apos;t measure the profiles that way&lt;/p&gt;</comment>
                            <comment id="17138" author="price" created="Wed, 13 May 2020 13:56:36 +0000"  >&lt;p&gt;I would love to replace &lt;tt&gt;FiberTrace&lt;/tt&gt; (that essentially encodes position and profile) with a new &lt;tt&gt;FiberProfile&lt;/tt&gt; object (that encodes only the profile, and use the &lt;tt&gt;DetectorMap&lt;/tt&gt; for the position). However, &lt;tt&gt;PfsFiberTrace&lt;/tt&gt; is part of the datamodel, so I think I need a firm proposal first, and perhaps an improved &lt;tt&gt;DetectorMap&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="17141" author="cloomis" created="Wed, 13 May 2020 16:29:10 +0000"  >&lt;p&gt;+many.  Every time we have discussed this, we have wanted to separate the trace positions from the fiber shape.&lt;/p&gt;</comment>
                            <comment id="17143" author="rhl" created="Wed, 13 May 2020 17:23:13 +0000"  >&lt;p&gt;I&apos;ve never pushed back on eventually replacing Andreas&apos; code; it&apos;s a question of priorities.  We&apos;ll know more once we have lots of SCR data.&lt;br/&gt;
Re Paul&apos;s point:  I don&apos;t think we need worry about the data model (we can update it), although we do need to be careful not to break people&apos;s work flows/notebooks.  I can imagine ways to providing backwards compatibility in the butler.&lt;/p&gt;</comment>
                            <comment id="17204" author="price" created="Wed, 27 May 2020 19:08:24 +0000"  >&lt;p&gt;This is a large addition. It doesn&apos;t change the state of the pipeline, but adds potential to change it in the future. It will be used for &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-472&quot; title=&quot;Strategy for determining traces from non-odd/even high-density fiber data&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-472&quot;&gt;&lt;del&gt;PIPE2D-472&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="17228" author="price" created="Fri, 29 May 2020 19:37:41 +0000"  >&lt;p&gt;Merged to master.&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|02qps1:1o</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Reviewers</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>hassan</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="93">2DDRP-2021 A</customfieldvalue>

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