Skip to content

Conversation

@coroa
Copy link
Member

@coroa coroa commented Nov 1, 2024

The ERA5 long run average is determined during cutout preparation by averaging the monthly mean wind speeds from 1980 to the last year and made available as a dataset variable wnd100m_lra.

Example usage:

cutout.wind(
    atlite.windturbines.Enercon_E101_3000kW,
    real_long_run_average_windspeed="gwa3_250_windspeed_100m.tif",
)

TODO:

  • Add docs
  • Add tests

Closes #373 .

Changes proposed in this Pull Request

Checklist

  • Code changes are sufficiently documented; i.e. new functions contain docstrings and further explanations may be given in doc.
  • Unit tests for new features were added (if applicable).
  • Newly introduced dependencies are added to environment.yaml, environment_docs.yaml and setup.py (if applicable).
  • A note for the release notes doc/release_notes.rst of the upcoming release is included.
  • I consent to the release of this PR's code under the MIT license.

The ERA5 long run average is determined during cutout preparation by averaging
the monthly mean wind speeds from 1980 to the last year and made available as
a dataset variable wnd100m_lra.

Example usage:

cutout.wind(
    atlite.windturbines.Enercon_E101_3000kW,
    real_long_run_average_windspeed="gwa3_250_windspeed_100m.tif",
)
@coroa
Copy link
Member Author

coroa commented Nov 1, 2024

Since the bias correction factor is independent of the turbine model and other settings of the conversion, it might make sense to either incorporate the full bias correction into the cutout preparation.

Or disentangle it completely from the actual stored dataset. ie. there could be a calculate_windspeed_bias_correction(cutout, gwa) like function which retrieves the long run average wind speed on demand and then calculates the bias correction for scaling the dataset wind speeds to the gwa average, which the user then passes as argument to the wind conversion function. So that the cutout does not need to store anything and the calculation of the scaling factor does not need to be repeatedly applied either.

@coroa
Copy link
Member Author

coroa commented Mar 13, 2025

Closing in favour of simpler and more flexible alternative in #405

@coroa coroa closed this Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow wind speeds to be corrected by a location-specific linear factor (e.g. from GWA)

1 participant