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

Turbine availability and repair times in morro bay tow to port. #154

Open
Filip-OWF opened this issue Jul 4, 2024 · 4 comments
Open

Turbine availability and repair times in morro bay tow to port. #154

Filip-OWF opened this issue Jul 4, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Filip-OWF
Copy link

Hi,

While running the morro bay tow to port case from the development package.

I notice a strange behaviour in the results.

When reducing the amount of turbines to 4 or less it appears that they get stuck somewhere.

When looking at the results at the standard case morro bay tow to port case it appears that after about 5 years the failures are happening only on a few of the turbines and that those failures results in extended repair times.

Attached a PDF with some of the plots for easy reference.
Corewind simulations.pdf

Best Regards,
Filip

@RHammond2
Copy link
Contributor

Thanks for flagging this behavior @Filip-OWF, it's definitely a bit baffling at first glance. Are you working with all the same configurations that are provided in the repository, and just varying the number of turbines, or are there other modifications you've applied? Any information that you could provide for replicating this is greatly appreciated.

@Filip-OWF
Copy link
Author

Hi @RHammond2 , I'm away from my computer for a few weeks but the only changes I have made to the corewind test case in the development package is to reduce the amount of locations in the plant morro bay layout excel file and the project capacity in the config file. It appears that 5 turbines gives the expected results.

@RHammond2
Copy link
Contributor

Thanks for clarifying, @Filip-OWF, I'll investigate on my end to see what's going on.

@RHammond2
Copy link
Contributor

Just to give a quick update, the latest release unfortunately doesn't relate to this issue. However, I've made some headway on figuring out the underlying behavior, but not its root cause. One thing I noticed is a compounding of maintenance requests, and will need to revisit this again to figure out why these requests are being submitted in quick succession. For instance, an annual inspection should not occur twice in a single port repair cycle. I'll keep you updated here as I continue to make progress on this issue.

@RHammond2 RHammond2 added the bug Something isn't working label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants