Skip to content

Improvement: Add test for (rather new) function t8_forest_leaf_neighbor_subface - #2388

Open
spenke91 wants to merge 4 commits into
mainfrom
test_neighbor_surface_helper
Open

Improvement: Add test for (rather new) function t8_forest_leaf_neighbor_subface#2388
spenke91 wants to merge 4 commits into
mainfrom
test_neighbor_surface_helper

Conversation

@spenke91

@spenke91 spenke91 commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Closes #2295

Describe your changes here:

Adds a test to the function t8_forest_leaf_neighbor_subface added in #2216 .

All these boxes must be checked by the AUTHOR before requesting review:

  • The PR is small enough to be reviewed easily. If not, consider splitting up the changes in multiple PRs.
  • The title starts with one of the following prefixes: Documentation:, Bugfix:, Feature:, Improvement: or Other:.
  • If the PR is related to an issue, make sure to link it.
  • [] The author made sure that, as a reviewer, he/she would check all boxes below.

All these boxes must be checked by the REVIEWERS before merging the pull request:

As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.

General

  • The reviewer executed the new code features at least once and checked the results manually.
  • The code follows the t8code coding guidelines.
  • New source/header files are properly added to the CMake files.
  • The code is well documented. In particular, all function declarations, structs/classes and their members have a proper doxygen documentation. Make sure to add a file documentation for each file!
  • README.md files are updated if necessary.
  • All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue).

Tests

  • The code is covered in an existing or new test case using Google Test.
  • The code coverage of the project (reported in the CI) should not decrease. If coverage is decreased, make sure that this is reasonable and acceptable.
  • Valgrind doesn't find any bugs in the new code. This script can be used to check for errors; see also this wiki article.

If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):

  • Should this use case be added to the github action?
  • If not, does the specific use case compile and all tests pass (check manually).

Scripts and Wiki

  • If a new directory with source files is added, it must be covered by the scripts/internal/find_all_source_files.sh to check the indentation of these files.
  • If this PR introduces a new feature, it must be covered in an example or tutorial and a Wiki article.

License

  • The author added a BSD statement to doc/ (or already has one).

@codecov

codecov Bot commented Aug 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.36%. Comparing base (add658b) to head (896779d).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2388      +/-   ##
==========================================
+ Coverage   82.28%   82.36%   +0.08%     
==========================================
  Files         125      125              
  Lines       20701    20706       +5     
==========================================
+ Hits        17033    17054      +21     
+ Misses       3668     3652      -16     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@lenaploetzke lenaploetzke left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks for adding the test, i have some first comments for you :)

"t8_forest_leaf_neighbor_subface requires leaf neighbor to be one level coarser!\n");
#endif

// Determine the virtual face neighbor of leaf along face.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I like the addition of comments! Can you also explain why we need a virtual neighbor here?

// Determine the neighbor_leaf's children at neighbor_face (i.e., at the dual face of face).
std::array<t8_element_t *, T8_ECLASS_MAX_FACE_CHILDREN>
neigh_children_at_face; // assumes the forest is (locally) 2:1 balanced
scheme->element_new (neighbor_tree_class, neigh_children_at_face.size (), neigh_children_at_face.begin ());

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Isnt it enough to use num_neighbor_face_children instead of the size?

num_children, nullptr);
// Find out which entry of neigh_children_at_face is equal to target_virtual_face_neighbor.
auto iter = std::find_if (
neigh_children_at_face.begin (), neigh_children_at_face.end (), [&] (t8_element *candidate) -> bool {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think here also end() is not necessary but only neigh_children_at_face.begin()+num_neighbor_face_children right?


INSTANTIATE_TEST_SUITE_P (t8_gtest_face_neighbors, forest_face_neighbors_two_quad_mesh, AllSchemeCollections);

/**

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

We have a t8_gtest_adapt_callback file (where we define one test callback at the moment), i think this one could be a cool addition (such that we can reuse it in other tests). What do you think?

/**
* \brief Class to test the functionality of \b t8_forest_leaf_neighbor_subface.
*/
class forest_face_neighbors_subface: public testing::TestWithParam<std::tuple<int, cmesh_example_base *> > {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Struct?

void
TearDown () override
{
// Unref the

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

forest?

// ----------------------------------------------------------
// -------- LOOP 1: Iterate over all local trees.
// ----------------------------------------------------------
for (int itree = 0; itree < num_local_trees; itree++) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
for (int itree = 0; itree < num_local_trees; itree++) {
for (t8_locidx_t itree = 0; itree < num_local_trees; itree++) {

?

// ----------------------------------------------------------
// -------- LOOP 2: Iterate over all local elements in the tree.
// ----------------------------------------------------------
for (int ielem_tree = 0; ielem_tree < num_elems_tree; ielem_tree++) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Same as above

int check_face = -1;
int neigh_child_to_check = -1;
int i_child_at_face = -1;
;

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
;

?

// Make sure the face relation is also correct.
EXPECT_EQ (iface, dual_dual_face);

// (7.) Free memory of neigh_children and checkelem

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
// (7.) Free memory of neigh_children and checkelem
// (7.) Free memory of neigh_children and check_elem

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.

Improvement: Cover t8_forest_leaf_neighbor_subface in a test case

2 participants