<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:50:59 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-319] Make line identification robust against wavelength shifts</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-319</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;Line identification needs to be robust against inaccuracies in the &lt;tt&gt;DetectorMap&lt;/tt&gt; wavelength solution. While it&apos;s true the &lt;tt&gt;DetectorMap&lt;/tt&gt; wavelength solution should be solid during observing, during development and commissioning and while dealing with both simulated data and LAM data, it&apos;s not unknown for the true wavelength solution to change relative to what&apos;s in the &lt;tt&gt;DetectorMap&lt;/tt&gt;. Here&apos;s a possible algorithm:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;find and centroid all peaks in spectrum&lt;/li&gt;
	&lt;li&gt;apply rough wavelength calibration to measured peaks&lt;/li&gt;
	&lt;li&gt;for both observed and model line lists:
	&lt;ul&gt;
		&lt;li&gt;find pairs of lines with separations between 5A and 500A (separation is not too small to allow confusion, not too large to be very non-linear)&lt;/li&gt;
		&lt;li&gt;for each pair, calculate mean and difference&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;match observed pairs to model pairs when the mean is within 50A and the difference is within ~ 0.5A&lt;/li&gt;
	&lt;li&gt;Instead of pairs, could use triplets, and match the ratio of spacings.&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="13251">PIPE2D-319</key>
            <summary>Make line identification robust against wavelength shifts</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>Tue, 29 Jan 2019 21:36:40 +0000</created>
                <updated>Thu, 28 Mar 2019 20:47:39 +0000</updated>
                            <resolved>Thu, 28 Mar 2019 20:47:22 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="15037" author="price" created="Thu, 28 Feb 2019 19:52:38 +0000"  >&lt;p&gt;I now believe that the use of this algorithm is not necessary given a decent detectorMap: when that is the case, the vanilla algorithm outperforms my implementation for HgAr (possibly due to the huge number of faint, blended lines). Nevertheless, this branch contains a lot of peripheral improvements, and the algorithm may be useful in other contexts.&lt;/p&gt;</comment>
                            <comment id="15210" author="hassan" created="Thu, 28 Mar 2019 20:47:22 +0000"  >&lt;p&gt;As &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price&quot; class=&quot;user-hover&quot; rel=&quot;price&quot;&gt;price&lt;/a&gt; has mentioned, algorithm is not required in 2D DRP for its original purpose, but much of this development is expected to be useful for other functions required in 2D DRP, for example the line intensity modeling of &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-345&quot; title=&quot;Provide a method for determining line intensities&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-345&quot;&gt;&lt;del&gt;PIPE2D-345&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13325">PIPE2D-345</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13319">PIPE2D-340</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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|02qpuc:7i73m</customfieldvalue>

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