-
Notifications
You must be signed in to change notification settings - Fork 137
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
Beamdyn #48
Beamdyn #48
Conversation
Here some more numbers to support the discussion OLD NEW |
1P is 0.125 Hz 6P might be problematic with the new design and we could further reduce TE reinforcement thickness |
Pietro, Thank you for laying this out so clearly. You went above and beyond in tracking the differences and impact. From the NREL toolchain point-of-view, this makes a lot of sense. I see it this update as better capturing the originally intended design and doesn't require a re-optimization of the blade shape and support structure. However, I also have in mind Jenni's comment that ontology changes to the blade are currently difficult for her to capture in HAWC2 without enlisting Frederik's help. I am curious to hear her perspective in our next conversation after the Easter holidays there. |
Seems like we are consolidating on the |
Fix wisdem hawc2
I've run SONATA and WISDEM iteratively trying to converge on a blade model whose properties are similar in both ElastoDyn and BeamDyn
The biggest change consists of widening the TE reinforcement to be able to reduce its thickness so that it can physically fit within the TE of the airfoils
The second change is to increase the gelcoat from 0.5 mm to 1 mm. This is an arbitrary change simply dictated by the inability of SONATA of meshing extremely thin layers with planar elements
With these two changes, the properties between the two models converge much better than earlier, here some plots
I understand the weaknesses of following such approach (especially the 1mm of gelcoat) and I'm happy to open a discussion about this