-
Notifications
You must be signed in to change notification settings - Fork 849
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
Improve the configuration file for the SA Neg test case #1559
Conversation
@@ -673,8 +673,8 @@ def main(): | |||
turbmod_sa_neg_rae2822 = TestCase('turbmod_sa_neg_rae2822') | |||
turbmod_sa_neg_rae2822.cfg_dir = "turbulence_models/sa/rae2822" | |||
turbmod_sa_neg_rae2822.cfg_file = "turb_SA_NEG_RAE2822.cfg" | |||
turbmod_sa_neg_rae2822.test_iter = 20 | |||
turbmod_sa_neg_rae2822.test_vals = [-2.004689, 0.742306, 0.497308, -5.265793, 0.809463, 0.062016] | |||
turbmod_sa_neg_rae2822.test_iter = 10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am curious why a reduced number of iterations would be beneficial? I would always tend to do more as small errors might accumulate enough only after a certain amount of iterations, to break the regression test. That scenario might not happen to frequently but as you also remove multigrid there should be some time freed-up, right :)
So feel free (from my point of view) to revert to 20 or higher if it doesnt cost minutes.
@@ -14,7 +14,7 @@ RESTART_SOL= NO | |||
MACH_NUMBER= 0.729 | |||
% | |||
% Angle of attack (degrees, only for compressible flows) | |||
AOA= 2.31 | |||
AOA= 20.31 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recon, the case still converges to a reasonable solution with that more aggressive AoA?
Co-authored-by: TobiKattmann <31306376+TobiKattmann@users.noreply.github.com>
Thank you @TobiKattmann for your feedback. The idea behind this new regression test config file is as follows: In my opinion, a diverging regression test is not a problem at all as it might not be used as a tutorial, only to verify the integrity of the commit. "The solution should always diverge to the same results". If the regression test should converge, let me know and I will update the config file :) |
That is a bit of a necessary evil, I would leave a warning in the config explaining exactly what you just did. |
Thanks for the explanation @suargi . I would personally advocate for that the testcases should converge to some reasonable solution people might use it as a starting point (copy the cfg and doing mild adaptions) for their own stuff. And the Testcases show off the capabilities to some degree, to do so, convergence is beneficial. But as we have a bunch of working 2D airfoils in regression already I recon that adding a clear explanation and warning to the cfg as suggested by Pedro is fine. Otherwise you might try to bisect the AoA ... maybe there is a value that triggers negative SA and does not diverge 🤔 Knowingly adding a diverging test without a clear warning is not good imo :) |
Include a header warning explaining the purpose and how to use this testcase.
Header with a warning included in commit 017616f. |
Is it ready to merge? |
% This regression test will diverge! % | ||
% % | ||
% This test case is only meant to trigger the negative part of the SA model, % | ||
% to check the integrity of the commits. It is inadvisable to use it as an % | ||
% starting point for tutorials. % | ||
% The rae2822 airfoil is a simple (fast) case. A high angle of attack is being % |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason github Files changed
tab shows me a messed up indentation ... but looking at the actual file the indentation is on point. Not sure why github does that 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm ... in chromium that looks good 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my side yes :) Can you though make sure the reg test run and report here in the PR correctly. I am not really what happened there. I started a re-run of all the jobs so if that runs like usual feel free to merge 👍 |
I do not know why a regression test from hybrid_regression_AD.py has failed. But it has nothing to do with this pull request. Therefore I think we can merge it. |
Yep sometimes certain cases of hybrid-reg-ad fail ... sometimes they don't :) |
Proposed Changes
Improve the configuration file for the turbulence_models SA Neg test case. With this new config file we should be better able to detect bugs in the code. For instance, with this new config file and number of iterations for the regression test, we will be able to detect bd40210.
PR Checklist