Spatial Modeling for Resources Framework

Spatial Modeling for Resources Framework (SMRF) was developed by Dr. Scott Havens at the USDA Agricultural Research Service (ARS) in Boise, ID. SMRF was designed to increase the flexibility of taking measured weather data and distributing the point measurements across a watershed. SMRF was developed to be used as an operational or research framework, where ease of use, efficiency, and ability to run in near real time are high priorities.

Read the full documentation for SMRF including up to date installation instructions.

• Spatial Modeling for Resources Framework
  • Which version to use?
    • Stable
    • Experimental
  • Installation
    • System dependencies
  • Topo setup
  • Input data
  • Running SMRF
  • Docker
  • Development
    • Tests

Which version to use?

Stable

The stable version of SMRF is currently v0.9. The code can be downloaded from the releases or can be found on the release-0.9 branch.

Best for:

• Applying the model in near real time
• Researchers wanting a ready to use model
• Those wanting the most stable and tested code

Experimental

:warning: Use at your own risk! While this contains the latest code, it is not guaranteed to work with the whole modeling framework.

The latest code on master contains all the latest development to SMRF. However, this must be used with caution as it can be under active development, may change at any time and is not guaranteed to work with the rest of the modeling framework at that moment. Once the code has been fully tested within the modeling framework, a new release will be created to signal a move to a stable version.

Best for:

• Those planning on developing with SMRF
• Model simulations require features only found in the latest code
• Okay with the possibility that SMRF doesn't work with the rest of the modeling system

Installation

python3 -m pip install smrf-dev

To install SMRF locally on Linux of MacOSX, first clone the repository and build into a virtual environment. This requires gcc <= 9.0. The general steps are as follows and will test the SMRF installation by running the tests.

Clone from the repository

git clone https://github.com/USDA-ARS-NWRC/smrf.git

And install the requirements, SMRF and run the tests.

python3 -m pip install -r requirements_dev.txt .[tests]
python3 setup.py install

To optionally verify the installation, run the unit tests

python3 -m unittest -v

For Windows, the install method is using Docker.

System dependencies

If using SMRF with gridded weather data from GRIB files, you will need the system dependancy for eccodes which is a GRIB file reader.

Topo setup

The topo provides SMRF with the following static layers:

1. Digital elevation model
2. Vegetation type
3. Vegetation height
4. Vegetation extinction coefficient
5. Vegetation optical transmissivity
6. Basin mask (optional)

All these layers are stored in a netCDF file, typically referred to the topo.nc file.

While the topo.nc file can be generated manually, a great option is to use basin_setup which creates a topo file that is compatible with SMRF and AWSM.

Input data

Input meterological data for SMRF requires the following variables:

• Air temperature
• Vapor pressure
• Precipitation
• Wind speed and direction
• Cloud factor (percentage between 0 and 1 of incoming solar obstructed by clouds)

The data can be supplied through the following formats:

• CSV files
• Weather Research and Forecasting (WRF) outputs
• High Resolution Rapid Refresh (HRRR)
• Generic netCDF

Running SMRF

There are two ways to run SMRF, first is through the run_smrf command or through the SMRF API. If SMRF is being used as input to a snow or hydrology model, we recommend to use run_smrf as it will generate all the input required. See the full documentation for more details.

run_smrf <config_file>

Docker

SMRF is also built into a docker image to make it easy to install on any operating system. The docker images are built automatically from the Github repository and include the latest code base or stable release images.

The SMRF docker image has a folder meant to mount data inside the docker image at /data.

docker run -v <path to data>:/data usdaarsnwrc/smrf run_smrf <path to config>

The <path to data> should be the path to where the configuration file, data and topo are on the host machine. This will also be the location to where the SMRF output will go.

NOTE: The paths in the configuration file must be adjusted for being inside the docker image. For example, in the command above the path to the config will be inside the docker image. This would be /data/config.ini and not the path on the host machine.

In a way that ARS uses this, we keep the config, topo and data on one location as the files are fairly small. The output then is put in another location as it file size can be much larger. To facilitate this, mount the input and output data separately and modify the configuration paths.

docker run -v <input>:/data/input -v <output>:/data/output usdaarsnwrc/smrf run_smrf <path to config>

Development

Tests

SMRF relies on class level and integration type testing. On the class level, tests cover expected structure and ensure proper attribute types. Example: tests/data/test_gridded_input.py

The integration tests ensure that changes to the code base do not trigger unexpected changes to the model output. Example: tests/test_full_smrf.py

All required data for integration tests is stored under: tests/basins/ with two sample areas.