-
Notifications
You must be signed in to change notification settings - Fork 9
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
Issue 278 - Refactor of domain folder. #413
Conversation
LOL this a big boi |
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.
How do you decide between using file name include/compute/element_types/element_types.hpp
and include/compute/compute_element_types.hpp
?
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.
It should always be element_types/element_types.hpp
imho. I initially started naming files compute_xxx.hpp/cpp
thinking that compute would be a small struct. Now its grown much more detailed.
Looks like there a few filed that are no longer needed in cmake:
include
|
Otherwise LGTM |
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 have nothing to add to congyue's remarks, except the minor formatting issue.
I think we need a testing hackathon. This behemoth of a PR would be less daunting if we had more coverage (mildly motivated by finding seismogram iterator bug earlier today).
Also, it is wild to me that this PR cuts 2700 lines.
fortran/meshfem3d/setup/precision.h
Outdated
Fifth Floor, Boston, | ||
if not | ||
, write to the Free Software Foundation, Inc., !51 Franklin Street, Fifth Floor, | ||
Boston, |
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.
clang-format being a butt
n_element, ngllz, ngllx) { | ||
elements.extent(0), ngllz, ngllx) { | ||
|
||
const int nelement = elements.extent(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.
This i nice, no need to loop over all elements no moe
A testing hackathon or a testing spring would be great in the future. We definitely need some of that. |
Fixed |
Description
Sorry for the big PR 😣
This PR refactors the domain folder.
get_element_on_device
functions are now part of element_typeskokkos_kernels
so that the functions are using the macrosIssue Number
closes #278
Checklist
Please make sure to check developer documentation on specfem docs.