High order hexes done -> order 6
order 7->9 seem to be wrong : the way shape functions are computed is maybe numerically unstable
Showing
- CMakeLists.txt 4 additions, 1 deletionCMakeLists.txt
- Common/GmshDefines.h 16 additions, 4 deletionsCommon/GmshDefines.h
- Common/GmshMessage.cpp 1 addition, 0 deletionsCommon/GmshMessage.cpp
- Geo/MElement.cpp 29 additions, 7 deletionsGeo/MElement.cpp
- Geo/MHexahedron.cpp 86 additions, 0 deletionsGeo/MHexahedron.cpp
- Geo/MHexahedron.h 141 additions, 1 deletionGeo/MHexahedron.h
- Mesh/HighOrder.cpp 316 additions, 105 deletionsMesh/HighOrder.cpp
- Mesh/highOrderSmoother.cpp 222 additions, 1 deletionMesh/highOrderSmoother.cpp
- Mesh/highOrderSmoother.h 5 additions, 0 deletionsMesh/highOrderSmoother.h
- Mesh/meshGFaceOptimize.cpp 2 additions, 2 deletionsMesh/meshGFaceOptimize.cpp
- Mesh/qualityMeasures.cpp 1 addition, 0 deletionsMesh/qualityMeasures.cpp
- Numeric/polynomialBasis.cpp 281 additions, 20 deletionsNumeric/polynomialBasis.cpp
- Numeric/polynomialBasis.h 2 additions, 2 deletionsNumeric/polynomialBasis.h
- Solver/elasticityTerm.cpp 169 additions, 4 deletionsSolver/elasticityTerm.cpp
- Solver/elasticityTerm.h 71 additions, 0 deletionsSolver/elasticityTerm.h
- Solver/functionSpace.h 1 addition, 1 deletionSolver/functionSpace.h
- benchmarks/3d/Sphere.geo 1 addition, 1 deletionbenchmarks/3d/Sphere.geo
- benchmarks/extrude/u_shape_boundary_layer.geo 3 additions, 3 deletionsbenchmarks/extrude/u_shape_boundary_layer.geo
Loading
Please register or sign in to comment