<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:03:09 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-1127] Type of broadband fluxes used by flux calibration should be configurable</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1127</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;&lt;tt&gt;fitPfsReferenceFlux.py&lt;/tt&gt; currently uses &lt;tt&gt;pfsConfig.fiberFlux&lt;/tt&gt; but it has to be &lt;tt&gt;pfsConfig.psfFlux&lt;/tt&gt; because &lt;tt&gt;pfsConfig&lt;/tt&gt; files that came out of observation contain &lt;tt&gt;psfFlux&lt;/tt&gt; only.&lt;/p&gt;

&lt;p&gt;Because there are disagreements as to which flux to use, we should make it configurable.&lt;/p&gt;</description>
                <environment></environment>
        <key id="23168">PIPE2D-1127</key>
            <summary>Type of broadband fluxes used by flux calibration should be configurable</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</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="sogo.mineo">sogo.mineo</assignee>
                                    <reporter username="sogo.mineo">sogo.mineo</reporter>
                        <labels>
                            <label>flux-calibration</label>
                    </labels>
                <created>Mon, 12 Dec 2022 05:41:23 +0000</created>
                <updated>Wed, 14 Dec 2022 05:06:44 +0000</updated>
                            <resolved>Wed, 14 Dec 2022 05:06:44 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="31950" author="price" created="Mon, 12 Dec 2022 15:31:53 +0000"  >&lt;p&gt;Surely fiberFlux and psfFlux should be very close to identical for the stars we want to use to calibrate against, and if they&apos;re not then it&apos;s not a suitable calibration source? The two should differ only for extended sources.&lt;/p&gt;</comment>
                            <comment id="31953" author="sogo.mineo" created="Mon, 12 Dec 2022 23:50:37 +0000"  >&lt;p&gt;They are close, but in reality pfsConfig.fiberFlux is NaN while pfsConfig.psfFlux is finite. The current code needs amending because it uses fiberFlux only. To hard-code psfFlux will suffice, but it is also easy to add a configuration parameter to choose between fiberFlux and psfFlux.&lt;/p&gt;</comment>
                            <comment id="31956" author="sogo.mineo" created="Tue, 13 Dec 2022 06:11:54 +0000"  >&lt;p&gt;Could you review this PR? I made two commits: the first one is the essential one. In the second commit, I typed several python scripts.&lt;/p&gt;</comment>
                            <comment id="31969" author="sogo.mineo" created="Wed, 14 Dec 2022 05:06:44 +0000"  >&lt;p&gt;Merged. (I don&apos;t think it a necessary condition for merging that mypy runs cleanly...) Thank you for the review.&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|zzsvsv:</customfieldvalue>

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

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