Skip to content

Conversation

@th-skam
Copy link
Collaborator

@th-skam th-skam commented Sep 5, 2025

The problem is described in issue #80 along with a video.

The solution is to change the proximity detection and coupling point addition algorithm. Instead of relying on the tip to detect tetrahedral proximities, the modified algorithm starts from the last coupling point added and traverses the needle edge segments until it reaches the tip while adding evenly spaced coupling points along the way. This avoids creating a gap after puncturing the surface.

25-09-04-PunctureFix.mp4

Fix #80

@th-skam th-skam added the pr: fix label Sep 5, 2025
@th-skam th-skam added pr: status to review To notify reviewers to review this pull-request and removed pr: status wip labels Sep 12, 2025
@th-skam th-skam requested a review from epernod September 12, 2025 13:14
@epernod epernod added pr: status ready Approved a pull-request, ready to be squashed and removed pr: status to review To notify reviewers to review this pull-request labels Sep 14, 2025
@epernod epernod merged commit e6d3e39 into master Sep 14, 2025
4 checks passed
@epernod epernod deleted the fix-puncture branch September 14, 2025 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: fix pr: status ready Approved a pull-request, ready to be squashed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[algorithm] Rely on existing coupling points and distance factor for proximity detection

3 participants