Skip to content

fix: Use correct precision from input mesh when generating fractures #204

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.

Sign up for GitHub

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

Merged
alexbenedicto merged 1 commit into from
Dec 15, 2025
Merged

fix: Use correct precision from input mesh when generating fractures #204

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions mesh-doctor/src/geos/mesh_doctor/actions/generateFractures.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -418,6 +418,7 @@ def __performSplit( oldMesh: vtkUnstructuredGrid, cellToNodeMapping: Mapping[ in
# Creating the new points for the new mesh.
oldPoints: vtkPoints = oldMesh.GetPoints()
newPoints = vtkPoints()
newPoints.SetDataType( oldPoints.GetDataType() ) # Preserve precision from input mesh
newPoints.SetNumberOfPoints( numNewPoints )
collocatedNodes = ones( numNewPoints, dtype=int ) * -1
# Copying old points into the new container.
Expand Down Expand Up @@ -528,6 +529,7 @@ def __generateFractureMesh( oldMesh: vtkUnstructuredGrid, fractureInfo: Fracture
fractureNodes: Collection[ int ] = tuple( filter( lambda n: n > -1, fractureNodesTmp ) )
numPoints: int = len( fractureNodes )
points = vtkPoints()
points.SetDataType( meshPoints.GetDataType() ) # Preserve precision from input mesh
points.SetNumberOfPoints( numPoints )
node3dToNode2d: dict[ int, int ] = {} # Building the node mapping, from 3d mesh nodes to 2d fracture nodes.
for i, n in enumerate( fractureNodes ):
Expand Down