<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:24:13 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-361] Add mechanism to tell STS that a subsystem is offline.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-361</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;We need a standard way to declare to STS that parts of the PFS instrument are offline. The obvious immediate need is the MCS, which will usually be powered off. &lt;/p&gt;</description>
                <environment></environment>
        <key id="12339">INSTRM-361</key>
            <summary>Add mechanism to tell STS that a subsystem is offline.</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="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="hiro">Yoshida, Hiroshige</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>subaru-personnel</label>
                    </labels>
                <created>Thu, 10 May 2018 15:25:04 +0000</created>
                <updated>Thu, 7 Nov 2019 01:20:36 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="13391" author="hiro" created="Thu, 10 May 2018 16:01:34 +0000"  >&lt;p&gt;If Subaru adds an ability to match STS text data using RE or wildcard, PFS could specify for each data sources that it is offline by setting its text data to &quot;OFFLINE&quot; or some other standard string. Will this work?&lt;/p&gt;</comment>
                            <comment id="13393" author="atsushi.shimono" created="Fri, 11 May 2018 03:52:20 +0000"  >&lt;p&gt;I think we had agreed to have some monitoring mechanism whether each actor is connected and live to the MHS server, and also to expose these status as &quot;status&quot; from (a) monitoring actor, no? &lt;br/&gt;
If it is possible to map and push these as STS status (or just flag/binary one), it seems request is implemented.&lt;/p&gt;</comment>
                            <comment id="13395" author="cloomis" created="Fri, 11 May 2018 09:59:10 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro&quot; class=&quot;user-hover&quot; rel=&quot;hiro&quot;&gt;Yoshida, Hiroshige&lt;/a&gt; For MCS I was thinking of a larger switch. Not per-datum, but applying to &quot;PFS MCS&quot; or &quot;PFS PFI&quot;. The &quot;offline&quot;/&quot;online&quot; switch on the GUI: is there a way to control that?&lt;/p&gt;

&lt;p&gt;But yes, regexp matching would also be nice, so that we could express things like: &lt;tt&gt;isAlarm = not (OK or OFFLINE)&lt;/tt&gt;. Clearly per-instrument switches will not work for everything, so we will need per-datum control.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=atsushi.shimono&quot; class=&quot;user-hover&quot; rel=&quot;atsushi.shimono&quot;&gt;shimono&lt;/a&gt; We need to distinguish between an actor/device being offline on purpose, or disconnected because of a failure. We will need alertsActor commands to declare known disconnections, and those will need to be passed on to STS so that all the sources do not alarm. I just did not see a good mechanism for doing so.&lt;/p&gt;</comment>
                            <comment id="13403" author="hiro" created="Mon, 14 May 2018 16:11:03 +0000"  >&lt;p&gt;A set of metrics in the same group (e.g., &quot;Instrument: PFS MCS&quot;) can be enabled / disabled at once (there are online / offline links at the top of the table).&lt;/p&gt;</comment>
                            <comment id="13404" author="cloomis" created="Mon, 14 May 2018 17:17:31 +0000"  >&lt;p&gt;Yes. But can that be done without the GUI?&lt;/p&gt;</comment>
                            <comment id="13405" author="hiro" created="Mon, 14 May 2018 17:38:37 +0000"  >&lt;p&gt;No.&lt;/p&gt;</comment>
                            <comment id="13812" author="cloomis" created="Wed, 25 Jul 2018 23:56:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro&quot; class=&quot;user-hover&quot; rel=&quot;hiro&quot;&gt;Yoshida, Hiroshige&lt;/a&gt; Is that &quot;No&quot; saying that the functionality cannot be added?&lt;/p&gt;</comment>
                            <comment id="13813" author="hiro" created="Thu, 26 Jul 2018 03:11:37 +0000"  >&lt;p&gt;No. We (= Subaru) could implement such a functionality, e.g., as a microservice. We have to figure out how to AA (same for STSradio), however.&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|ii04jr:</customfieldvalue>

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