-
Notifications
You must be signed in to change notification settings - Fork 170
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add in baseline solver documentation
- Loading branch information
Showing
2 changed files
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Solver Descriptions | ||
|
||
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. | ||
|
||
## Sequential | ||
|
||
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. | ||
|
||
## CC Solver | ||
|
||
TODO | ||
|
||
## TurbOPark Solver | ||
|
||
TODO |