https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/PIPE2D-36 DRP 2-D Pipeline <p>As per discussion with Robert and John it is fine for now to install drp_stella, drp_stella_data, and obs_pfs from github, but in the near future we would want the installation be possible via eups distrib install.</p> <p>Note that this doesn't preclude pulling some packages from git, the two systems work well together. We should expect to have a complete copy of the PFS code installed at all major sites and usable by people <b>without</b> having to do an install; <tt>eups distrib install</tt> provides a way to install updated components into this central copy. Because the PFS dependencies are simple, this is really pretty easy to do (the base LSST stack can be transparently installed as part of this operation).</p> PIPE2D-36

make PFS pipeline installable with eups distrib install

Story Major Done Done price aritter Fri, 8 Jul 2016 18:19:35 +0000 Fri, 5 Apr 2019 16:37:18 +0000 Wed, 6 Mar 2019 19:56:29 +0000 6.0 0 5 <p>A separate ticket needs to be created for binary distributions to be done.</p> <p>In particular, using a binary installer. We can base this on the LSST one, and just add a few packages of our own.</p> <p>Having installed the pipeline under eups, and with <tt>EUPS_PKGROOT</tt> pointing to the LSST distro (<tt><a href="https://eups.lsst.codes/stack/redhat/el7/devtoolset-6/miniconda3-4.3.21-10a4fa6" class="external-link" rel="nofollow">https://eups.lsst.codes/stack/redhat/el7/devtoolset-6/miniconda3-4.3.21-10a4fa6</a>|https://eups.lsst.codes/stack/src</tt>), this is a simple matter of:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> pfs@6a5b860c4e22:~ $ eups distrib create --server-dir ~/pfs/eups-server -d tarball pfs_pipe2d 5.0 </pre> </div></div> <p>I've now added an OSX version as well as the Linux version I created above.</p> <p>You should be able to do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> EUPS_PKGROOT=<span class="code-quote">"${EUPS_PKGROOT}|http:<span class="code-comment">//tigress-web.princeton.edu/~pprice/pfs-drp-2d"</span> </span>eups distrib install pfs_pipe2d 5.0 </pre> </div></div> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl" class="user-hover" rel="rhl">rhl</a>, could you please give this a try?</p> <p>I tested <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price" class="user-hover" rel="price">price</a>'s suggestion above on my own laptop and ran the <tt>pfs_integration_test.sh</tt> with success. </p> <p>Note however I needed to run the shebangtron (<a href="https://github.com/lsst/shebangtron" class="external-link" rel="nofollow">https://github.com/lsst/shebangtron</a>) prior to running the integration test.</p> <p>If we use the latest version of eups (maybe master – but we can tag) this can be done automatically.  We should do this</p> <p>We're using the <tt>newinstall.sh</tt> that comes with LSST <tt>v16&#95;0</tt>. Does that let us choose to use the latest eups version, or does it stick us with whatever was being used back then?</p> <p>I think we replace newinstall.  It does very little after installing eups and it needs to set EUPS_PKGROOT which we can do by hand.  I can take another look, but I think it's a massively complicates solution to a simple problem.</p> <p>It may well be, but it's one I don't have to write, maintain or document.</p> <p>The fix Paul described in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-36?focusedCommentId=14827&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14827" class="external-link" rel="nofollow">https://pfspipe.ipmu.jp/jira/browse/PIPE2D-36?focusedCommentId=14827&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14827</a></p> <p>with the additional need to run the shebangtron, works as expected.</p> <p>Consider this issue to be resolved based on those points. Additional changes can be raised as separate issues.</p> Relates PIPE2D-397 Development Rank 0|02qpt6:49 Sprint 2019 B Story Points 4.0