Skip to main content

wind-up

A Python package for assessing wind turbine yield uplift from operational data.

PyPI version License Python versions Lint & Format: Ruff Typing: mypy Lint and test

wind-up compares turbine performance before and after a change to estimate energy-yield uplift. It is designed for wind-farm SCADA analysis where the signal of interest is small, operational data is messy, and a credible result needs more than a simple before/after power-curve plot.

The package is published on PyPI as res-wind-up and imported in Python as wind_up.

What it does

wind-up provides a complete analysis workflow for pre/post or toggle-style uplift assessments:

  • prepares and filters wind-farm SCADA data
  • builds SCADA-derived power curves by turbine type
  • adds reanalysis, mast, or LiDAR reference data
  • applies yaw direction northing corrections
  • estimates wind speed and waking state
  • detrends test turbine performance against reference wind direction
  • performs pre/post power performance analysis with reversal checks and bootstrapped uncertainty
  • combines per-reference results into turbine-level and fleet-level uplift estimates
  • writes result tables and diagnostic plots for review

The public examples cover several realistic analysis shapes, including SMARTEOLE toggle data, Kelmarsh turbine data, and WeDoWind challenge-style pre/post assessments.

Further example useage can be seen in the Hill of Towie open analysis repo.

Methodology

The validation methodology that wind-up implements is described in detail in wind-up uplift validation methodology v3 in the docs folder.

Installation

Install the released package with your Python environment manager of choice. Python 3.10 to 3.13 is supported.

Using uv:

uv add res-wind-up

Using pip:

python -m venv .venv
source .venv/bin/activate
pip install res-wind-up

On Windows PowerShell, activate the virtual environment with:

.venv\Scripts\Activate.ps1

To run the bundled notebooks and example scripts, install the optional example dependencies as well:

uv add "res-wind-up[examples]"
# or
pip install "res-wind-up[examples]"

Check that the package imports correctly:

import wind_up

print(wind_up.__version__)

First steps

The fastest way to understand the expected data model and analysis flow is to start from the examples:

A typical analysis has four stages:

from wind_up.interface import AssessmentInputs
from wind_up.main_analysis import run_wind_up_analysis
from wind_up.models import PlotConfig, WindUpConfig
from wind_up.reanalysis_data import ReanalysisDataset

# 1. Build a WindUpConfig describing the asset, test turbines,
#    reference turbines, analysis dates, filters, and output folder.
cfg = WindUpConfig(...)

# 2. Configure diagnostic plot output.
plot_cfg = PlotConfig(
    show_plots=False,
    save_plots=True,
    plots_dir=cfg.out_dir / "plots",
)

# 3. Prepare inputs from SCADA, metadata, and reference datasets.
assessment_inputs = AssessmentInputs.from_cfg(
    cfg=cfg,
    plot_cfg=plot_cfg,
    scada_df=scada_df,
    metadata_df=metadata_df,
    reanalysis_datasets=[ReanalysisDataset(id="ERA5", data=reanalysis_df)],
    cache_dir=cache_dir,
)

# 4. Run the assessment and save the per-test/per-reference results.
results_per_test_ref_df = run_wind_up_analysis(assessment_inputs)
results_per_test_ref_df.to_csv(cfg.out_dir / "results_per_test_ref.csv", index=False)

For complete, executable versions of this pattern, use the example files above. The configuration is intentionally explicit: wind-resource assessments are sensitive to turbine metadata, analysis periods, filters, and reference choices, so those assumptions should be visible in code.

Inputs and outputs

At a high level, an assessment needs:

Input Purpose
SCADA time series turbine power, wind speed, yaw, pitch, RPM, downtime, and related operational signals
turbine metadata turbine names, turbine type, rated power, rotor diameter, and location where available
analysis configuration test/reference turbines, pre/post or toggle periods, filters, long-term settings, and output paths
reference data reanalysis, mast, LiDAR, or reference-turbine signals used for detrending and validation

The main analysis returns a pandas.DataFrame with per-test/per-reference uplift results, uncertainty columns, warning counts, and supporting diagnostic metrics. When plot saving is enabled, diagnostic figures are written under PlotConfig.plots_dir; CSV results are written under the configured assessment output directory.

Analysis features

wind-up includes utilities for the parts of an uplift study that usually need careful handling:

  • SCADA cleaning and filtering for unavailable or implausible operating data
  • power curve estimation by turbine type
  • wind speed estimation from turbine power (preferred for reference turbines) and measured wind speed
  • waking state calculation per timestep using turbine coordinates and SCADA
  • yaw direction northing checks and optional optimized northing corrections
  • long-term distribution calculations
  • wind speed drift checks
  • pre/post and toggle-based splitting
  • reference selection and combined uplift calculations
  • diagnostic plots for input data, detrending, power curves, yaw direction, reanalysis comparison, waking state, long-term distributions, and final results

Development

This project uses uv for dependency management, poethepoet for task running, Ruff for formatting/linting, mypy for type checking, and pytest with coverage for tests.

Create the development environment:

uv sync --all-extras --dev
uv run poe all-fast

Run the full local verification suite before releases or when you need the slow regression tests as well:

uv run poe all

Individual tasks are also available:

uv run poe lint-check   # formatter, linter, and mypy checks
uv run poe test-fast    # tests excluding the slow marker
uv run poe test         # full test suite with coverage report
uv run poe jupy         # start JupyterLab for example exploration

The GitHub Actions workflow runs linting and tests on Python 3.10 and 3.13.

Project status

The package is marked as beta in the Python package metadata. Interfaces and configuration options may still evolve, but the repository includes a substantial test suite and example analyses for regression coverage.

License

wind-up is released under the BSD 3-Clause License. See LICENSE.txt for the full license text.

Contact

For questions about the package, contact Alex Clerc at Alex.Clerc@res-group.com.

Metadata

Release files for res-wind-up 0.5.1

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

Source distribution (sdist)

Source distribution for res-wind-up 0.5.1
File Size Uploaded Provenance Actions
res_wind_up-0.5.1.tar.gz 105.5 kB With provenance Details for res_wind_up-0.5.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for res-wind-up 0.5.1
File Interpreter ABI Platform Actions
res_wind_up-0.5.1-py3-none-any.whl Python 3 none any Details for res_wind_up-0.5.1-py3-none-any.whl

Total release size: 204.8 kB

Release files / res_wind_up-0.5.1.tar.gz

Download URL res_wind_up-0.5.1.tar.gz
Size 105.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9c891b7039eea467eaec8e2283703ab20c821dcdc43557cd571dd4e525e8f6bf
BLAKE2b-256 checksum
How to use checksums
0992db62e9473b584685559520f1eeb4d415f944d7a0f2748333a3f8548ce5c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / res_wind_up-0.5.1-py3-none-any.whl

Download URL res_wind_up-0.5.1-py3-none-any.whl
Size 99.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a41c253738c9afcf465b5c70bcabc8c7868a2a0d60368b5479b22824d65045a5
BLAKE2b-256 checksum
How to use checksums
06977c5141fa5f3af44e1d153f201c420124e43de13148f35076c0f6e1e0b113
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Security for res-wind-up 0.5.1

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for res_wind_up-0.5.1.tar.gz

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 Nov 3, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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