Files
FESADev/phases/1-linear-static-mitc4-rebaseline/step1.md
T
2026-05-04 12:15:07 +09:00

62 lines
2.2 KiB
Markdown

# Sprint Contract: Reference Onboarding
## Objective
Create a Phase 1 reference path for `quad_02` without modifying the original Abaqus artifact or silently expanding parser support.
## Required Reading
- /AGENTS.md
- /PROGRESS.md
- /PLAN.md
- /docs/ABAQUS_INPUT_SUBSET.md
- /docs/VERIFICATION_PLAN.md
- /docs/RESULTS_SCHEMA.md
- /docs/MITC4_FORMULATION.md
- /references/quad_02.inp
- /references/quad_02_displacements.csv
## Scope
- Inspect `quad_02` and document its supported and unsupported features.
- Add a normalized Phase 1-compatible derivative input if selected by the planner, keeping the original `quad_02.inp` unchanged.
- Add notes or manifest metadata for unit system, source solver, expected outputs, and tolerances.
## Allowed Files
- `references/`
- `docs/ABAQUS_INPUT_SUBSET.md`
- `docs/VERIFICATION_PLAN.md`
- `PLAN.md`
- `PROGRESS.md`
- `tests/` only for reference artifact parsing/comparator tests
## Explicit Non-Goals
- Do not implement `Part`, `Assembly`, or `Instance` parser support in this step unless this contract is revised first.
- Do not edit `references/quad_02.inp` or `references/quad_02_displacements.csv`.
- Do not compare solver displacements until the MITC4 rebuild and end-to-end workflow are complete.
## Tests To Write First
- Test that original `quad_02.inp` is recognized as stored provenance with unsupported `Part/Assembly/Instance`.
- If a normalized input is added, test that it contains only the documented Phase 1 subset.
- Test `quad_02_displacements.csv` column loading and 121-row node-label parsing.
## Reference Artifacts
- `references/quad_02.inp`
- `references/quad_02_displacements.csv`
## Acceptance Commands
```bash
python scripts/validate_workspace.py
```
## Evaluator Checklist
- Original Abaqus files are preserved.
- Any normalized derivative file has a clear name and provenance note.
- Parser scope remains aligned with `docs/ABAQUS_INPUT_SUBSET.md`.
- Tolerances and result mapping are documented before regression use.
## Handoff Requirements
- Update `PROGRESS.md` with reference files changed or added.
- Update `PLAN.md` if parser compatibility remains blocked.
## Do Not
- Do not treat `*Density` as material support.
- Do not allow `Part/Assembly/Instance` through the Phase 1 parser accidentally.