<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:50:39 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>[PIPE2D-292] Strip down dependency tree</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-292</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;Our dependency tree could be stripped down, simplifying and speeding up the install.&lt;/p&gt;

&lt;p&gt;We can dump our dependency on obs_subaru by using the &lt;tt&gt;CrosstalkTask&lt;/tt&gt; in ip_isr.&lt;br/&gt;
We could remove our dependency on pipe_drivers and pipe_tasks by forking &lt;tt&gt;constructCalibs.py&lt;/tt&gt;, &lt;tt&gt;ingestImages.py&lt;/tt&gt; and &lt;tt&gt;ingestCalibs.py&lt;/tt&gt;.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12841">PIPE2D-292</key>
            <summary>Strip down dependency tree</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="price">price</assignee>
                                    <reporter username="price">price</reporter>
                        <labels>
                    </labels>
                <created>Tue, 25 Sep 2018 20:27:58 +0000</created>
                <updated>Tue, 18 Dec 2018 19:31:39 +0000</updated>
                            <resolved>Tue, 18 Dec 2018 19:31:39 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="14130" author="price" created="Wed, 3 Oct 2018 21:00:53 +0000"  >&lt;p&gt;We also need &lt;tt&gt;RepairTask&lt;/tt&gt; from pipe_tasks.&lt;/p&gt;</comment>
                            <comment id="14141" author="price" created="Fri, 5 Oct 2018 15:05:57 +0000"  >&lt;p&gt;OK, we needed a few other itty bitty files from pipe_tasks and pipe_drivers (a total of about 10 functional python files, plus some bin scripts), but I think it&apos;s quite manageable. I propose to call the new repo drp_lsst; it&apos;s currently on &lt;a href=&quot;https://github.com/PaulPrice/drp_lsst&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;my GitHub&lt;/a&gt; until we can create a place for it in the PFS GitHub.&lt;/p&gt;

&lt;p&gt;Because we no longer want to build all of LSST and we don&apos;t want to use the full LSST docker that&apos;s provided by LSST, I&apos;ve reworked the installation scripts. We now install just ip_isr, meas_algorithms and ctrl_pool as top-level products.&lt;/p&gt;

&lt;p&gt;I also took this opportunity to refactor the Dockerfiles. They have been in the top-level directory of pfs_pipe2d, mixed in with everything else, and it wasn&apos;t clear how to build them. I&apos;ve moved them into their own directory, added a &lt;tt&gt;Makefile&lt;/tt&gt;, and renamed them to be more consistent with their names as on DockerHub. There&apos;s a new &lt;tt&gt;pfs_lsst&lt;/tt&gt; image that will replace what we were using from LSST. The pfs_pipe2d image is now about 45% smaller than it used to be. The integration test in Travis is now run through the docker &lt;tt&gt;Makefile&lt;/tt&gt; (&lt;tt&gt;make test&lt;/tt&gt;), as that can both build the image and run the test.&lt;/p&gt;

&lt;p&gt;Unrelated, but because I was thinking about the reduction in time to run the integration test in Travis, I deleted the old sim data in drp_stella_data: it&apos;s no longer used now we have real data. However, I haven&apos;t seen a speedup in Travis because the integration test first clones the &lt;tt&gt;master&lt;/tt&gt; branch before checking out the ticket branch, which means it&apos;s still downloading everything until we merge the ticket branch.&lt;/p&gt;</comment>
                            <comment id="14142" author="rhl" created="Fri, 5 Oct 2018 15:25:54 +0000"  >&lt;p&gt;Please do not do this.&lt;/p&gt;

&lt;p&gt;We are going to want to move to PipelineTask and the new butler when they become available, so the dependency on pipe_tasks etc. must remain.&lt;/p&gt;

&lt;p&gt;We can remove things above the level we use, or packages that we never import even indirectly.&lt;/p&gt;</comment>
                            <comment id="14143" author="price" created="Sat, 6 Oct 2018 00:10:29 +0000"  >&lt;p&gt;OK, keeping pipe_tasks and pipe_drivers is not as efficient as the previous method for stripping the dependencies (76 packages instead of about 57, and 3.84 GB instead of 3.24 GB), but it does clean some things up. The changes to Docker stand.&lt;/p&gt;

&lt;p&gt;&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;, would you please review these changes?&lt;/p&gt;</comment>
                            <comment id="14720" author="price" created="Tue, 18 Dec 2018 19:31:39 +0000"  >&lt;p&gt;Merged to master.&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|s0014g:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Reviewers</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>cloomis</customfieldvalue>

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