<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:38:57 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-1744] Pull BEE ADIO control (gatevalve/SAM power) out into own actor.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1744</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Control of the gatevalve and SAM power is done via a kernel module and a thin cython shim, both in ics_xcu_rtdADIO. When the controlling program (the xcuActor) exits or the device is closed, the H4 DAQ is powered down and the gatevalve is closed. Both of these can be annoying/surprising/troublesome/problematic, especially after a recent change to the SAM/BEE power board.&lt;/p&gt;

&lt;p&gt;I think factoring the gatevalve and SAM power control off into a tiny and stable actor would help significantly. The interface is tiny: we are flipping or reading four bits via very few commands (sam on/off/status, gatevalve open/close/status).&lt;/p&gt;


</description>
                <environment></environment>
        <key id="23033">INSTRM-1744</key>
            <summary>Pull BEE ADIO control (gatevalve/SAM power) out into own actor.</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="cloomis">cloomis</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>NIR</label>
                            <label>SPS</label>
                            <label>near-term</label>
                    </labels>
                <created>Wed, 5 Oct 2022 13:19:33 +0000</created>
                <updated>Thu, 20 Jul 2023 15:14:43 +0000</updated>
                                                                            <component>ics_xcuActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="34084" author="cloomis" created="Thu, 20 Jul 2023 12:20:40 +0000"  >&lt;p&gt;Bump, due to twice cooling n3 ASICs to failure.&lt;/p&gt;

&lt;p&gt;An alternate fix might be to modify the kernel driver to &lt;b&gt;not&lt;/b&gt; clear ADIO bits when user connections close. Why not just leave them as is? I&apos;ll look at the code.&lt;/p&gt;</comment>
                            <comment id="34085" author="cloomis" created="Thu, 20 Jul 2023 15:14:43 +0000"  >&lt;p&gt;Take that back: I&apos;m not touching the kernel driver. &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|02qpjd:00xznup2d04</customfieldvalue>

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