-
Notifications
You must be signed in to change notification settings - Fork 97
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
Convert hdterm and hdterm3 to C++ #2625
Conversation
there's a crash in the test suite for rad-thermalwave-3d |
compliation failure actually |
fixed |
{ | ||
if (mask.contains(i+icp,j+jcp,k+kcp)) { | ||
if (mask(i+icp,j+jcp,k+kcp) > 0) { | ||
if (bct == LO_DIRICHLET) { |
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.
do we want to throw an error if they come in with the wrong boundary type? That's the only real diff with the Fortran
// group is for cell edges. | ||
|
||
int icp = 0; | ||
int jcp = 0; |
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.
we have this same code now in several places.. Maybe we should make an inline function with this and return things via structured binding? Doesn't need to be this PR
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.
Yes, one of my plans after we finish the Fortran conversion is to do a bunch of cleanup on this since there's a bunch of similar-ish functions across the three Hypre ABEC implementations
PR summary
PR checklist
CHANGES
file has been updated, if appropriate