<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:39:23 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-1781] Punch list to start the engineering run in November 2022</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1781</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Here is a test and check list for software updates before coming the engineering run (2022/11/14-20). Note that all the software should be tagged and implemented at the summit/Hilo system.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;AG name (&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-138&quot; title=&quot;Add AGCC filename format&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-138&quot;&gt;&lt;del&gt;DAMD-138&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1764&quot; title=&quot;Rename AGCC image files&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1764&quot;&gt;&lt;del&gt;INSTRM-1764&lt;/del&gt;&lt;/a&gt;)&lt;/li&gt;
&lt;/ol&gt;


&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;Take AG camera frame and check the name (Yan)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;ol&gt;
	&lt;li&gt;XML file
	&lt;ul&gt;
		&lt;li&gt;Check bits of masked cobras in modified xml file (Yan)&lt;/li&gt;
		&lt;li&gt;Generate PfsDesign with new bit flags (Onodera)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;RHL PFS scheme
	&lt;ul&gt;
		&lt;li&gt;Document &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1765&quot; title=&quot;Document scheme for measuring cobra offset, brightness and PSF &quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1765&quot;&gt;&lt;del&gt;INSTRM-1765&lt;/del&gt;&lt;/a&gt; (Lupton)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;opDB grouping
	&lt;ul&gt;
		&lt;li&gt;Test with 2+ frames with the same groupId (Le Fur)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;opDB schema integrity
	&lt;ul&gt;
		&lt;li&gt;guidestars objId &#8211; test by loading PfsDesign/config (Onodera or Yabe)&lt;/li&gt;
		&lt;li&gt;population by ASIAA &#8211; test by MCS frame (Karr)&#160;&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;SM1+SM3 operation
	&lt;ul&gt;
		&lt;li&gt;Can SM1 be operated independently of SM3 and concurrently (Le Fur, Loomis)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Optical Crosstalk
	&lt;ul&gt;
		&lt;li&gt;Regenerate coefficients (Le Fur, Price)&lt;/li&gt;
		&lt;li&gt;Fix bug&#160; on one side of detector &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1100&quot; title=&quot;Optical cross-talk doesn&amp;#39;t work on one side of detector&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-1100&quot;&gt;&lt;del&gt;PIPE2D-1100&lt;/del&gt;&lt;/a&gt; (Lupton)&lt;/li&gt;
		&lt;li&gt;Test? (Price)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;OBJECT card contents
	&lt;ul&gt;
		&lt;li&gt;Look at the contents as data are taken (Loomis)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;DRP CALIB (Note: SuNSS cannot be used for SM3)
	&lt;ul&gt;
		&lt;li&gt;SM3 DCB data &#8211; detectorMaps (b+r), fiberProfiles (Siddiqui)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;After POpt2 installed (i.e. the beginning of the run), the following items can be tested:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Cobra convergence&lt;/li&gt;
	&lt;li&gt;Raster scan&lt;/li&gt;
	&lt;li&gt;Full Boresight calculation (check population of the DB)&lt;/li&gt;
	&lt;li&gt;Check population of agc_data flags column (Karr)&lt;/li&gt;
&lt;/ol&gt;
</description>
                <environment></environment>
        <key id="23099">INSTRM-1781</key>
            <summary>Punch list to start the engineering run in November 2022</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="-1">Unassigned</assignee>
                                    <reporter username="yuki.moritani">yuki.moritani</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Fri, 4 Nov 2022 17:17:10 +0000</created>
                <updated>Tue, 7 Feb 2023 22:35:34 +0000</updated>
                            <resolved>Wed, 30 Nov 2022 13:05:23 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="31738" author="rhl" created="Fri, 4 Nov 2022 20:51:18 +0000"  >&lt;p&gt;We need to add taking a full set of calibrations, reducing them, checking them, and ingesting them in the usual place&lt;/p&gt;</comment>
                            <comment id="31739" author="yuki.moritani" created="Fri, 4 Nov 2022 22:05:15 +0000"  >&lt;p&gt;Yes, but calibrations using pfilamp can be taken only after PFI is on the telescope. And we can take bias/dark before the run?&lt;/p&gt;

&lt;p&gt;I think my summary was confuging... this is the punch list mainly done &quot;before&quot; the run.&lt;/p&gt;</comment>
                            <comment id="31886" author="hassan" created="Wed, 30 Nov 2022 13:05:23 +0000"  >&lt;p&gt;Closing as November 2022 (Run 08) completed.&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|02qph7:03</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="162">2DDRP-2023 A</customfieldvalue>

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