Develop #8
Merged
Develop #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed some initial condition issues that were being seen. Particularly, I'm initializing the generator torque for the TSR tracking as Komega^2 or rated torque, if initial rotor speed is near rated rotor speed.
Had a bug in my autotuning of K for Komega^2, so fixed that.
Update the DTU parameter file. One thing I'm noticing is that CCBlade needs a more highly resolved blade to give the same rotor performance that is stated in the literature. I'm not sure how to get around this bug for now, so we'll have to stick with it. This does result in the "optimal" TSR being off from that in the literature, but CCBlade and openfast seem to be pretty consistent. Basically, I think everything likes more highly resolved blades..