<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:33: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>[INSTRM-1266] VisitID and FrameID name convention of MCS-FPS interaction</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1266</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The FPS actor now calls the MCS actor to do exposure.  However, the image name generated by MCS is not following the convention  f&apos;PFSC&lt;/p&gt;
{VisitID}
{FrameID}
&lt;p&gt;.fits&apos;.  &lt;/p&gt;</description>
                <environment></environment>
        <key id="15593">INSTRM-1266</key>
            <summary>VisitID and FrameID name convention of MCS-FPS interaction</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="cloomis">cloomis</assignee>
                                    <reporter username="chyan">chyan</reporter>
                        <labels>
                    </labels>
                <created>Fri, 7 May 2021 01:51:57 +0000</created>
                <updated>Tue, 3 Aug 2021 02:54:39 +0000</updated>
                            <resolved>Tue, 3 Aug 2021 02:54:39 +0000</resolved>
                                                                    <component>ics_fpsActor</component>
                    <component>ics_mcsActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="19285" author="chyan" created="Fri, 7 May 2021 01:57:04 +0000"  >&lt;p&gt;Looking down to the MCS actor, the file name is given by the getNextFilename function.  This function calls gen2Actor in line 218.&lt;/p&gt;</comment>
                            <comment id="19286" author="cloomis" created="Fri, 7 May 2021 01:59:42 +0000"  >&lt;p&gt;This needs to be changed for Subaru:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;iic gets the visit from gen2&lt;/li&gt;
	&lt;li&gt;iic sends visit= to fps for all the top-level commands (motor maps, convergence, etc.). iic already does that for SPS, btw.&lt;/li&gt;
	&lt;li&gt;iic sends visit= and frame= down to mcs for each exposure.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;getNextFilename is only for standalone testing.&lt;/p&gt;</comment>
                            <comment id="19287" author="cloomis" created="Fri, 7 May 2021 03:59:13 +0000"  >&lt;p&gt;This is actually slightly more involved than I stated. Because it is so informative to group data by action (motor map, convergence), cobraCharmer has been creating a directory for each of these, with subdirectories for PFxC and stack files, logs, and output files (.xml and the file versions of the opdb tables, mainly).&lt;/p&gt;

&lt;p&gt;I think we should continue doing this. Which essentially boils down to telling the mcsActor where to save the PFxC files. For now I propose being explicit (path=/data/raw/$date/fps/$runName), though we could also send the name of the&#160;&quot;run directory&quot; (run=$runName) and use a/the butler to instantiate the file path.&lt;/p&gt;</comment>
                            <comment id="21684" author="cloomis" created="Tue, 13 Jul 2021 03:16:29 +0000"  >&lt;p&gt;I was wrong. Mcs should dumbly save PFxC files in &lt;tt&gt;/data/raw/mcs&lt;/tt&gt;. They partition into runs nicely by visit. Fps can make structured directories separately, and can have symbolic links to the read data files. &lt;/p&gt;

&lt;p&gt;We &lt;b&gt;might&lt;/b&gt; want to add mcs commands to control the generation of the very useful stack image files &amp;#8211; with 100 Mpix cameras it does pay to avoid round trips to disk over the network.&lt;/p&gt;</comment>
                            <comment id="21770" author="cloomis" created="Tue, 3 Aug 2021 02:54:39 +0000"  >&lt;p&gt;Basics done. Depends on unmerged opdb changes.&lt;/p&gt;

&lt;p&gt;Merged at a2bb35a, tagged 1.5.0&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|zzs56w:</customfieldvalue>

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