<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:35:43 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>[PIPE1D-25] Output pfsZcandidate*.fits files for the stellar solver</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE1D-25</link>
                <project id="10700" key="PIPE1D">DRP 1D pipeline</project>
                    <description>&lt;p&gt;I&#8217;m running the drp_1dpipe for a stellar input spectrum and using a set of templates from X-shooter library (R~10000). A resulting velocity looks very good with 15km/s for an input spectrum of 18km/s.&lt;br/&gt;
The resulting pfsZcandidate*.fits file, however, contains only 2 HDUs instead of 5 and therefore does not contain uncertainty and posterior probabilities for the redshift. The contents of the output files look like:&lt;/p&gt;

&lt;p&gt;No.&#160;&#160;Name&#160;&#160;&#160;Ver&#160;&#160;Type&#160;&#160;&#160;Cards &#160;Dimensions &#160;Format&lt;br/&gt;
&#160;0&#160;PRIMARY &#160;&#160;&#160;1 PrimaryHDU&#160;&#160;&#160;10 &#160;() &#160;&#160;&#160;&lt;br/&gt;
&#160;1&#160;ZCANDIDATES&#160;&#160;1 BinTableHDU &#160;&#160;21 &#160;1R x 6C &#160;&lt;span class=&quot;error&quot;&gt;&amp;#91;D, D, J, D, 15A, 15A&amp;#93;&lt;/span&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;When I set &#8220;enablestellarsolve = no&#8221;, an output pfsZcandidate*.file properly contains 5 HDUs, but when I set &#8220;enablestellarsolve = yes&#8221;, an output file contains only 2 HDUs. It would be great if the drp_1dpipe contains additional HDUs also for stellar analyses.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="14904">PIPE1D-25</key>
            <summary>Output pfsZcandidate*.fits files for the stellar solver</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="10001" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The assignee thinks that the issue is resolved, and it&apos;s being reviewed before merge/close">In Review</status>
                    <statusCategory id="4" key="indeterminate" colorName="yellow"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="ali.allaoui">Ali Allaoui</assignee>
                                    <reporter username="ishigaki">ishigaki</reporter>
                        <labels>
                    </labels>
                <created>Tue, 29 Sep 2020 23:49:53 +0000</created>
                <updated>Fri, 17 Dec 2021 12:55:36 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="17825" author="vlebrun" created="Fri, 2 Oct 2020 10:07:15 +0000"  >&lt;p&gt;Dear Miho&lt;/p&gt;

&lt;p&gt;actually we did not include the other HDUs, which contain the PDF, the model and the line measurements in the stellar solver output, because it did not seem relevant. Indeed the PDF is only computed on the very short redshift range &#160;&lt;span class=&quot;error&quot;&gt;&amp;#91;-0.001;0.001&amp;#93;&lt;/span&gt;, the model is only the template, and we do not perform line measurements on stars.&#160;&lt;/p&gt;

&lt;p&gt;For consistency, we will include those HDUs within this branch&lt;/p&gt;

&lt;p&gt;Vincent&lt;/p&gt;</comment>
                            <comment id="17827" author="ishigaki" created="Sun, 4 Oct 2020 21:23:12 +0000"  >&lt;p&gt;Dear Vincent,&#160;&lt;/p&gt;

&lt;p&gt;Thank you for your comments! Yes, that would be very helpful. For the stellar solver, I set&lt;/p&gt;

&lt;p&gt;&quot;redshiftrange&quot; &lt;span class=&quot;error&quot;&gt;&amp;#91;-0.001; 0.001&amp;#93;&lt;/span&gt;, &#160;&quot;redshiftstep&quot; 1.0e-6. Is this very small step compatible with the pipeline algorithm?&lt;/p&gt;</comment>
                            <comment id="17828" author="vlebrun" created="Mon, 5 Oct 2020 06:54:03 +0000"  >&lt;p&gt;Well, all steps values are theoretically OK, but the computation time will increase. It should remain OK as the resdshit range is small&lt;/p&gt;

&lt;p&gt;Vincent&lt;/p&gt;</comment>
                            <comment id="17829" author="ishigaki" created="Mon, 5 Oct 2020 08:22:28 +0000"  >&lt;p&gt;Thanks for the confirmation. Then, we will, at the moment, continue using&#160; &quot;redshiftrange&quot; &lt;span class=&quot;error&quot;&gt;&amp;#91;-0.001; 0.001&amp;#93;&lt;/span&gt;, &#160;&quot;redshiftstep&quot; 1.0e-6 for stellar analyses.&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="15000">DAMD-92</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|zzs2s8:</customfieldvalue>

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

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