3D beam distributed load : SOFA vs FF cross-validation#39
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends the 2D distributed-load cross-validation (cantilever beam, no analytical
solution) to 3D with a tetrahedral mesh. The load is applied as a surface traction
(Neumann) on the Top face, equivalent to the FreeFEM term
int2d(Th,4)(-Q*vy).No plane-strain/plane-stress distinction is needed here since the full 3D volume
is modeled directly.
Files
beam3dtet.py— Gmsh tetrahedral mesh generator for the 3D beam (box geometry,physical tags: 1=Fixed, 2=Bottom, 3=Right, 4=Top, 5=Front, 6=Back, 7=Beam volume)
freefem_beam3d_distributed.edp— full 3D bilinear form (int3d, all cross-shearterms), Neumann load via
int2d(Th,4), mesh loaded withgmshload3comparaison_script3d.py— SOFA vs FreeFEM comparison, coordinate-based nodematching, separate RMS on ux/uy/uz, parity plots
params_beam3d_distributed.json— physical parameters (same as the 2D case)Bug fixed: non-conforming mesh
setTransfiniteVolume()was used together with triangulated (non-recombined)boundary surfaces. Transfinite volume meshing picks its own internal diagonal
split, independent of the diagonals already chosen by the transfinite surface
mesh — the two are not guaranteed to agree, which produced boundary triangles
not matching any tetrahedron face (
Border element not in meshin FreeFEM).Fix: removed
setTransfiniteVolume(). Surfaces stay transfinite (controlled,structured boundary mesh); the volume is filled by the standard (Delaunay)
3D algorithm, which is constrained to respect the already-fixed boundary mesh
exactly. Conformity confirmed via
check_mesh_conformity.pyat multipleresolutions (all 6 tagged faces OK).