-
Notifications
You must be signed in to change notification settings - Fork 376
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'jgfouca/p3_cxx_init' into master (PR #6845)
This removes the last f90 from P3. Change list: 1) Move table read/write implementation to CXX in p3_init_impl.hpp 2) p3_init now returns a P3LookupTables object with all the views inside containing the tables. 3) Rename init_kokkos_tables to get_global_tables 4) Rename init_kokkos_ice_lookup_tables to get_global_ice_lookup_tables 5) Remove all f90 bridge code 6) Move p3_tables_setup to tests dir, cleans up top p3 directory 7) Fix p3_tables_setup implementation; it got broken in recent PRs but we didn't notice because it didn't get built by default 8) Remove P3GlobalForFortran test struct, just call p3_init! 9) Remove P3InitAP3Data test struct Debatable change: I really wanted to have P3LookupTables lookup_tables be static in p3_init so they would not have to be re-created on every p3_init call. Unfortunately, Kokkos does not allow static views to be active on program shutdown, since this occurs after Kokkos::finalize, so we would need add a p3_finalize method and ensure it was called at the end of p3. This seems burdensome and error prone, so I just decided to re-read all the tables every time p3_init is called. There are some round-off level diffs in P3, so: [non-BFB] * jgfouca/p3_cxx_init: GPU fixes: need to use host views for init stuff Update PAM submodule Change new table names to not conflict with older tables Github feedback Convert p3_init from f90 to CXX
- Loading branch information
Showing
25 changed files
with
397 additions
and
530 deletions.
There are no files selected for viewing
Submodule external
updated
2 files
+2 −14 | physics/scream_cxx_interfaces/scream_cxx_interface_finalize.cpp | |
+3 −27 | physics/scream_cxx_interfaces/scream_cxx_interface_p3.cpp |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.