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-184 DRP 2-D Pipeline <p>Upgrade our existing system to be based on the LSST version 13.0 release. This includes making sure all our code works and updating the docs at <a href="http://pfs-2d-pipeline.readthedocs.io/en/latest/" class="external-link" rel="nofollow">http://pfs-2d-pipeline.readthedocs.io/en/latest/</a>.</p> PIPE2D-184

Upgrade to hscPipe 5.0

Story Major Won't Fix Won't Fix cloomis swinbank Tue, 2 May 2017 19:14:54 +0000 Thu, 20 Jul 2017 02:30:03 +0000 Thu, 20 Jul 2017 02:30:03 +0000 0 3 <p>We may well want to move past v13_0, in particular to a pybind11-based release.</p> <p>Before this switch, we need to minimise the amount of C++ exposed to python! At present there are many functions that are either not used (especially instantiations), but also things written in C++ that could probably by python with no loss of speed (e.g. <tt>addFiberTraceToCcdArray</tt>)</p> <p>I thought we decided to modernize in two steps, using pybind11 as the start of the second? That said I was mostly interested in getting obs_pfs updated, which was trivial and does not depend on swig. </p> <blockquote> <p>I thought we decided to modernize in two steps...</p></blockquote> <p>I think Craig's recollection is correct — we agreed that moving to v13.0 was doable with minimal effort by Craig in the short term, while conversion to pybind11 would take more effort (and, as Robert and I discussed earlier, we'll likely call on Paul &amp; Pim to do the bulk of the work).</p> <p>I do think we should go to pybind11 as soon as we can reasonably schedule it, but I don't think that should stop Craig moving to 13.0 if he has time now.</p> <p>One question: is drp_stella's master well enough merged, or are there some larger active branches one I should wait for?</p> <p>After some discussion we decided to target hscPipe 5.0. 5.0 was branched off of LSST's w.2017.10 and was used for the HSC DR1 reductions. I believe the LSST 13.0 tag was applied to w.2017.6.</p> <p>hscPipe 5.0 is also before LSST's pybind11 work, so we are deferring that for now. As of this afternoon we intend to track the hscPipe development. The specific tag we are starting with is hscPipe 5.0 beta8</p> <p>The worst problem for me (and JHU and LAM) is the loss of the conda install.</p> <p>This turned out to be trivial, only requiring tiny renames for <tt>pex_logging</tt> -&gt; <tt>log</tt> and some minor work for <tt>daf_butlerUtils</tt> -&gt; <tt>obs_base</tt>.</p> <p>I think I should wait until any outstanding <tt>drp_stella</tt> ticket merges are done. </p> <p>Re conda:</p> <p>The conda stuff was really bad (a new EUPS_PATH for each upgrade). I believe that binary installs are now working, which should let you install into a pre-existing conda environment. Is that acceptable?</p> <p>Superseded by <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-220" title="Wrap using pybind11" class="issue-link" data-issue-key="PIPE2D-220"><del>PIPE2D-220</del></a> (go to LSST master)</p> Blocks PIPE2D-165 Development Rank 0|031vid:xi07fhk Sprint 2014-17 Story Points 4.0