Skip to content

Commit 133f308

Browse files
committed
Add more descriptions of the solvers
1 parent 80534c8 commit 133f308

File tree

1 file changed

+54
-7
lines changed

1 file changed

+54
-7
lines changed

docs/solvers.md

Lines changed: 54 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,62 @@
11
# Solver Descriptions
22

3-
This page will explain the different solvers available in FLORIS. For each of the solvers (except TurbOPark) there is the regular solver, which computes the wake effects at each turbine, an a full flow solver, which calculates the wake effects across the entire layout, including non-turbine positions. The full flow solver is used primarily for visualizing the flow field because it's more computationally intensive, so runtimes are much slower for larger wind power plants.
3+
FLORIS includes a collection of solver algorithms to support different
4+
types of simulations and details for all wake models. The solver
5+
is selected and configured in the `solver` block of the main input file
6+
by specifying a type of grid, and each solver type has specific
7+
configuration options.
48

5-
## Sequential
9+
The following solver-types are available:
10+
- `sequential_solver`
11+
- Required grid: `TurbineGrid`
12+
- Primary use: AEP
13+
- This is the general purpose solver for any wake model that doesn't
14+
have a corresponding solver. It is often used in other solver
15+
algorithms to initialize the velocities at the turbines.
16+
- `full_flow_sequential_solver`:
17+
- Required grid: `FullFlowGrid`, `FullFlowPlanarGrid`
18+
- Primary use: Visualization
19+
- This is a widely used solver typically for visualization of a plane
20+
of points within the fluid domain. It is compatible with any wake
21+
model that doesn't have a corresponding solver.
22+
- `cc_solver`:
23+
- Required grid: `TurbineGrid`
24+
- Primary use: AEP with Cumulative-Curl model
25+
- This is a version of the `sequential_solver` specific to the
26+
Cumulative-Curl wake model.
27+
- `full_flow_cc_solver`:
28+
- Required grid: `FullFlowGrid`, `FullFlowPlanarGrid`
29+
- Primary use: Visualization with Cumulative-Curl model
30+
- This is a version of the `full_flow_sequential_solver` specific to the
31+
Cumulative-Curl wake model.
32+
- `turbopark_solver`:
33+
- Required grid: `TurbineGrid`
34+
- Primary use: AEP with TurbOPark model
35+
- This is a version of the `sequential_solver` specific to the
36+
TurbOPark wake model.
37+
- `full_flow_turbopark_solver`:
38+
- Required grid: `FullFlowGrid`, `FullFlowPlanarGrid`
39+
- Primary use: Visualization with TurbOPark model
40+
- This is a version of the `full_flow_sequential_solver` specific to the
41+
TurbOPark wake model.
642

7-
For each turbine in the layout (sorted from upstream to downstream), we calculate its effect on every downstream turbine. This is accomplished by calculating the deficit that each turbine adds to downstream turbines, then integrating it into the main data structure.
843

9-
## CC Solver
1044

11-
TODO
45+
## Sequential Solvers
1246

13-
## TurbOPark Solver
47+
This collection of solvers iterates over each turbine in order from
48+
upstream to downstream and applies the current turbine's wake impacts
49+
onto the downstream grid points. The grid points are typically
50+
associated with a turbine's rotor grid. The wake effect is calculated
51+
for the entire downstream domain, and masks are used to apply the wake
52+
only to points within a box of influence. The velocity deficit due to the
53+
wake is combined with the freestream velocity via the chosen wake
54+
combination model.
1455

15-
TODO
56+
## Full Flow Solvers
57+
58+
These solvers are typically used for visualization of a 3d or 2D
59+
collection of points. First, a sequential solver is used to calculate
60+
the wake as described above. Then, another loop over all turbines
61+
allows to add the impact of each turbine onto the points throughout
62+
the fluid domain.

0 commit comments

Comments
 (0)