<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:53:12 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>[FIBERALLOC-37] UPdate ets_fiberalloc to output pfsDesign FITS files</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-37</link>
                <project id="10500" key="FIBERALLOC">Target to fiber allocation and configuration</project>
                    <description>&lt;p&gt;To my understanding, ets_fiberalloc is supposed toi output pfsDesign files in FITS format. To achieve this, I plan to&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;have ets_fiberalloc import pfs.datamodel for easy creation of these files&lt;/li&gt;
	&lt;li&gt;put all information I have currently available into these files.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;But there are large parts of the file, like &quot;tract&quot;, &quot;patch&quot; and everything flux-related, which I can only fill with dummy values.&lt;/p&gt;</description>
                <environment></environment>
        <key id="15054">FIBERALLOC-37</key>
            <summary>UPdate ets_fiberalloc to output pfsDesign FITS files</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="Martin.Reinecke">Martin Reinecke</assignee>
                                    <reporter username="Martin.Reinecke">Martin Reinecke</reporter>
                        <labels>
                    </labels>
                <created>Tue, 1 Dec 2020 09:08:48 +0000</created>
                <updated>Wed, 8 Mar 2023 08:21:29 +0000</updated>
                            <resolved>Wed, 8 Mar 2023 08:21:29 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="32359" author="martin.reinecke" created="Tue, 7 Mar 2023 08:47:08 +0000"  >&lt;p&gt;There have been no complaints about incomplete FITS files for more than two years, so I assume that the production of files that are only partially filled is OK.&lt;br/&gt;
The current philosophy seems to be that every software component fills the part of the file it is responsible for, leading to a complete data product at the end of the chain.&lt;/p&gt;</comment>
                            <comment id="32360" author="martin.reinecke" created="Tue, 7 Mar 2023 08:53:57 +0000"  >&lt;p&gt;Dear Kiyoto,&lt;/p&gt;

&lt;p&gt;please let us know if you agree with my impression that the fiber allocator actually does not have to fill every field of its output FITS file. If you agree, this issue can be closed.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
  Martin&lt;/p&gt;</comment>
                            <comment id="32368" author="kiyoto.yabe" created="Tue, 7 Mar 2023 23:39:24 +0000"  >&lt;p&gt;Thank you, Martin. Yes, a script to generate pfsDesigns file is responsible for some fields in the design files,&#160;which was actually used in the past engineering runs without any problems (as far as I know). So, we can close this issue.&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|zzs38g:</customfieldvalue>

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