NonMatching::MeshClassifier for single point intersections

24 views
Skip to first unread message

Anne-Kathrin Wenske

unread,
Mar 31, 2026, 8:53:44 AM (3 days ago) Mar 31
to dea...@googlegroups.com
Dear all

I am using a cut finite element method to solve fluid-structure
interaction problems similarly to step-85.

In the current implementation of NonMatching::MeshClassifier, cells that
intersect the interface (given by a level set function) in only a single
vertex are classified as "intersected".

For my implementation I need those cells to be classified as strictly
"inside" or "outside" and modified the function location_from_dof_signs
accordingly. However, I am wondering whether there might be a case where
one wants those cells to actually count as "intersected" and would like
your opinion on this. Should those single point intersections count as
"intersected" or is "inside"/"outside" more reasonable?

Best

Anne

Simon Sticko

unread,
Mar 31, 2026, 1:41:28 PM (3 days ago) Mar 31
to dea...@googlegroups.com
Hello.

> In the current implementation of NonMatching::MeshClassifier, cells that
> intersect the interface (given by a level set function) in only a single
> vertex are classified as "intersected".

Just to be clear: Are we talking about the situation where the zero contour goes exactly through a single cell corner?

Given the implementation, I had expected that such a cell would be classified as inside/outside.

Best,
Simon

--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dealii+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dealii/8dac5b4b-a211-431c-9122-32719d6bca58%40ifam.uni-hannover.de.

Anne-Kathrin Wenske

unread,
Apr 2, 2026, 8:53:57 AM (yesterday) Apr 2
to deal.II User Group
Hello Simon,

you are correct, I hadn't realized that this issue has also been adressed in issue #16950.

Best
Anne
Reply all
Reply to author
Forward
0 new messages