Setting Environment Variables

Setting Environment Variables#

H2Integrate can pull weather resource datasets (e.g. data needed for wind or solar generation) automatically for a user-provided location. To use resource datasets from the NREL developer network, you will need an NREL API key, which can be obtained from: https://developer.nrel.gov/signup/.

You will need to set the API key and the email you used to get the API key for downloading resource data from the NREL developer network. The 40 character API key is referred to in following sections as the value for the NREL_API_KEY environment variable. The email used to get the API key is referred to in the following sections as the value for the NREL_API_EMAIL environment variable.

In the following sections on setting these environment variables, 'api-key-value' should be replaced with your NREL API key and 'email-for-api-key' should be replaced with your email address.

An optional environment variable is RESOURCE_DIR. If set, this will be used as the default folder to save resource data to that is downloaded from the API. If setting this, please set its value as the full filepath to the folder you'd like to save resource files to, and ensure that the folder exists.

The remaining sections outline different options for setting environment variables in H2Integrate:

Save Environment Variables with Conda (Preferred)#

After creating the conda environment for H2Integrate, you can save environment variables with conda within that environment. This is the preferred method for setting environment variables for H2Integrate.

Windows Instructions#

If you are using a Windows machine, please follow the steps documented for conda on saving environment variables on Windows. The specific variable names and values to set are listed below; use these for steps 3 and 4 from the conda installation instructions..

The .\etc\conda\activate.d\env_vars.bat file may look like below:

set NREL_API_KEY='api-key-value'
set NREL_API_EMAIL='email-for-api-key'
set RESOURCE_DIR=C:\path\to\my\resource\folder

The .\etc\conda\deactivate.d\env_vars.bat file may look like below:

set NREL_API_KEY=
set NREL_API_EMAIL=
set RESOURCE_DIR=

macOS and Linux instructions#

If you are using a macOS or Linux machine, please follow the steps documented for conda on saving environment variables on macOS or Linux

The ./etc/conda/activate.d/env_vars.sh file may look like below:

#!/bin/sh
export NREL_API_KEY='api-key-value'
export NREL_API_EMAIL='email-for-api-key'
export RESOURCE_DIR=/path/to/my/resource/folder/

The ./etc/conda/deactivate.d/env_vars.sh file may look like below:

#!/bin/sh

unset NREL_API_KEY
unset NREL_API_EMAIL
unset RESOURCE_DIR

Set Environment Variables with .yaml file#

  1. In environment.yml, add the following lines to the bottom of the file, and replace the environment variable values with your information. Be sure that "variables" has no leading spaces.

    variables:
    NREL_API_KEY='api-key-value'
    NREL_API_EMAIL='email-for-api-key'
    RESOURCE_DIR='/path/to/my/resource/folder/'

  2. After that, create a conda environment and install H2Integrate and all its dependencies using the modified environment.yml file with the command:

    conda env create -f environment.yml

Set Environment Variables with .env file#

Note

This method only works for setting the NREL_API_KEY and NREL_API_EMAIL environment variables; this method should not be used to set the RESOURCE_DIR environment variable.

The ".env" file will be looked for in all of the following locations: - H2Integrate root directory (/path/to/H2Integrate/h2integrate/) - parent of H2Integrate root directory (/path/to/H2Integrate/) (preferred location to store your environment file) - current working directory (this is not a preferred location to store your environment file)

  1. Choose which of the above directories you want to host your .env file, and create a file named ".env" in that folder.

  2. Open the ".env" file and add the environment variables:

    NREL_API_KEY='api-key-value'
NREL_API_EMAIL='email-for-api-key'

  3. Save and close the ".env" file.

Contents