Distributed Wind Generation Model (dWind)
Please note that at this time the model can only be run on NatLabRockies's Kestrel HPC system.
Though a savvy user could recreate our data in their own computing environment and update the
internal pointers in the example configuration at examples/larimer_county_btm_baseline_2025.toml
and examples/model_config.toml.
Installing dwind
-
Install Anaconda or Miniconda (recommended) if not already installed.
-
Clone the repository
git clone https://github.com/NatLabRockies/dwind.git
-
Navigate to the dwind repository.
cd /path/to/dwind
-
Create your dwind environment using our recommended settings and all required dependencies.
conda env create -f environment.yml
Running
Configuring
dWind relies on 2 configuration files: 1) a system-wise setting that can be shared among a team,
and 2) a run-specific configuration file. Both will be described below.
Primary model configuration
The primary model configuration should look exactly like (or be compatible with)
examples/model_config.toml to ensure varying fields are read correctly throughout the model.
Internally, dWind is able to convert the following data to adhere to internal usage:
- Any field with "DIR" is converted to a Python
pathlib.Pathobject for robust file handling - SQL credentials and constructor strings are automatically formed in the
[sql]table for easier construction of generic connection strings. Specifically the{USER}and{PASSWORD}fields get replaced with their corresponding setting in the same table.
Configuration, the primary class handling this data allows for dot notation and dictionary-style
attribute calling at all levels of nesting. This means, config.pysam.outputs.btm and
config.pysam.outputs["btm"] are equivalent. This makes for more intuitive dynamic attribute
fetching when updating the code for varying cases.
Run configuration
The run-specific configuration should look like examples/larimer_county_btm_baseline_2025.toml,
which controls all the dynamic model settings, HPC configurations, and a pointer to the primary
model configuration described above.
Run the model
dwind has a robust CLI interface allowing for the usage of python path/to/dwind/dwind/main.py or
by directly callingdwind. For more details on using the CLI, use the --help flag, or visit our
CLI documentation page https://natlabrockies.github.io/dwind/cli.html
To run the model, it is recommended to use the following workflow from your analysis folder.
-
Start a new
screensession on Kestrel.screen -S <analysis-name>
-
Load your conda environment with dwind installed.
module load conda conda activate <env_name>
-
Navigate to your analysis folder if your relative data locations in your run configuration are relative to the analysis folder.
cd /path/to/analysis/location
-
Run the model.
dwind run config examples/larimer_county_btm_baseline_2025.toml
-
Disconnect your screen
Ctrl+a+dand wait for the analysis to complete and view your results.
Metadata
Release files for dwind 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dwind-0.5.tar.gz | 2.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dwind-0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 MB
Release files / dwind-0.5.tar.gz
| Download URL | dwind-0.5.tar.gz |
|---|---|
| Size | 2.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71334419a4b14782804bbdacfbabbcedaca878be027423bbb432d5c21223e2c0
|
|
BLAKE2b-256 checksum How to use checksums |
ed28049b66feb77f8470c7e50e91a13866c33ff2335431efaaee25b4cd01cb75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 4, 2026.
Transparency logRelease files / dwind-0.5-py3-none-any.whl
| Download URL | dwind-0.5-py3-none-any.whl |
|---|---|
| Size | 51.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
545f2d725cc58edd56fffaab07c307f678df5ef1396f6d3f65643d97217eee7d
|
|
BLAKE2b-256 checksum How to use checksums |
fa1169e17abdc6d943992ad218e42b5770b76ff724ee4ff8fca232904c325466
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 4, 2026.
Transparency log