<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:49:39 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-216] make FiberTrace::extractFromProfile complain about NaNs or to deal with them</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-216</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;Currently &lt;tt&gt;FiberTrace::extractFromProfile&lt;/tt&gt; crashes with the message &lt;tt&gt;CFits::GCF: ERROR: a too large, ITMAX too small in GCF&lt;/tt&gt; if &lt;tt&gt;NaN&lt;/tt&gt; s are present in the image, as can happen after the &lt;tt&gt;ISR&lt;/tt&gt; task if the pixels are saturated (maybe Cosmics, too?). Please make the error message more telling, check for &lt;tt&gt;Nan&lt;/tt&gt; s before running the procedure, and make it complain about or fix the problem. Originally the procedure ignored pixels which were masked as 0 while 1 meant a good pixel. I&apos;m not sure how much of that is left.&lt;br/&gt;
&lt;tt&gt;CFits::&lt;/tt&gt; is definitely a remnant from old times and should be replaced with the actual &lt;tt&gt;namespace&lt;/tt&gt; . In general all the debug messages &lt;br/&gt;
{{ #ifdef _&lt;em&gt;DEBUG_EXTRACTFROMPROFILE&lt;/em&gt;__&lt;br/&gt;
  cout &amp;lt;&amp;lt; &quot;message &amp;lt;&amp;lt; endl;&lt;br/&gt;
#endif }}&lt;br/&gt;
should be replaced with &lt;tt&gt;LSST::log&lt;/tt&gt; messages, but this also part of ticket &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-165&quot; title=&quot;Replace {{cout &amp;lt;&amp;lt;}} and {{print}} with appropriate LSST log messages&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-165&quot;&gt;&lt;del&gt;PIPE2D-165&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11679">PIPE2D-216</key>
            <summary>make FiberTrace::extractFromProfile complain about NaNs or to deal with them</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="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="aritter">aritter</reporter>
                        <labels>
                    </labels>
                <created>Thu, 29 Jun 2017 06:28:22 +0000</created>
                <updated>Fri, 2 Nov 2018 17:38:01 +0000</updated>
                            <resolved>Fri, 2 Nov 2018 17:38:01 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="12370" author="rhl" created="Thu, 29 Jun 2017 13:31:06 +0000"  >&lt;p&gt;While making things robust is always good, we do not permit NaNs in images.  I assume that you&apos;re using the mask planes to decide which pixels to use (but that should not be needed to avoid NaN woes)&lt;/p&gt;</comment>
                            <comment id="14330" author="hassan" created="Fri, 2 Nov 2018 17:38:01 +0000"  >&lt;p&gt;Will revisit this issue if this appears again once we have the SIM2D + 2D DRP working.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11511">PIPE2D-165</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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|031vid:xi07fhk0ii</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>