<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:34:36 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>[DAMD-132] Will the science database include &quot;Class II&quot; pipeline products?</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/DAMD-132</link>
                <project id="10400" key="DAMD">Data Model</project>
                    <description>&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-97&quot; title=&quot;Add missing 2D pipeline outputs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-97&quot;&gt;&lt;del&gt;DAMD-97&lt;/del&gt;&lt;/a&gt; will audit &lt;tt&gt;datamodel.txt&lt;/tt&gt; for missing 2D pipeline products and add anything that&apos;s missing. However, it&apos;s not clear whether we need python I/O implementations in the datamodel package for the &quot;Class II&quot; products (not commonly used by science users, e.g., the sky flux models and flux calibration vectors; see &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-97&quot; title=&quot;Add missing 2D pipeline outputs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-97&quot;&gt;&lt;del&gt;DAMD-97&lt;/del&gt;&lt;/a&gt;). One clear reason to add a python I/O implementation would be if it is anticipated that the science database will include these products.&lt;/p&gt;

&lt;p&gt;Could you please report whether you anticipate the science database including &quot;Class II&quot; pipeline products?&lt;/p&gt;</description>
                <environment></environment>
        <key id="22767">DAMD-132</key>
            <summary>Will the science database include &quot;Class II&quot; pipeline products?</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="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="msyktnk">Masayuki Tanaka</assignee>
                                    <reporter username="price">price</reporter>
                        <labels>
                    </labels>
                <created>Thu, 5 May 2022 18:42:27 +0000</created>
                <updated>Mon, 3 Jul 2023 01:09:47 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="30842" author="msyktnk" created="Fri, 6 May 2022 06:20:31 +0000"  >&lt;p&gt;We do not need the I/O interfaces now, but we may want to have them in the future.&#160; We will make all data products including intermediate pipeline products available at the science database.&#160; Science users will not use, e.g., calibration files, very often as you say, but if they find I/O interfaces useful, then we can consider implementing them.&#160; So, my answer to your question is; let&apos;s leave it as a future question, unless we need to freeze the datamodel package now for good.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="15062">DAMD-97</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|02qpjd:4</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>