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

Blade Reynolds number was above table limit #33

Open
danrhouck opened this issue Jul 22, 2020 · 3 comments
Open

Blade Reynolds number was above table limit #33

danrhouck opened this issue Jul 22, 2020 · 3 comments

Comments

@danrhouck
Copy link

I've gotten this warning at the end of simulations a few times: AT LEAST ONE BLADE REYNOLDS NUMBER WAS ABOVE TABLE LIMIT. UPPER LIMIT USED. I'm surprised to see it, though. In deciding what Reynolds numbers to use to calculate polars, I calculated all possible Reynolds numbers using the chord distribution and tip speed ratio to get the relative velocities, and then the freestream velocity to get the resultant at each span location. The highest Reynolds number that I used for my polars is about twice the highest Reynolds number I calculated. Could you verify how the Reynolds number is being determined in the simulation and, perhaps, explain how it could be so much higher than my estimates?

@whophil
Copy link
Collaborator

whophil commented Aug 14, 2020

Do your airfoil tables contain data for multiple Reynolds numbers, or just one? It looks like this error will be written if there is only one Reynolds number for any given airfoil.

https://github.com/SNL-WaterPower/CACTUS/blob/1776c78f61aab9366342469c8df07459e2b74ef0/src/mod/airfoil.f95#L94-L98

@danrhouck
Copy link
Author

danrhouck commented Aug 14, 2020 via email

@whophil
Copy link
Collaborator

whophil commented Aug 14, 2020

Not as written, it appears the error flag which controls the printing of that message, IUXTP, is global. It should be easy to modify to make it do what you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants