<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:49:48 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-230] Remove at least one of the spline implementations in drp_stella</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-230</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;I discovered that there are two separate spline interpretations in drp_stella, and we should remove at least one of them. There are unnecessary copies of arrays in &lt;tt&gt;FiberTraces.cc&lt;/tt&gt; that should be removed when we clean up the interpolation.&lt;/p&gt;

&lt;p&gt;There is functional spline interpolation in {lsst::afw::math::Interpolate}} , but it only supports &lt;tt&gt;std::vector&amp;lt;double&amp;gt;&lt;/tt&gt;.  If it is appropriate to use doubles wherever we need to interpolate in &lt;tt&gt;drp_stella&lt;/tt&gt; we should definitely switch to use the &lt;tt&gt;afw&lt;/tt&gt; implementation.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11711">PIPE2D-230</key>
            <summary>Remove at least one of the spline implementations in drp_stella</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="-1">Unassigned</assignee>
                                    <reporter username="rhl">rhl</reporter>
                        <labels>
                    </labels>
                <created>Sun, 23 Jul 2017 17:32:35 +0000</created>
                <updated>Fri, 2 Nov 2018 21:20:08 +0000</updated>
                            <resolved>Fri, 2 Nov 2018 21:20:08 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                            <comment id="12418" author="rhl" created="Tue, 25 Jul 2017 19:09:55 +0000"  >&lt;p&gt;I also note that both of these splines seem to be &quot;natural&quot; splines (with vanishing second derivative at the first/last knots).  This is the simplest to code, but almost always a bad choice in practice.&lt;/p&gt;</comment>
                            <comment id="12465" author="swinbank" created="Fri, 28 Jul 2017 19:41:39 +0000"  >&lt;p&gt;Per our meeting of 2017-07-28, we agreed that RHL would replace existing the spline implementations with a &quot;not-a-knot&quot; implementation which he has lying around. We will then file an LSST-side ticket to get the afw spline implementation cleaned up, in the hope that we can ultimately switch to that.&lt;/p&gt;</comment>
                            <comment id="12472" author="rhl" created="Tue, 1 Aug 2017 14:59:03 +0000"  >&lt;p&gt;I have replaced the &quot;spline.cc&quot; implementation with a clean implementation which supports not-a-knot; this was done on &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-228&quot; title=&quot;Cleanup and restructure fiber assignment (&amp;quot;ITrace&amp;quot;) to use explicit focal plane model&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-228&quot;&gt;&lt;del&gt;PIPE2D-228&lt;/del&gt;&lt;/a&gt; as the functionality was needed there (probably a mistake).&lt;/p&gt;</comment>
                            <comment id="14332" author="hassan" created="Fri, 2 Nov 2018 17:39:01 +0000"  >&lt;p&gt;Done already according to RHL&apos;s recent comments on this ticket.&lt;/p&gt;</comment>
                            <comment id="14339" author="rhl" created="Fri, 2 Nov 2018 21:11:53 +0000"  >&lt;p&gt;I don&apos;t think this ticket is done (but didn&apos;t check). &#160;I cleaned things up, and added a not-a-knot, but I am not sure that the other versions are fine, and we certainly didn&apos;t switch to afw&lt;/p&gt;</comment>
                            <comment id="14340" author="price" created="Fri, 2 Nov 2018 21:17:11 +0000"  >&lt;p&gt;I believe there&apos;s only one spline implementation in drp_stella these days, which is RHL&apos;s.&lt;/p&gt;</comment>
                            <comment id="14341" author="price" created="Fri, 2 Nov 2018 21:20:08 +0000"  >&lt;p&gt;Agreed with RHL that this can be closed.&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|ii02jj:</customfieldvalue>

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