Repository navigation
Conversation
for more information, see https://pre-commit.ci
Contributor
Author
|
I am using the following notebook for my own tests: |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #531
Note
This PR was assisted by AI. The new data module
era5_corrected.pyis based on the existingera5.pymodule.There are probably smarter ways to handle the features. I am also unsure of the naming. One needs to be aware to not mix it with the ERA5 features.
I didn't test everything but for me it works quite well. Would be great if someone could have a look at the PR. There are probably things that can be improved or made more precise.
The differences in capacity factor between ERA5 and ERA5corrected can be quite large.
Changes proposed in this Pull Request
New module
atlite/datasets/era5_corrected.py(registered as"era5-corrected"). It downloads the C3S Energy bias-corrected ERA5 wind data (CDS datasetsis-energy-global-reanalysis). Bias-correction is based on GWA2 (see product user manual)Selectable features (use in
cutout.prepare(features=[...])):wind_correctedwnd100m_corrected100m_wind_speedwind_corrected_extrapolatedwnd100m_corrected_extrapolated100m_wind_speed_extrapolatedwind_shear_exp_correctedwnd_shear_exp_correctedwind_power_law_coefficientstime. A whole year in one request works, and so domonthly_requests=Trueinprepare().atlite/datasets/era5.pyandera5_edh.py:roughnessfeature (thewindfeature still includes it), because the default for extrapolation to different heights is logarithmic which needs roughness.atlite/data.py:gc.collect()is called first.Other:
atlite/wind.py: base-height regex changed tofullmatch. --> I dont know why AI did this.What to consider when using
era5-correctedcutout.windonly useswnd100mandwnd_shear_exp, so assign the corrected variables first:roughnessfeature fromera5/era5-edhtogether withinterpolation_method="logarithmic".wnd_shear_exp_correctedis an average by month and hour, not a time series. It does not follow weather variability, unlike the ERA5wnd_shear_exp.module=["era5-edh", "era5-corrected"], and name the features explicitly inprepare().~/.cdsapirc.Image below compares the raw mean wind speeds at 100m (DK, DE, Alpes):

Image below shows the difference in mean wind between ERA5 and ERA5 corrected (100m)

You can compare image above loosely with Nayak et al. (different units though)

Image below shows the hourly shear factor (mean area).

Checklist
doc.environment.yaml,environment_docs.yamlandsetup.py(if applicable).doc/release_notes.rstof the upcoming release is included.