Skip to content

Feature: Add subelement scheme for quad and triangle hanging node resolution - #2395

Open
lenaploetzke wants to merge 37 commits into
mainfrom
subelement_quads
Open

Feature: Add subelement scheme for quad and triangle hanging node resolution#2395
lenaploetzke wants to merge 37 commits into
mainfrom
subelement_quads

Conversation

@lenaploetzke

@lenaploetzke lenaploetzke commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

Closes #2396

Describe your changes here:
This PR adds a general subelement scheme with specializations for quad and triangle hanging node resolution. It also provides two examples and one test.
I implemented only the functions necessary for the visualization. Next steps are all functions necessary for simulations. This means for example neighbors.

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 13, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 84.27481% with 103 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.35%. Comparing base (ea082ff) to head (ba8cf74).
⚠️ Report is 4 commits behind head on main.

Files with missing lines Patch % Lines
.../t8_schemes/t8_subelement/t8_subelement_scheme.hxx 76.40% 80 Missing ⚠️
.../t8_subelement/specializations/t8_scheme_quads.hxx 91.75% 8 Missing ⚠️
...es/t8_subelement/specializations/t8_scheme_tri.hxx 90.69% 8 Missing ⚠️
src/t8_forest/t8_forest_subelement.cxx 93.87% 3 Missing ⚠️
src/t8_schemes/t8_scheme.hxx 85.71% 2 Missing ⚠️
src/t8_forest/t8_forest_adapt.cxx 91.66% 1 Missing ⚠️
src/t8_schemes/t8_subelement/t8_subelement.cxx 96.66% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2395      +/-   ##
==========================================
+ Coverage   82.28%   82.35%   +0.07%     
==========================================
  Files         125      131       +6     
  Lines       20703    21352     +649     
==========================================
+ Hits        17035    17584     +549     
- Misses       3668     3768     +100     

☔ 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.

@ole-alb ole-alb assigned ole-alb and unassigned ole-alb Aug 17, 2026
Comment thread src/t8_schemes/t8_scheme.cxx Outdated
@spenke91
spenke91 self-requested a review August 17, 2026 13:03
@spenke91 spenke91 self-assigned this Aug 17, 2026

@spenke91 spenke91 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 a lot @lenaploetzke for this great feature! I'm glad to see the subelement concept being molded into an actual implementation 👍
I like the overall code design and think it is great that we barely have to change the interface of the normal schemes. As you will see in one of the comments, I feel like we might be missing one layer of inheritance between "a subelement scheme for triangles" and "a subelement schemes for triangles that resolves haning nodes".

Aside from that, most of my comments are minor suggestion and remarks, as usual :-)

Comment on lines +66 to +69
if ((t8_forest_get_tree_element_offset (forest_from, which_tree) + lelement_id) % 2 == 0) {
return 1;
}
return 0;

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 this is actually the local element ID, not the global one. It relies on the tree's member variable
elements_offset, which is process-local, see here:

Image

}

int
t8_test_adapt_even_global_id ([[maybe_unused]] t8_forest_t forest, t8_forest_t forest_from, t8_locidx_t which_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.

Suggested change
t8_test_adapt_even_global_id ([[maybe_unused]] t8_forest_t forest, t8_forest_t forest_from, t8_locidx_t which_tree,
t8_test_adapt_even_local_id ([[maybe_unused]] t8_forest_t forest, t8_forest_t forest_from, t8_locidx_t which_tree,

* \param [in] elements Pointers to a family or, if \a is_family is zero, pointer to one element.
*/
int
t8_test_adapt_even_global_id (t8_forest_t forest, t8_forest_t forest_from, t8_locidx_t which_tree, t8_eclass_t eclass,

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
t8_test_adapt_even_global_id (t8_forest_t forest, t8_forest_t forest_from, t8_locidx_t which_tree, t8_eclass_t eclass,
t8_test_adapt_even_local_id (t8_forest_t forest, t8_forest_t forest_from, t8_locidx_t which_tree, t8_eclass_t eclass,

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'd suggest to use the callback refine_every_nth_element_callback I recently added 🙂
(which is adjusted to global elements in #2415 )

@@ -0,0 +1,25 @@
# t8_subelement

This folder provides **subelement schemes**. Subelements are inserted *after* the standard recursive refinement and enable one additional refinement level that uses a different scheme.

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
This folder provides **subelement schemes**. Subelements are inserted *after* the standard recursive refinement and enable one additional refinement level that uses a different scheme.
This folder provides **subelement schemes**. Subelements are inserted *after* the standard recursive refinement and enable one additional refinement step that uses a different scheme.

I think we should not call it level to avoid confusion 🤔

void *scheme_context; /**< Anonymous implementation context. */

public:
// #################################____Constructor & Destructor...____###############################################

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.

Is there a specific reason the constructor above is not sorted into this category?

* \param[in] forest Forest to be adapted.
*/
t8_forest_t
t8_adapt_forest_2and (t8_forest_t forest)

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
t8_adapt_forest_2and (t8_forest_t forest)
t8_adapt_forest_2nd (t8_forest_t forest)

?

prefix_removed_sub);

/* --- Second cycle: adapt around the larger circle. --- */
forest = t8_adapt_forest_2and (forest);

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
forest = t8_adapt_forest_2and (forest);
forest = t8_adapt_forest_2nd (forest);

Comment on lines +141 to +148
struct t8_adapt_data adapt_data = {
{ 0, 1, 0 }, /* Center of the circle. */
0.6, /* Radius */
0.1, /* Delta (transition band width) */
2, /* Minlevel */
6 /* Maxlevel */
};

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.

Wouldn't it be easier to define the whole adapt_data somewhere accessible from main and just adjust the radius then via adapt_data.radius?
Then we could also get rid of these two adapt wrappers. However, both is fine.

/* --- Adapt the forest: refine near the first circle, creating hanging nodes. --- */
forest = t8_adapt_forest (forest);
std::cout << "Subelements before removing: " << t8_forest_has_global_subelements (forest) << std::endl;
prefix = "t8_adapted1";

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.

Might be convenient to adjust the naming because Paraview otherwise shows the two t8_adapted ptvu files as series in the open-file menu. Not a big problem, but maybe it would be nice to avoid it, e.g.,

Suggested change
prefix = "t8_adapted1";
prefix = "t8_adapted_1st";

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
*/

/** \file t8_scheme_tri.hxx

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 would suggest to use more descriptive names for these two files. I know the context is clear from the path, but the path is often not shown, e.g., in vs code. So maybe something like t8_subelement_scheme_tri.hxx or t8_scheme_hanging_nodes_tri.hxx?

@spenke91 spenke91 assigned lenaploetzke and unassigned spenke91 Sep 3, 2026
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.

Feature: Add subelement scheme for quad and triangle hanging node resolution

4 participants