rafmudaf / floris

This is my fork of FLORIS containing lots of works in progress. Don't trust anything here :) See https://github.com/nrel/floris for the stable version.

Hi there 👋

I'm Rafael. I'm a researcher at the National Renewable Energy Laboratory (NREL) working primarily on wind energy modeling software. In addition to wind turbine and wind farm dynamics, I'm interested in improving the software development process especially as it relates to research software, and I'm pursuing this throughout 2023 as a Better Scienfitic Software Foundation Fellow where I'll develop processes and training material on visually communicating elements of software design as part of the software development process.

Please get in touch (LinkedIn) to talk about wind energy and research software!

Active projects:

• WETO Software Stack characterization and coordination
• wcomp steady-state wind farm wake modeling software comparison
• Communicating Design
• FLORIS 4ever
• Heat flow and humidity in my house

floris's Issues

Add an iterative solver initially operating on the FullFlowField grid type

This will do some sort of iterative solve (newton solve?) to converge on a solution of the full flow field. For cases with a large number of points, this may be more efficient and could lead to a path for parallelization.

Build a visualization package around the new array structures

We need functionality similar to what currently exists in v2, but also some other things more relevant to v3.

See #9.

Sort turbines within Farm data structure prior to iterating through the solve

Investigate the kink in the gauss wake

Change conftest TI to 6%

This matches the example input file.

Support heterogeneous flow field input

Reduce the default number of grid points on TurbineGrid

Determine a many turbine with multiple wind speeds and wind directions use case to establish a speedup benchmark for v2 v v3

Add combination model class and infrastructure

Add GCH components to Gauss models

Add attrs structure to the FarmController class

Update getting–started examples to v3

Add turbulence model class and infrastructure

Implement cumulative wake model

• Model
• Solver
• Grid?

Wind rose / AEP calculation performance comparison

Wind rose definition from input and modeled in code

Add Gauss wake model to v3

Raise an error if the power curve data is invalid

Port the floris v2 tools package to use the v3 simulation package

`FlorisInterface`, `Floris`, and the json/yaml input spec to mirror v2 robustness of definition, with a new method to define a simulation with one configuration.

Infrastructure for testing and reporting

airspeed velocity (asv) is a tool for benchmarking Python packages over their lifetime. Runtime, memory consumption and even custom-computed values may be tracked. The results are displayed in an interactive web frontend that requires only a basic static webserver to host.

Incorporate Gaussian models

I've made good progress on this in https://github.com/rafmudaf/floris/tree/v3/gauss. Things left to do:

• Incorporate the wake-added turbulence
• Gauss deflection model

Gauss GCH regression test baselines changed slightly. Why?

attrs testing generates warnings

Pytest parses the test files and collects any class or function containing the work "test" into its list of tests. However, if a class has an __init__ method, it is not added to the test list and a warning is printed to the screen. See https://github.com/rafmudaf/floris/runs/4069114151?check_suite_focus=true#step:5:24.

In FLORIS, we have a couple of test modules that define classes containing the work "test" but are not meant to be standalone tests themselves. Instead, they're used as infrastructure for other tests. See the following locations:

• https://github.com/rafmudaf/floris/blob/redesign/tests/base_model_test.py#L23
• https://github.com/rafmudaf/floris/blob/redesign/tests/utilities_unit_test.py#L38

I propose to rename these classes to something like "AttrsClassNoModelString" so that we avoid these warnings.

Resetting the dynamically set properties on Grid

• turbine_coordinates is not reset here: https://github.com/rafmudaf/floris/blob/redesign/src/simulation/grid.py#L59
• If the list properties are appended to rather than replaced via =, the validators don't run so the dynamic properties are out of sync