<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:34:54 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-1385] Make MCS readouts more efficient: pipe reads to mcsActor w/o going to disk</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1385</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The canonexp readout and mcs exposure processing take significantly more time than we want, and can be made more efficient. As it stands a single 0.8s exposure takes more than 10s. From looking at the timings, three obvious improvements are:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;run the canonexp library routines in a permanently running daemon, which can pipe N*0.8s reads to the mcsActor without going to disk.&lt;/li&gt;
	&lt;li&gt;likewise, write the PFSC files in a background process, so that nothing waits on the writes.&lt;/li&gt;
	&lt;li&gt;mask off the non-PFI parts of the image and otherwise tune the background subtraction and centroiding.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This ticket addresses the first of these improvements.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18088">INSTRM-1385</key>
            <summary>Make MCS readouts more efficient: pipe reads to mcsActor w/o going to disk</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="chyan">chyan</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Fri, 8 Oct 2021 14:52:08 +0000</created>
                <updated>Sun, 21 Nov 2021 06:56:15 +0000</updated>
                            <resolved>Sun, 21 Nov 2021 06:56:15 +0000</resolved>
                                                                    <component>ics_mcsActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="24798" author="chyan" created="Tue, 26 Oct 2021 08:47:58 +0000"  >&lt;p&gt;&lt;br/&gt;
Canon did not provide the library for the camera, so we just use it &apos;as it is&apos;.  So, the first option is not the feasible path before the e-run. &lt;/p&gt;</comment>
                            <comment id="24805" author="cloomis" created="Tue, 26 Oct 2021 15:24:17 +0000"  >&lt;p&gt;The canonexp.c program can at the very least pipe the output to the caller, right? There should be no file writes between the expose command and the generation of the mcs_data, etc. rows.&lt;/p&gt;</comment>
                            <comment id="24821" author="hassan" created="Wed, 27 Oct 2021 02:12:01 +0000"  >&lt;p&gt;Chi-Hung requires more time to think about this. This will be fixed at the end of this week or early next week.&lt;/p&gt;</comment>
                            <comment id="25094" author="chyan" created="Tue, 16 Nov 2021 00:30:46 +0000"  >&lt;p&gt;Discussed with Craig couple hours ago, the current low level calls are not easy to transform with Cython. &#160;This is because the C program deals with shutter and detector readouts. &#160;Also those low level call has to maintain the synchronicity, so that the exposure time will exactly the same. &#160;Using Cython is a ultimate goal to do, but we can use standard output as work around.&lt;/p&gt;</comment>
                            <comment id="25172" author="chyan" created="Sun, 21 Nov 2021 06:56:05 +0000"  >&lt;p&gt;Branch test on telescope and merged to master. &#160;Now working on for canon 50M.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="18275">INSTRM-1414</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="18238">INSTRM-1396</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="18305">INSTRM-1425</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="18306">INSTRM-1426</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="18239">INSTRM-1397</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|zzs2x4:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="123">PreEngRun4</customfieldvalue>
    <customfieldvalue id="124">EngRun3Cleanup</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>