<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:33: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>[INSTRM-1278] Add commands to generate complete pfsDesign and pfsConfig files and rows</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1278</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;We need top-level iic commands which generate pfsDesign and pfsConfig files, based on the configuration of the entire instrument (primarily the sps.lightSource keys, the targeting and FPS information, the DCBx and SuNSS configurations, and the pfs_instdata status ).  These would be called at the start of each field or exposure.&lt;/p&gt;

&lt;p&gt;It may be that we will want per-SM design/configs, but I think those should be derived from the configuration of the entire instrument. I propose that we always generate files describing all 2604 slit holes and treat those as the single sources for all further HDUs, opdb rows, etc.&lt;/p&gt;

&lt;p&gt;An implementation note: any files should be put into per-night directories &lt;tt&gt;/data/raw/$date/pfsConfig/&lt;/tt&gt;, say, just to keepthe pfsDesign directory from becoming a bottleneck.&lt;/p&gt;</description>
                <environment></environment>
        <key id="15637">INSTRM-1278</key>
            <summary>Add commands to generate complete pfsDesign and pfsConfig files and rows</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="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="cloomis">cloomis</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>EngRun</label>
                            <label>SPS</label>
                    </labels>
                <created>Mon, 17 May 2021 18:35:26 +0000</created>
                <updated>Fri, 17 Dec 2021 12:35:41 +0000</updated>
                            <resolved>Fri, 22 Oct 2021 21:23:22 +0000</resolved>
                                                                    <component>ics_iicActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="21891" author="cloomis" created="Thu, 2 Sep 2021 03:17:20 +0000"  >&lt;p&gt;For each iteration of the fps convergence sequence, the fpsActor writes the achieved fiber positions in the cobra_match table. At the end of the sequence we need to read all the data from the pfsDesign ingest, merge with the final cobra_match rows, and write out pfsConfig files.&lt;/p&gt;

&lt;p&gt;Actual file I/O must be done by the existing datamodel PfsConfig class.&lt;/p&gt;</comment>
                            <comment id="23366" author="cloomis" created="Fri, 22 Oct 2021 21:23:22 +0000"  >&lt;p&gt;This was preliminary and incomplete. Replaced by the &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1422&quot; title=&quot;Publish complete pfsDesign/pfsConfig files before any exposure.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1422&quot;&gt;INSTRM-1422&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="16900">INSTRM-1299</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="17016">INSTRM-1348</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="15483">INSTRM-1214</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|02qpqk:c</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="108">SM1PD-2021 A9</customfieldvalue>
    <customfieldvalue id="110">SM1PD-2021 A10</customfieldvalue>
    <customfieldvalue id="112">SM1PD-2021 A 11</customfieldvalue>
    <customfieldvalue id="113">SM1PD-2021 A 12</customfieldvalue>
    <customfieldvalue id="114">SM1PD-2021 A 13</customfieldvalue>
    <customfieldvalue id="118">EngRun03</customfieldvalue>

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