<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:33:45 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-1281] move device/instrument configuration into a single repo.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1281</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;I&apos;m reviving that subject following the discussion with &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis&quot; class=&quot;user-hover&quot; rel=&quot;cloomis&quot;&gt;cloomis&lt;/a&gt; today.&lt;br/&gt;
I think we manage to distinguish our needs and expectations, I will be trying to rephrase it here to avoid further confusions. I&apos;m going to start with what we currently have : &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;a per actor configuration file in $ICS_ACTOR_DIR/etc/&lt;/li&gt;
	&lt;li&gt;InstData class in pfs_utils to persist/load mhs keywords to/from disk.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;What we want is to move as much information as possible for the etc file to a common repo.&lt;br/&gt;
yaml is very likely to be right choice, so that we can factorize configuration shared among identical module/unit and specify per-instance dedicated values.&lt;br/&gt;
This/these file(s) are edited/written by human in most (all?) cases.&lt;/p&gt;

&lt;p&gt;The persistence mechanism is completely machine-oriented, it&apos;s read and written by a program.&lt;br/&gt;
It can be seen as an instrument snapshot, so that some variable/state can be reloaded if needed for instance after :&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;software reboot&lt;/li&gt;
	&lt;li&gt;some power cycle&lt;/li&gt;
	&lt;li&gt;temporary hardware issue...&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Those two mechanisms are actually different and so their time constant.&lt;br/&gt;
I hope it clarifies the big picture. &lt;/p&gt;
</description>
                <environment></environment>
        <key id="15654">INSTRM-1281</key>
            <summary>move device/instrument configuration into a single repo.</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</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="arnaud.lefur">arnaud.lefur</assignee>
                                    <reporter username="arnaud.lefur">arnaud.lefur</reporter>
                        <labels>
                            <label>SPS</label>
                    </labels>
                <created>Thu, 20 May 2021 19:15:22 +0000</created>
                <updated>Tue, 4 Oct 2022 20:14:14 +0000</updated>
                            <resolved>Tue, 4 Oct 2022 20:14:13 +0000</resolved>
                                                                    <component>ics_enuActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="30600" author="cloomis" created="Thu, 17 Mar 2022 23:25:01 +0000"  >&lt;p&gt;We have been moving forward with the actor configuration part of this, putting per-actor (&quot;enu&quot;, not &quot;enu-sm2&quot;) yaml files in &lt;tt&gt;$PFS_INSTDATA/config/actors/&lt;/tt&gt;. &lt;/p&gt;

&lt;p&gt;Replacing the last part of the per actor (&quot;enu-sm2&quot;, not &quot;enu&quot;) .cfg files will require a change to tron_actorcore itself, since that is what sets up the connections to the tron hub and the actor logging. See&lt;/p&gt;
</comment>
                            <comment id="31543" author="arnaud.lefur" created="Tue, 4 Oct 2022 20:14:14 +0000"  >&lt;p&gt;all API has been implemented in pfs_instdata/ics_utils and available now in tron_actorcore.&lt;br/&gt;
it&apos;s now up to each actor to use it and get rid of the old etc/configParser file.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="11620">INSTRM-119</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="22552">INSTRM-1485</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22684">INSTRM-1552</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|02qple:y</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <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="117">SM1PD-2021 A 14</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>