Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: layout constraint and minimum distance definition #363

Closed
MYMahfouz opened this issue Mar 4, 2022 · 2 comments · Fixed by #367
Closed

Bug report: layout constraint and minimum distance definition #363

MYMahfouz opened this issue Mar 4, 2022 · 2 comments · Fixed by #367
Assignees
Labels
bug Something isn't working v3 Label to denote focus on v3

Comments

@MYMahfouz
Copy link

The second constraint: distance from boundary
The constraint is defined with a lower bound as zero. Zero is the upper bound according to the constraint function.
This can be fixed by changing line 104 in floris.tools.optimization.pyoptsparse.layout.py

optProb.addConGroup("boundary_con", self.nturbs, upper=0.0)

The minimum distance is fixed and not read from the turbine input
The value of the turbine diameter is fixed to 126 m instead of reading the turbine diameter.
This can be fixed by updating the last line in floris.tools.optimization.pyoptsparse.layout.py

@MYMahfouz MYMahfouz changed the title Layout constraint and minimum distance definition Bug report: layout constraint and minimum distance definition Mar 4, 2022
@bayc bayc self-assigned this Mar 4, 2022
@bayc bayc added bug Something isn't working v3 Label to denote focus on v3 labels Mar 4, 2022
@bayc
Copy link
Collaborator

bayc commented Mar 4, 2022

Thanks for the bug report! I will look into this today and get it addressed.

@MYMahfouz
Copy link
Author

Happy to help. Thanks for adding the function to the new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v3 Label to denote focus on v3
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants