<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:50:53 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>[INFRA-246] Location for F-star template data</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-246</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;In order to address &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/SIM2D-113&quot; title=&quot;Provide F-star spectra &quot; class=&quot;issue-link&quot; data-issue-key=&quot;SIM2D-113&quot;&gt;&lt;del&gt;SIM2D-113&lt;/del&gt;&lt;/a&gt;, a physical location to store and share F-star data needs to be discussed and agreed between the PFS Project Office and Princeton. &lt;/p&gt;

&lt;p&gt;The total size of that data is still TBC, but can vary between 30 and 300 GB. &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=takuji.yamashita&quot; class=&quot;user-hover&quot; rel=&quot;takuji.yamashita&quot;&gt;Takuji Yamashita&lt;/a&gt; to confirm.&lt;/p&gt;</description>
                <environment></environment>
        <key id="13518">INFRA-246</key>
            <summary>Location for F-star template data</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="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                    </labels>
                <created>Fri, 5 Apr 2019 16:27:57 +0000</created>
                <updated>Fri, 12 Apr 2019 17:21:34 +0000</updated>
                            <resolved>Fri, 12 Apr 2019 17:20:58 +0000</resolved>
                                                                    <component>newitem</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                <comments>
                            <comment id="15292" author="rhl" created="Fri, 5 Apr 2019 17:19:43 +0000"  >&lt;p&gt;Depending on how this data is used in the pipelines it may need to be visible as a path relative to the root of the raw data.&#160; This isn&apos;t a problem (as we can use symbolic links), but we should be aware.&#160; We will also need to make this data available at all PFS sites, and handle versioning it as our knowledge evolves.&lt;/p&gt;

&lt;p&gt;Those data volumes seem high to me, and I suspect that we can design a much more efficient format if necessary.&lt;/p&gt;</comment>
                            <comment id="15308" author="msyktnk" created="Thu, 11 Apr 2019 07:28:02 +0000"  >&lt;p&gt;Here is a revised estimate.&#160; If we store only the flux, each file (including extrapolation) will be about 4Mbytes in the fits format.&#160; The spectral sampling is 0.01A/pix, which is a very fine sampling and we do not need that.&#160; If we bin the spectra to, e.g., 0.1A/pix, which is still fine enough for our purpose, the data volume will be 1/10.&#160; We have not decided yet which type of stars to use, but if we limit ourselves to 5500&amp;lt;Teff&lt;span class=&quot;error&quot;&gt;&amp;#91;K&amp;#93;&lt;/span&gt;&amp;lt;8000K, which roughly corresponds to mid-G to early-A, there are ~6000 spectra.&#160; So, 4Mbytes * 0.1 * 6000 = 2.4Gbytes in total.&lt;/p&gt;</comment>
                            <comment id="15313" author="hassan" created="Fri, 12 Apr 2019 16:12:48 +0000"  >&lt;p&gt;Following the 2D DRP technical telecon 2019-04-12: The total volume of the data is now relatively small. As these data need to be available at all locations where the pipeline is being run, we should only specify where in the Butler path these data are located. &lt;/p&gt;

&lt;p&gt;I will therefore close this ticket and create a new one for the Butler location.&lt;/p&gt;</comment>
                            <comment id="15317" author="hassan" created="Fri, 12 Apr 2019 17:20:58 +0000"  >&lt;p&gt;Work will now be addressed under &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-51&quot; title=&quot;Theoretical spectra for flux calibration: location relative to Butler&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-51&quot;&gt;DAMD-51&lt;/a&gt;.&lt;/p&gt;
</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="13413">SIM2D-113</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13529">INFRA-247</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13533">DAMD-51</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|zx0060:</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>