You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the WindIO definition of the floating platform, I cannot seem to find an indication that the lower pontoons are flooded.
After a conversation with @gbarterhere, I think the correct way to specify fluid ballast would be to add something like the following block in the specification of the lower pontoons, together with a new material called ocean_water.
The text was updated successfully, but these errors were encountered:
fabiopierella
changed the title
Missing specification of liquid ballast missing in WindIO specification of floating platform
Missing specification of liquid ballast in WindIO specification of floating platform
Dec 30, 2024
fabiopierella
changed the title
Missing specification of liquid ballast in WindIO specification of floating platform
Missing liquid ballast in WindIO specification of floating platform
Dec 30, 2024
I agree that there should be some way to specify whether a member is filled/flooded. It's been on my TODO list to add this to WindIO/WISDEM.
In my mind, it was just a flooded: True flag. If a specific volume is specified, then it could conflict with the calculated volume that's defined by the member diameter/thickness and joint locations.
WindIO improvement work is planned for the next 2-3 months. Let's keep this Issue open as a placeholder / reminder to add a flooded flag. This will be useful for fixed-bottom monopiles too.
Description
In the WindIO definition of the floating platform, I cannot seem to find an indication that the lower pontoons are flooded.
After a conversation with @gbarter here, I think the correct way to specify fluid ballast would be to add something like the following block in the specification of the lower pontoons, together with a new material called
ocean_water
.Let me know what you think about this solution.
Best,
Fabio
The text was updated successfully, but these errors were encountered: