<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:24:03 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-345] Support &quot;online&quot; and &quot;offline&quot; OCSes.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-345</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;PFS will want to be able to run (take exposures) anytime, whether allocated or not, whether on the telescope or not.&lt;/p&gt;

&lt;p&gt;Discussions yielded:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;PFS will have an &quot;online&quot; and an &quot;offline&quot; OCS. The online one is the real operational Subaru copy, the offline one is something which PFS will run, can connect to, and will let us never worry about interfering with observations by other instruments.&lt;/li&gt;
	&lt;li&gt;Subaru will come up with a single frame counter accessible to both.&lt;/li&gt;
	&lt;li&gt;PFS will come up with a way to seamlessly and quickly switch between the two. &quot;gen2 online&quot;/&quot;gen2 offline&quot; is the way I think of it.&lt;/li&gt;
	&lt;li&gt;The offline OCS should be clever about headers: what to provide, what to declare, what to lie about.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This ticket should simply defer to at least two others: for the Subaru OCS work and for the PFS &lt;tt&gt;ics_gen2Actor&lt;/tt&gt; work.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12318">INSTRM-345</key>
            <summary>Support &quot;online&quot; and &quot;offline&quot; OCSes.</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="-1">Unassigned</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                    </labels>
                <created>Mon, 30 Apr 2018 22:01:32 +0000</created>
                <updated>Fri, 9 Nov 2018 01:10:10 +0000</updated>
                            <resolved>Fri, 9 Nov 2018 01:10:10 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="14509" author="cloomis" created="Fri, 9 Nov 2018 01:10:10 +0000"  >&lt;p&gt;The visit/frame number function has been tested: both observatory servers use the same database table.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-462&quot; title=&quot;Add command to switch Gen2 servers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-462&quot;&gt;INSTRM-462&lt;/a&gt; deals with switching between servers, and/or &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-379&quot; title=&quot;Invert nesting of OCS/MHS parts of ics_gen2Actor&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-379&quot;&gt;INSTRM-379&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="12366">INSTRM-379</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|ii04fb:</customfieldvalue>

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