Visible boundaries prevent a mesh containing these families from being mistaken for an ordinary supported route.
01 Model and scope
This sheet is a fail-closed boundary: a mesh containing an unsupported or research-only family must not be silently treated as a supported continuum model. No interpolation or stiffness formula is advertised as a public production route here.
This is a scope record. Its presence in the catalogue does not make the described route an ordinary supported capability.
Route assumptions and calculation checks
- Pyramid5 is internal/research-only, not a public supported-element claim.
- WEDGE15 is unsupported.
- No formulation card implies a mesh converter may silently replace either family.
Useful foundations and prerequisites
02 Essential equations and symbols
This sheet records a scope or execution boundary. Its detailed steps explain the relevant conditions.
Definitions and conventions
- PYRAMID5
- Internal/research-only family in the public maturity map.
- WEDGE15
- Unsupported family.
- RESEARCH_ONLY
- Implementation presence does not establish a supported route.
03 Step by step derivation
Follow the assumptions, equations and discrete operations in order. The full explanation stays visible.
Pyramid5 · internal research boundary
Pyramid5 may exist in internal or research code, but the public maturity map does not declare it a supported production continuum element. Therefore this sheet intentionally does not publish an interpolation or stiffness equation as though it were an accepted route. Implementation presence is not evidence of mesh, Jacobian, patch, convergence, or solver qualification.
Before using this family, inspect the capability row and confirm that import/validation fails closed when the family is outside the selected route.
WEDGE15 · unsupported family
WEDGE15 is marked unsupported. There is no public formulation equation to derive and no evidence permitting the solver to silently replace it with WEDGE6 or another cell. A valid workflow must identify the element type during mesh import and stop with a clear unsupported-family diagnostic before assembly.
The right next step is a separate element-development and verification effort: topology/node ordering, shape functions, geometry validity, strain operator, quadrature, loads/mass, patch tests, convergence, and named route evidence.
04 Algorithm and implementation
This sheet provides explanatory references rather than an inline source excerpt. Use the labeled sources to inspect the precise boundary.
05 Verification and limitations
PYRAMID5 RESEARCH_ONLY · WEDGE15 UNSUPPORTED
Each reference supports its own model, observable and analysis route. Read the original contract and limitations before transferring a conclusion.