Skip to main content

Docs Tests Linter PythonV Pypi Codecov Zenodo Binder


reV (the Renewable Energy Potential model) is an open-source geospatial techno-economic tool that estimates renewable energy technical potential (capacity and generation), system cost, and supply curves for solar photovoltaics (PV), concentrating solar power (CSP), geothermal, and wind energy. reV allows researchers to include exhaustive spatial representation of the built and natural environment into the generation and cost estimates that it computes.

reV is highly dynamic, allowing analysts to assess potential at varying levels of detail — from a single site up to an entire continent at temporal resolutions ranging from five minutes to hourly, spanning a single year or multiple decades. The reV model can (and has been used to) provide broad coverage across large spatial extents, including North America, South and Central Asia, the Middle East, South America, and South Africa to inform national and international-scale analyses. Still, reV is equally well-suited for regional infrastructure and deployment planning and analysis.

For a detailed description of reV capabilities and functionality, see the NREL reV technical report.

How does reV work?

reV is a set of Python classes and functions that can be executed on HPC systems using CLI commands. A full reV execution consists of one or more compute modules (each consisting of their own Python class/CLI command) strung together using a pipeline framework, or configured using batch.

A typical reV workflow begins with input wind/solar/geothermal resource data (following the rex data format) that is passed through the generation module. This output is then collected across space and time (if executed on the HPC), before being sent off to be aggregated under user-specified land exclusion scenarios. Exclusion data is typically provided via a collection of high-resolution spatial data layers stored in an HDF5 file. This file must be readable by reV’s ExclusionLayers class. See the reVX Setbacks utility for instructions on generating setback exclusions for use in reV. Next, transmission costs are computed for each aggregated “supply-curve point” using user-provided transmission cost tables. See the reVX transmission cost calculator utility for instructions on generating transmission cost tables. Finally, the supply curves and initial generation data can be used to extract representative generation profiles for each supply curve point.


To get up and running with reV, first head over to the installation page, then check out some of the Examples or go straight to the CLI Documentation! You can also check out the guide on running GAPs models.

Installing reV

NOTE: The installation instruction below assume that you have python installed on your machine and are using conda as your package/environment manager.

Option 1: Install from PIP (recommended for analysts):

  1. Create a new environment:

    conda create --name rev python=3.11

  2. Activate directory:

    conda activate rev

  3. Install reV:
    1. pip install NREL-reV or

      • NOTE: If you install using conda and want to use HSDS you will also need to install HSDS dependencies: pip install NREL-reV[hsds]

Option 2: Clone repo (recommended for developers)

  1. from home dir, git clone git@github.com:NREL/reV.git

  2. Create reV environment and install package
    1. Create a conda env: conda create -n rev

    2. Run the command: conda activate rev

    3. cd into the repo cloned in 1.

    4. prior to running pip below, make sure the branch is correct (install from main!)

    5. Install reV and its dependencies by running: pip install . (or pip install -e . if running a dev branch or working on the source code)

  3. Check that reV was installed successfully
    1. From any directory, run the following commands. This should return the help pages for the CLI’s.

      • reV

reV command line tools

Launching a run

Tips

reV pipeline -c "/scratch/user/rev/config_pipeline.json"
  • Running simply generation or econ can just be done from the console:

reV generation -c "/scratch/user/rev/config_gen.json"

General Run times and Node configuration on Eagle

  • WTK Conus: 10-20 nodes per year walltime 1-4 hours

  • NSRDB Conus: 5 nodes walltime 2 hours

Eagle node requests

Metadata

Release files for NREL-reV 0.14.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for NREL-reV 0.14.5
File Size Uploaded
nrel_rev-0.14.5.tar.gz 906.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for NREL-reV 0.14.5
File Interpreter ABI Platform
nrel_rev-0.14.5-py3-none-any.whl Python 3 none any Details

Total release size: 1.9 MB

Release files / nrel_rev-0.14.5.tar.gz

Download URL nrel_rev-0.14.5.tar.gz
Size 906.3 kB
Tags Source
SHA-256 checksum
How to use checksums
292d66249f54a3ce0581d9b667f8c4256c938930e699187924ee78f2d5126c19
BLAKE2b-256 checksum
How to use checksums
d4fbef4b21cb37ff83138a2f98d2fe8979a6eeec6faec530b0f1d2d0f5d61f1f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2025.

Transparency log

Release files / nrel_rev-0.14.5-py3-none-any.whl

Download URL nrel_rev-0.14.5-py3-none-any.whl
Size 946.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a1b0406b218cf29faf1add553ea3846bf32a0dcbfd8dfacf747ba2b99fe7dfec
BLAKE2b-256 checksum
How to use checksums
2f522cacd3e8ee4793d1cfce1d7f735843d958f37c5d4f27b3e769eb966ab5f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.14.5 This release

2 release files

0.14.4

2 release files

0.14.2

2 release files

0.14.1

2 release files

0.13.1

2 release files

0.13.0

2 release files

0.9.7

2 release files

0.9.6

2 release files

0.9.5

2 release files

0.9.4

2 release files

0.9.2

2 release files

0.9.0

2 release files

0.8.9

2 release files

0.8.7

2 release files

0.8.6

2 release files

0.8.5

2 release files

0.8.4

2 release files

0.8.3

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.3

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.6

2 release files

0.6.5

2 release files

0.6.4

2 release files

0.6.3

2 release files

0.6.2

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.5.14

2 release files

0.5.13

2 release files

0.5.12

2 release files

0.5.10

2 release files

0.5.9

2 release files

0.5.8

2 release files

0.5.7

2 release files

0.5.6

2 release files

0.5.5

2 release files

0.5.4

2 release files

0.5.3

2 release files

0.5.2

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.55

2 release files

0.4.54

2 release files

0.4.53

2 release files

0.4.51

2 release files

0.4.50

2 release files

0.4.49

2 release files

0.4.48

2 release files

0.4.47

2 release files

0.4.44

2 release files

0.4.43

2 release files

0.4.42

2 release files

0.4.38

2 release files

0.4.36

2 release files

0.4.35

2 release files

0.4.34

2 release files

0.4.33

2 release files

0.4.32

2 release files

0.4.31

2 release files

0.4.29

2 release files

0.4.28

2 release files

0.4.27

2 release files

0.4.26

2 release files

0.4.25

2 release files

0.4.23

2 release files

0.4.21

2 release files

0.4.20

2 release files

0.4.19

2 release files

0.4.15

2 release files

0.4.14

2 release files

0.4.13

2 release files

0.4.12

2 release files

0.4.11

2 release files

0.4.9

2 release files

0.4.8

2 release files

0.4.7

2 release files

0.4.6

2 release files

0.4.5

2 release files

0.4.4

2 release files

0.4.3

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page