<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:35:02 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-1397] Fast SpS reads for cobra moves behind blackspots</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1397</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;During the Sept 2021 Engineering Run, the SpS was used to determine how well a cobra can be positioned behind a blackspot given that the MCS CANON camera was not sensitive enough. Please find ways to improve the read time, for example special exposures where the data are windowed and binned (as the flux is the main output needed from the SpS).&lt;/p&gt;</description>
                <environment></environment>
        <key id="18239">INSTRM-1397</key>
            <summary>Fast SpS reads for cobra moves behind blackspots</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="cloomis">cloomis</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                            <label>EngRun</label>
                            <label>SPS</label>
                    </labels>
                <created>Mon, 11 Oct 2021 17:33:35 +0000</created>
                <updated>Fri, 19 Nov 2021 07:54:49 +0000</updated>
                            <resolved>Fri, 19 Nov 2021 07:54:49 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                            <comment id="22552" author="cloomis" created="Mon, 11 Oct 2021 18:39:21 +0000"  >&lt;p&gt;I propose reading out the middle couple hundred rows. The wipe for a full frame takes ~7-8s, so this should take ~5s without much effort (i.e. without making a faster wipe). &lt;/p&gt;

&lt;p&gt;If we trust the detector map, we could use the first few rows and skip the wipe. So in practice I&apos;d implement this as &lt;tt&gt;read window=row0,row1&lt;/tt&gt; and wipe up to row0.&lt;/p&gt;</comment>
                            <comment id="24979" author="cloomis" created="Tue, 9 Nov 2021 16:20:56 +0000"  >&lt;p&gt;Added &lt;tt&gt;row0=N nrows=M&lt;/tt&gt; to &lt;tt&gt;ccd read&lt;/tt&gt; command. This extends the existing &lt;tt&gt;nrows=&lt;/tt&gt; logic, which has always simply read out some rows, without caring about image file format.  But if both are specified, a full size image is generated, with the band of rows placed appropriately and the rest left at 0.&lt;/p&gt;

&lt;p&gt;For the wipe, requesting &lt;tt&gt;nrows=0&lt;/tt&gt; makes the &lt;tt&gt;exposureState=&lt;/tt&gt; keywords get spit out correctly and the  puts the detector voltages in the integration mode, but no clocking is done. This also extends existing engineering functionality.&lt;/p&gt;

&lt;p&gt;When reading a band of rows, &lt;tt&gt;W_CDROW0&lt;/tt&gt; and &lt;tt&gt;W_CDROWN&lt;/tt&gt; are added to the PHDU.&lt;/p&gt;

&lt;p&gt;Still slower than I want, but most of the easy time has been picked out. Umm, for row0=1800 and nrows=400, 11s.&lt;/p&gt;

&lt;p&gt;Need to confirm that the data look good, but am waiting on a lamp replacement for that.&lt;/p&gt;</comment>
                            <comment id="25165" author="cloomis" created="Fri, 19 Nov 2021 07:54:49 +0000"  >&lt;p&gt;Implemented as discussed. Could still make it a bit faster but there is no tall pole.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="18275">INSTRM-1414</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="18240">PIPE2D-914</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="18088">INSTRM-1385</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="18331">INSTRM-1439</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|zzs2x3:</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>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>