-
Notifications
You must be signed in to change notification settings - Fork 200
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
[WIP] Interfacing 1D CurlCurl from AMReX #5662
base: development
Are you sure you want to change the base?
[WIP] Interfacing 1D CurlCurl from AMReX #5662
Conversation
Should we document the performance like I did for this PR? |
Array<MultiFab,3> solution { MultiFab(*x_mfarrvec[n][2], make_alias, 0, 1), | ||
MultiFab(*x_mfarrvec[n][1], make_alias, 0, 1), | ||
MultiFab(*x_mfarrvec[n][0], make_alias, 0, 1) }; | ||
Array<MultiFab,3> rhs { MultiFab(*b_mfarrvec[n][2], make_alias, 0, 1), | ||
MultiFab(*b_mfarrvec[n][1], make_alias, 0, 1), | ||
MultiFab(*b_mfarrvec[n][0], make_alias, 0, 1) }; |
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.
Why did you map the AMReX to WarpX dimensions as 0,1,2 -> 2,1,0 and not 0,1,2 -> 2,0,1?
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 was clarified in a meeting based on the available documentation: https://warpx.readthedocs.io/en/latest/developers/dimensionality.html.
I think you can rebase this PR, the commit we fetch after #5699 is 044d52f7d309e340939d7cae449fd83209da317f, which seems to include AMReX-Codes/amrex#4331, if I'm not mistaken. |
Currently needs to compile with AMReX-Codes/amrex#4331 if using cmake for 1D compilation
(Currently CI tests will fail since it uses amrex src that does not include the above PR)