Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-9591

Python 3 Conda binaries fail lsst_dm_stack_demo on Ubuntu 16.04

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      To reproduce login to https://jupyter-jmatt.lsst.codes using your GitHub credentials.

      Start the bash or terminal app using the drop down.

      setup obs_sdss
      source '/opt/conda/bin/eups-setups.sh'
      cd ./lsst_dm_stack_demo
      setup obs_sdss
      ./bin/demo.sh
      cat ./detected-sources.txt | sed -E -e 's/(True|False)/-/' > ./detected-sources-fixed.txt
      ./bin/compare ./detected-sources.txt
      cp ./detected-sources-fixed.txt ./detected-sources.txt
      ./bin/compare ./detected-sources.txt
      

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            Try commit 3cc7631 in lsst_dm_stack_demo.

            Show
            tjenness Tim Jenness added a comment - Try commit 3cc7631 in lsst_dm_stack_demo.
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            My best guess is it is due to conda-lsst's slightly older range limits on numpy (or similar). That is something I could test, but it requires rebuilding the conda binaries. So it'll take the rest of the night.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - My best guess is it is due to conda-lsst 's slightly older range limits on numpy (or similar). That is something I could test, but it requires rebuilding the conda binaries. So it'll take the rest of the night.
            Hide
            tjenness Tim Jenness added a comment -

            No. It's most definitely DM-903. If you use the commit I mentioned in the demo it will work fine. We are meant to put a tag on the demo to match the associated release. I assume DM-903 was merged after Frossie Economou created the release.

            Show
            tjenness Tim Jenness added a comment - No. It's most definitely DM-903 . If you use the commit I mentioned in the demo it will work fine. We are meant to put a tag on the demo to match the associated release. I assume DM-903 was merged after Frossie Economou created the release.
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            Excellent, checking out 3cc7631 works.

            So it looks like it's DM-903 or similar.

            Thanks Tim.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - Excellent, checking out 3cc7631 works. So it looks like it's DM-903 or similar. Thanks Tim.
            Hide
            frossie Frossie Economou added a comment -

            I have made the 13.0 release of lsst_dm_stack_demo off this commit:

            https://github.com/lsst/lsst_dm_stack_demo/commit/3cc7631b5c3d7d1bc6aace87ea3822f0736bc2ea

            jmatt, please confirm it works for your binaries. I have tested it with the candidate source build on OSX and it seems fine.

            Show
            frossie Frossie Economou added a comment - I have made the 13.0 release of lsst_dm_stack_demo off this commit: https://github.com/lsst/lsst_dm_stack_demo/commit/3cc7631b5c3d7d1bc6aace87ea3822f0736bc2ea jmatt, please confirm it works for your binaries. I have tested it with the candidate source build on OSX and it seems fine.

              People

              Assignee:
              frossie Frossie Economou
              Reporter:
              jmatt J Matt Peterson [X] (Inactive)
              Reviewers:
              J Matt Peterson [X] (Inactive)
              Watchers:
              Frossie Economou, J Matt Peterson [X] (Inactive), Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.