2.9 KiB
2.9 KiB
Step 8: validation-readiness
Read First
/AGENTS.md/docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md/docs/ARCHITECTURE.md/docs/ADR.md/.codex/skills/abaqus-subroutine-validation/SKILL.md/.codex/skills/abaqus-subroutine-physics-sanity/SKILL.md/.codex/skills/abaqus-subroutine-readiness/SKILL.md/docs/requirements/uel-3d-euler-beam.md/docs/formulations/uel-3d-euler-beam.md/docs/io-definitions/uel-3d-euler-beam.md/docs/reference-models/uel-3d-euler-beam.md/docs/build-test-reports/uel-3d-euler-beam-green.md/tests/fortran/manifest.json
Task
Audit implementation readiness and define the handoff for external Abaqus validation.
Create or update:
/docs/reference-verifications/uel-3d-euler-beam.md/docs/physics-evaluations/uel-3d-euler-beam.md/docs/releases/uel-3d-euler-beam.md
The audit must include:
- Traceability from must requirements to tests and evidence.
- No-Abaqus Fortran validation results.
- Reference artifact status for each planned external model.
- Exact files the user must provide from an Abaqus PC:
model.inp, extracted CSV files,.msg/.dat/.log/.statails, metadata, source hashes, compiler version, Abaqus version, and extraction provenance. - Physics sanity checks expected after CSV artifacts are supplied: displacement direction, reaction equilibrium, bending/torsion/axial trends, finite values, units, and coordinate systems.
- Known limitations from the requirements and formulation documents.
- Release readiness decision:
ready-for-external-reference,blocked, ornot-ready.
If approved external reference artifacts already exist under references/uel-3d-euler-beam/, validate them using the scripts and summarize the result. If they do not exist, do not fabricate them; mark solver-result validation as waiting for user-provided external artifacts while still completing the no-Abaqus readiness audit.
Tests To Write First
- None unless the audit finds a missing no-Abaqus requirement. If so, add a targeted test first and return to implementation only if needed.
Acceptance Criteria
python -m unittest discover -s scripts -p "test_*.py"
python scripts/validate_fortran.py
python scripts/validate_reference_artifacts.py
python scripts/validate_workspace.py
The step is complete only when the release/readiness documents distinguish passed no-Abaqus evidence from pending external Abaqus CSV evidence.
Validation Notes
- Use externally generated ODB-extracted CSV artifacts for solver-result validation evidence.
- Do not run Abaqus analyses from this project.
- Update
/phases/uel-3d-euler-beam/index.jsonstep 8 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 mark solver-result validation complete without ready-for-comparison artifacts.
- Do not break existing tests.