Details

    • Sprint:
      DevOps Sprint 1, DevOps Sprint 2, DevOps Sprint 3
    • Team:
      SQuaRE

      Description

      Create a Confluence page with instructions for installing PhoSim for users of the LSST Stack. Note: there are two libraries (cfitsio and fftw3) in common with the Stack, which needs to be specified when installing PhoSim.

        Attachments

          Activity

          Hide
          shaw Richard Shaw [X] (Inactive) added a comment -

          Simon: you noted that the install process for PhoSim v3.4 changed a little, so I am attempting to up-rev. When running ./configure, the installer (still) claims the cfitsio and fftw3 dependencies. So I chose to provide the paths by hand (as in the past) and fill them in for these two packages.

          <gripe>Now I find that it also wants the path to nanoflann.hpp, and eigen, which were not mentioned in install instructions (neither https://confluence.lsstcorp.org/display/PHOSIM/Installation nor https://confluence.lsstcorp.org/display/PHOSIM/PhoSim+Walkthrough+and+Cookbook) or even in the first output line of the install script. Can you bug whoever and encourage them to update their docs when they update the software?</gripe>

          Show
          shaw Richard Shaw [X] (Inactive) added a comment - Simon: you noted that the install process for PhoSim v3.4 changed a little, so I am attempting to up-rev. When running ./configure, the installer (still) claims the cfitsio and fftw3 dependencies. So I chose to provide the paths by hand (as in the past) and fill them in for these two packages. <gripe>Now I find that it also wants the path to nanoflann.hpp, and eigen, which were not mentioned in install instructions (neither https://confluence.lsstcorp.org/display/PHOSIM/Installation nor https://confluence.lsstcorp.org/display/PHOSIM/PhoSim+Walkthrough+and+Cookbook ) or even in the first output line of the install script. Can you bug whoever and encourage them to update their docs when they update the software?</gripe>
          Hide
          shaw Richard Shaw [X] (Inactive) added a comment -

          Ok, I've implemented the following changes:
          1. Updated the install instructions for PhoSim v3.4, and tested.
          2. Included a link to the LSST Software Installation page.
          3. Clarified that the user needs git to download the packages, OR to setup the LSST environment (where git is available).
          4. Bash only applies to the "source loadLSST.sh" command. I could include alternatives for other shells, but they don't always work as well. There is a JIRA issue for this.
          5. While the SED library can be got with eups, one would have to alter the installation of PhoSim (create a symlink) to use it. Seems like downloading the directory to the phosim/data subdirectory is just as easy. Perhaps when phosim is more directly integrated with eups this will be less cumbersome.
          6. Added an Info block to direct the reader to the PhoSim tutorial or the "Using PhoSim" project page.

          Show
          shaw Richard Shaw [X] (Inactive) added a comment - Ok, I've implemented the following changes: 1. Updated the install instructions for PhoSim v3.4, and tested. 2. Included a link to the LSST Software Installation page. 3. Clarified that the user needs git to download the packages, OR to setup the LSST environment (where git is available). 4. Bash only applies to the "source loadLSST.sh" command. I could include alternatives for other shells, but they don't always work as well. There is a JIRA issue for this. 5. While the SED library can be got with eups, one would have to alter the installation of PhoSim (create a symlink) to use it. Seems like downloading the directory to the phosim/data subdirectory is just as easy. Perhaps when phosim is more directly integrated with eups this will be less cumbersome. 6. Added an Info block to direct the reader to the PhoSim tutorial or the "Using PhoSim" project page.
          Hide
          krughoff Simon Krughoff added a comment -

          I should have mentioned this earlier, but v3.4 is not the official release yet. John has not given an ETA, but hopefully the documentation will be updated at the same time.

          Show
          krughoff Simon Krughoff added a comment - I should have mentioned this earlier, but v3.4 is not the official release yet. John has not given an ETA, but hopefully the documentation will be updated at the same time.
          Hide
          shaw Richard Shaw [X] (Inactive) added a comment -

          It's odd that v3.4 is not considered "official"; it's what users will get when the git clone from master, no?

          Show
          shaw Richard Shaw [X] (Inactive) added a comment - It's odd that v3.4 is not considered "official"; it's what users will get when the git clone from master, no?
          Hide
          krughoff Simon Krughoff added a comment -

          Official != master. Master should be considered the bleeding edge. Tags should be considered stable, and it just so happens there have been no commits to master since v3.4 has been tagged. As for which version is considered "official," that depends on whether the docs have been updated and whether the calibration products exist.

          Show
          krughoff Simon Krughoff added a comment - Official != master. Master should be considered the bleeding edge. Tags should be considered stable, and it just so happens there have been no commits to master since v3.4 has been tagged. As for which version is considered "official," that depends on whether the docs have been updated and whether the calibration products exist.

            People

            • Assignee:
              shaw Richard Shaw [X] (Inactive)
              Reporter:
              shaw Richard Shaw [X] (Inactive)
              Reviewers:
              Simon Krughoff
              Watchers:
              Mario Juric, Richard Shaw [X] (Inactive), Simon Krughoff
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel