Skip to content
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

Communicate volume mesh in boundary data #6293

Merged

Conversation

kidder
Copy link
Member

@kidder kidder commented Sep 17, 2024

Proposed changes

  • Adds tag evolution::dg::subcell::Tags::MeshForGhostData which holds the volume mesh used by each neighbor for communicating subcell ghost data. This information was previously held by domain::Tags::NeighborMesh<Dim> which will now always hold the mesh of the neighbor.
  • Add the volume mesh to what is communicated via BoundaryData. This is needed for reactive adaptive mesh refinement.

Upgrade instructions

Code review checklist

  • The code is documented and the documentation renders correctly. Run
    make doc to generate the documentation locally into BUILD_DIR/docs/html.
    Then open index.html.
  • The code follows the stylistic and code quality guidelines listed in the
    code review guide.
  • The PR lists upgrade instructions and is labeled bugfix or
    new feature if appropriate.

Further comments

@kidder
Copy link
Member Author

kidder commented Sep 17, 2024

@nilsdeppe please test this for a BNS

Copy link
Member

@nilsdeppe nilsdeppe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mostly reasonable. I'll give this a test.

@@ -177,12 +178,12 @@ struct BoundaryCorrectionAndGhostCellsInbox {
ReceiveDataType&& data) {
auto& current_inbox = (*inbox)[time_step_id];
if (auto it = current_inbox.find(data.first); it != current_inbox.end()) {
auto& [volume_mesh_of_ghost_cell_data, face_mesh, ghost_cell_data,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also update retrieve_boundary_data_spsc in src/Evolution/DiscontinuousGalerkin/Actions/ApplyBoundaryCorrections.hpp

@kidder
Copy link
Member Author

kidder commented Sep 23, 2024

@nilsdeppe

  • added a fixup which fixed a problem with blast wave.
  • can you point me to a BNS setup I can test this on
  • On line 111 of PrepareNeighborData, in the alg::all_of(neighbor_meshes,...) should the meshes be the actual mesh of the neighbor or the ghost_data_mesh ?

This tag will be used to hold the mesh used for communicating subcell
ghost data instead of using the tag NeighborMesh.
Also change volume_mesh_ghost_cell_data to std::optional.
Now the item for Tags::NeighborMesh is always filled with the
communicated volume_mesh which is the active mesh of the neighbor.
The item for Tags::MeshForGhostData is set to the communicated
volume_mesh_ghost_cell_data, and is only used when doing DG-subcell.
@nilsdeppe nilsdeppe merged commit c4cc373 into sxs-collaboration:develop Sep 26, 2024
23 checks passed
@kidder kidder deleted the volume_mesh_in_boundary_data branch September 26, 2024 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants