baram2584/FESADev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: reset mitc4 formulation baseline

Browse Source
This commit is contained in:
NINI
2026-05-04 12:00:16 +09:00
parent c5be1f988c
commit a385235e14
117 changed files with 5924 additions and 213 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PLAN.md
+11 -6
View File
@@ -13,7 +13,7 @@ Every new agent session must read this file together with `PROGRESS.md` before p
- If an item becomes obsolete, move it to `PROGRESS.md` with a short reason instead of silently deleting it.
## Current Objective
Resolve the remaining Phase 1 reference-artifact blockers after the P1-01 through P1-14 implementation pass: add Phase 1-compatible Abaqus `TYPE=S4` displacement references and decide the first RF reference path.
Rebaseline Phase 1 before any more implementation: use the revised `docs/MITC4_FORMULATION.md` as the MITC4 gate, decide how `references/quad_02.inp` should be handled despite its `Part/Assembly/Instance` structure, and draft new sprint contracts before reworking the solver.
## Required Reading For New Agents
1. `AGENTS.md`
@@ -37,13 +37,14 @@ Resolve the remaining Phase 1 reference-artifact blockers after the P1-01 throug
- Execute with: `python scripts/execute.py 1-linear-static-mitc4`
- Step numbering is zero-based for the harness: `step0.md` corresponds to milestone P1-01, and `step15.md` corresponds to milestone P1-16.
- Every step file contains a sprint contract with objective, scope, allowed files, tests-first plan, reference-artifact policy, evaluator checklist, acceptance command, and handoff requirements.
- Current phase status: blocked at P1-15 because no Phase 1-compatible Abaqus `TYPE=S4` reference input and matching displacement CSV are available yet.
- Current phase status: rebaseline required. Do not resume the old P1-15/P1-16 path until new contracts are drafted against the revised MITC4 formulation and the `quad_02` compatibility decision.
## Phase 1 Readiness Tasks
| ID | Status | Owner | Task | Source |
|---|---|---|---|---|
| R-010 | pending | user + verification agent | Add or define reaction-force reference artifacts, preferably `*_reactions.csv`, or decide that Phase 1 `RF` is verified by equilibrium tests until Abaqus RF CSV is available. | `docs/VERIFICATION_PLAN.md`, `docs/RESULTS_SCHEMA.md` |
| R-011 | pending | user + Abaqus compatibility agent | Add at least one Phase 1-compatible Abaqus `TYPE=S4` input case; keep `quad_01.inp` as stored S4R/NLGEOM reference provenance until S4R/nonlinear support is intentionally added. | `docs/ABAQUS_INPUT_SUBSET.md`, `docs/VERIFICATION_PLAN.md` |
| R-011 | partial | user + Abaqus compatibility agent | Review `references/quad_02.inp` and `references/quad_02_displacements.csv`: `TYPE=S4` is now available, but the input includes `Part/Assembly/Instance`, so decide whether to normalize the file into the current flat keyword subset or add a dedicated parser sprint. | `docs/ABAQUS_INPUT_SUBSET.md`, `docs/VERIFICATION_PLAN.md`, `docs/MITC4_FORMULATION.md` |
| R-012 | pending | planner + evaluator | Draft a Phase 1 redo plan and step contracts that replace or supersede the old P1-01 through P1-16 implementation path where it conflicts with the revised MITC4 formulation. | `docs/HARNESS_ENGINEERING.md`, `docs/MITC4_FORMULATION.md` |
## Phase 1 Definition Of Done
Phase 1 is complete only when FESA can run a documented linear static MITC4 workflow from input to verified results without requiring Abaqus execution.
@@ -74,8 +75,8 @@ Each gate should be satisfied before moving to the next implementation band unle
| G1 - Build and validation | satisfied | Build system, test framework, and `scripts/validate_workspace.py` run real checks. | Validation command output |
| G2 - Parser and domain | satisfied | Phase 1 `.inp` subset parses into `Domain`; unsupported features fail clearly. | Parser tests and diagnostics tests |
| G3 - DOF/math/results infrastructure | satisfied | Core types, DofManager, sparse math adapters, minimal results writer, and CSV comparator are tested. | Unit tests and schema/comparator tests |
| G4 - MITC4 element readiness | satisfied | MITC4 formulation open decisions are closed and element-level tests pass. | Updated formulation doc and element tests |
| G5 - End-to-end solver | partial | Linear static path writes `U`/`RF`; stored Phase 1-compatible Abaqus reference regression is blocked by missing artifacts. | Integration/reference regression output |
| G4 - MITC4 element readiness | reopened | MITC4 formulation was rewritten from local papers; the existing element tests must be reassessed and expanded before implementation is trusted. | Revised `docs/MITC4_FORMULATION.md`, future element tests |
| G5 - End-to-end solver | reopened | Linear static path must be revalidated after the MITC4 rebuild and after the `quad_02` compatibility path is decided. | Future integration/reference regression output |
## Phase 1 Implementation Milestones
All milestones are intended to become one or more self-contained sprint contracts or `phases/{phase}/stepN.md` files. Each sprint must follow `docs/HARNESS_ENGINEERING.md` and be evaluated independently.
@@ -113,15 +114,19 @@ Verification should grow with the implementation bands:
Current reference state:
- `references/quad_01.inp` and `references/quad_01_displacements.csv` are accepted stored artifacts.
- `quad_01.inp` contains `S4R`, `Part/Assembly/Instance`, `*Density`, and `NLGEOM=YES`; it is not a Phase 1 parser acceptance case as-is.
- `references/quad_02.inp` and `references/quad_02_displacements.csv` have been added by the user as an S4 reference pair.
- `quad_02.inp` uses `TYPE=S4`, but also includes `Part/Assembly/Instance`; this is a compatibility decision point, not automatic parser scope expansion.
Required reference additions or decisions:
- Add at least one Phase 1-compatible `TYPE=S4` linear static `.inp` case.
- Decide whether `quad_02.inp` is normalized into the current Phase 1 keyword subset or used to justify a dedicated Abaqus/CAE `Part/Assembly/Instance` parser sprint.
- Add `*_reactions.csv` or explicitly use internal equilibrium tests for Phase 1 `RF` until Abaqus RF output is available.
- Add more small cases until Phase 1 can pass one single-element case, one simple multi-element plate/shell case, and one curved shell benchmark.
## Phase 1 Risk Controls
- Do not implement MITC4 element stiffness until the formulation gate in `docs/MITC4_FORMULATION.md` is closed.
- Do not treat the previous P1-01 through P1-14 implementation as authoritative after the MITC4 formulation reset.
- Do not use `quad_01.inp` to justify `S4R`, `Part/Assembly/Instance`, or `NLGEOM=YES` support.
- Do not use `quad_02.inp` to silently justify `Part/Assembly/Instance` support without a parser contract.
- Do not compute reactions from reduced vectors only.
- Do not expose MKL, TBB, or HDF5 APIs directly in solver core.
- Do not narrow ids, equation numbers, or sparse indices below int64.