Wind Power Simulation¶
RESKit provides a feature-rich wind power simulation, as demonstrated by the following examples:
- The first example provides an overview of how to apply the available wind power worklows.
- The next example deals with wind power curves.
- It shows how to define, load, and inspect a power curve.
- Then, it presents how to create a power curve from srcatch and how to load a real turbine's power curve.
- The third example shows how to convolute the power curve to account for stochastic effects.
- The fourth example shows how RESKit can suggest wind turbine designs for specific operation conditions.
- The fifth example demonstrates how to estimate the capital cost of a wind turbine using RESKit.
- The sixth example shows how to conduct actual simulations of a wind power plant.
- First, a basic simulation is shown.
- Then, a more advanced example is shown, which accounts for more realistic effects.
- Lastly, it is demonstrated how to use one of the predefined workflows provided by RESKit.
- To apply this workflow outside of the test example, you need the full ESA Land Cover Dataset. It can be downloaded here: https://cds.climate.copernicus.eu/datasets/satellite-land-cover?tab=download.
- The final example shows how to apply the ETHOS.RESKit.Wind workflow.
- This requires the ERA5 dataset, for which a download instructions can be found here.
- In order to use the workflow, the ERA5 dataset must be preprocessed to contain the absolute wind speeds, as shown here.
- To increase spatial resolution of the simulation and allow extrapolation of wind speeds to turbine hub height, the GWAv4 (Global Wind Atlas) is used. This example provides a small test data sample for demonstration purposes. For applications outside the test example, however, the full GWAv4 dataset is required, which can be downloaded here: https://globalwindatlas.info/en/download/gis-files.
- (Optional) If you have purchased Power Curves from thewindpower.net, please use the following script to process them: Process Power Curves
Paths to a custom turbine library and baseline turbine definitions can be set in default_paths.yaml.