NatLabRockies / NatLabRockies/H2Integrate
Enable functionality to run FLORIS file with custom layout and/or multiple turbine types
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
Enable functionality to run FLORIS file with custom layout and/or multiple turbine types
The FLORIS wrapper in PR #372 sacrifices some functionality in FLORIS so that the number of wind turbines can be used as a design variable. The functionality sacrificed is:
- being able to use multiple turbine types in the farm
- being able to use a custom turbine layout
Proposed solution
Either create a separate FLORIS wrapper that runs FLORIS and does not have number of turbines as an input or modify the FLORIS component in PR #372 to have extended logic to handle this.
Alternatives considered
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the FLORIS wrapper introduced in PR #372 and the functionality it omits. Determine whether the implementation should be a separate wrapper or an extension of that component, then verify that custom layouts and multiple turbine types work without removing the existing turbine-count design variable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100