-
Notifications
You must be signed in to change notification settings - Fork 99
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
Overset update fixes #225
Overset update fixes #225
Conversation
Codecov Report
@@ Coverage Diff @@
## main #225 +/- ##
==========================================
+ Coverage 41.04% 41.35% +0.30%
==========================================
Files 13 13
Lines 3793 3794 +1
==========================================
+ Hits 1557 1569 +12
+ Misses 2236 2225 -11
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
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.
Looks good. I have just a few questions.
!call updateOversetConnectivity_d(1_intType, sps) | ||
if (oversetPresent) then | ||
if (oversetUpdateMode == updateFast) then | ||
call updateOversetConnectivity_d(1_intType, sps) |
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.
So the routine always existed it just wasn't being used?
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.
This is related to your first question. For some reason, the fast and full updates were grouped in the residual and derivative routines. As with updateOversetConnectivity
, the AD routines also only apply for fast mode. The AD routines existed and worked, but they were commented out some time ago by Ney, who was using the full update.
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.
Just left a minor comment. The rest of the PR looks good to me.
Overset update fixes (mdolab#225)
Overset update fixes (mdolab#225)
Purpose
I made some fixes to the
full
andfast
oversetUpdateMode
options.full
was not working because #27 changed thecutCallback
function signature but did not change it forfull
mode.fast
was not working in parallel because the pointer toxCen
was deleted in this commit: b32cfb4.This was leading to errors like this:
I also fixed the adjoint routines for
fast
mode and updated the docs to make the drawbacks of these options clear.Expected time until merged
One week
Type of change
Testing
I expanded the cube overset tests to test all three overset update modes. The
fast
andfull
tests fail without the fixes in this PR.Checklist
flake8
andblack
to make sure the code adheres to PEP-8 and is consistently formatted