Skip to content

Latest commit

 

History

History
193 lines (131 loc) · 9.6 KB

SOFTWARE.md

File metadata and controls

193 lines (131 loc) · 9.6 KB
Raw

Software Installation

Table of Contents generated with DocToc

To get the most out of this class, you will need to come prepared with a laptop computer that has Python installed. If you have the conda- or mamba-based python distribution installed (conda, mini), are familiar with conda environments, and know how to create a new conda environment using an environment.yml file, then skip ahead to Part 2. For all others, we recommend using the Miniforge python distribution. You should be able to install Miniforge without elevated privileges but if you have your IT staff install the software make sure they do not install for all users.

Installation

The following instructions will guide you through the installation process and setup of a conda environment for the class.

1. Install Miniforge

  1. Go to the miniforge website and download the installer (https://github.com/conda-forge/miniforge) for your platform. If you have trouble downloading Miniforge in Microsoft Edge try another browser (for example, Chrome).

  2. Run the installer program that you downloaded. On Windows the installer is called Miniforge3-Windows-x86_64.exe.

  3. Click through the installer options, and select "Just Me (recommended)" if asked. Default installation options should be fine, with the exception that you should select an installation location that does not have any special characters or spaces in it.

  4. After installation, you should see "Miniforge Prompt" as a program under the Windows Start menu.

2. Create an Environment File

We will use an environment file to create a containerized version of Python and the Python packages needed for the class. An environment file is simply a list of packages that we want to install in our environment.

  1. Using a text editor, such as Notepad or Notepad++, create a file called environment.yml. It should contain the information in this environment file. Save this file to your hard drive, preferably in your user home folder so that it can be easily accessed in the next step. (Caution! Notepad will automatically append a .txt suffix to your file name; you don't want this to happen.)

    Alternatively, clone this repository and use environment.yml directly.

  2. For MacOS and Linux users only! You will need to add seven additional dependencies to the environment.yml file from step 1. The following dependencies are also required:

    MacOS

    - pkg-config
- openmpi<5.0.0
- gfortran
- petsc
- netcdf-fortran
- meson>=1.1.0
- ninja

    Linux

    - pkg-config
- openmpi
- gfortran
- petsc
- netcdf-fortran
- meson>=1.1.0
- ninja

3. Create the gw3099 Environment

  1. Start the miniforge prompt from the Windows start menu (or equivalent on MacOS or Linux) to bring up a terminal.

  2. At the terminal prompt enter the following command, where <path to file> is the location of the environment.yml file that you created in Part 2. You will need to be connected to the internet for this to work properly. The installation process may take a couple of minutes.

    mamba env create --file <path to file>/environment.yml

    If you installed the class environment in an existing python distribution, you will need to use the conda command if mamba is not installed.

  3. After the environment has been installed, you may activate this new class environment with the following command

    mamba activate gw3099

  4. The windows terminal prompt should reflect the current environment:

    (gw3099) C:\Users\JaneDoe>

  5. We will be using jupyter notebooks in the class. To test if jupyter is installed and working properly use the following command. After entering this command, the default web browswer should open to a Jupyter Lab page.

    jupyter lab

For most users, the setup is complete at this point. For those working on a MacOS or Linux laptop, please proceed to Part 4.

4. Create the gw3099pws environment

On Thursday morning the pywatershed package will be covered. Currently, pywatershed requires a separate environment because it is not yet caught up with numpy 2.0.0+. Here we install the environment to run the pywatershed examples.

  1. Using a text editor, such as Notepad or Notepad++, create a file called environment-pywatershed.yml. It should contain the information in this environment file. Save this file to your hard drive, preferably in your user home folder so that it can be easily accessed in the next step. (Caution! Notepad will automatically append a .txt suffix to your file name; you don't want this to happen.)

  2. Start the miniforge prompt from the Windows start menu (or equivalent on MacOS or Linux) to bring up a terminal or if you already have a miniforge prompt running make sure you are in the base environment.

    (base) C:\Users\JaneDoe>

    If you are not in the base environment you can switch using the command

    mamba deactivate

  3. At the terminal prompt enter the following command, where <path to file> is the location of the environment-pywatershed.yml file that you created in Part 2. You will need to be connected to the internet for this to work properly. The installation process may take a couple of minutes.

    mamba env create --file <path to file>/environment-pywatershed.yml

  4. After the environment has been installed, you may activate this new class environment with the following command

    mamba activate gw3099pws

  5. The windows terminal prompt should reflect the current environment:

    (gw3099pws) C:\Users\JaneDoe>

Part 5. Create the gw3099viz environment (OPTIONAL)

On Friday there will be an Advanced Visualization session that will cover use of Paraview, QGIS, Panolopy, and PyVista. Paraview, QGIS, and Panaolopy are not included in the gw3099 class environment. If you would like to run these programs on your laptop you will have to install an additional environment.

  1. Using a text editor, such as Notepad or Notepad++, create a file called environment-viz.yml. It should contain the information in this environment file. Save this file to your hard drive, preferably in your user home folder so that it can be easily accessed in the next step. (Caution! Notepad will automatically append a .txt suffix to your file name; you don't want this to happen.)

  2. Start the miniforge prompt from the Windows start menu (or equivalent on MacOS or Linux) to bring up a terminal or if you already have a miniforge prompt running make sure you are in the base environment.

    (base) C:\Users\JaneDoe>

    If you are not in the base environment you can switch using the command

    mamba deactivate

  3. At the terminal prompt enter the following command, where <path to file> is the location of the environment-viz.yml file that you created in Part 2. You will need to be connected to the internet for this to work properly. The installation process may take a couple of minutes.

    mamba env create --file <path to file>/environment-viz.yml

  4. After the environment has been installed, you may activate this new class environment with the following command

    mamba activate gw3099viz

  5. The windows terminal prompt should reflect the current environment:

    (gw3099viz) C:\Users\JaneDoe>

6. Obtaining MODFLOW 6

=======

We will be using the parallel version of MODFLOW 6 in this class. If you are working on Windows, we will be using the latest nightly-build of the extended version of MODFLOW 6 in the class. We will also walk through this step during the class. The distribution file for Windows that includes the extended version is called win64ext.zip.

If you are using a MacOS or Linux laptop for the class, then you will need to build the extended version of MODFLOW. We have simplified the build process, which can be completed in just a few minutes. Instructions for building the extended version of MODFLOW 6 are located here.

Preparation for the Class

If you have never used Python before, there are many online resources for getting started. A recommendation is to start with the tutorial at https://cscircles.cemc.uwaterloo.ca/.

Troubleshooting

Codesigning

M1 Mac users may see executables hang or crash due to codesigning enforcement. This can be remedied with:

codesign --force --sign - /path/to/program

Other issues

If encountering another issue with software installation, contact jdhughes@usgs.gov.