2.2 KiB
2.2 KiB
Step 3: numerical-review
Read First
/AGENTS.md/docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md/docs/ARCHITECTURE.md/docs/ADR.md/.codex/skills/abaqus-subroutine-numerical-review/SKILL.md/docs/requirements/uel-3d-euler-beam.md/docs/research/uel-3d-euler-beam-research.md/docs/formulations/uel-3d-euler-beam.md/docs/numerical-reviews/README.md
Task
Create /docs/numerical-reviews/uel-3d-euler-beam.md.
Independently review the formulation before any implementation. Check:
- Local stiffness matrix completeness, units, symmetry, and positive semidefiniteness before boundary conditions.
- Rigid-body mode count for a free two-node 3D beam.
- Correct association of
Iy,Iz, local bending planes, and rotational DOFs. - Transformation orthonormality and behavior for reversed node order.
- Residual sign convention for Abaqus
UEL. - Tolerance choices for degeneracy and floating-point checks.
- Patch, cantilever, axial, torsion, and orientation regression tests needed downstream.
Record each finding as pass, needs-change, or blocked. If the formulation needs correction, update only the numerical review document with explicit required upstream changes and mark this phase step blocked; do not silently patch formulation content in this review step.
Do not create or modify Fortran source, tests, reference artifacts, or implementation plans in this step.
Tests To Write First
- None. This is a numerical review artifact step.
Acceptance Criteria
python -m unittest discover -s scripts -p "test_*.py"
python scripts/validate_reference_artifacts.py
python scripts/validate_workspace.py
The step is complete only when /docs/numerical-reviews/uel-3d-euler-beam.md gives a clear proceed/block decision for implementation readiness.
Validation Notes
- Downstream implementation must not override a blocked numerical finding.
- Update
/phases/uel-3d-euler-beam/index.jsonstep 3 withcompleted,error, orblockedand a concrete summary or reason.
Forbidden
- Do not add JavaScript/TypeScript/npm fallback.
- Do not run Abaqus analyses from this project.
- Do not generate reference CSVs.
- Do not create Fortran production source.
- Do not break existing tests.