docs: align FESA agents with minimal reference cases
This commit is contained in:
KOKO\Mimi
@@ -1,11 +1,13 @@
|
||||
---
|
||||
name: fesa-reference-models
|
||||
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required Abaqus reference CSV files, coverage matrices, and implementation-planning handoffs.
|
||||
description: Use when a FESA feature needs existing Abaqus input/CSV reference cases, required comparison quantities, tolerance mapping, or implementation-planning handoff.
|
||||
---
|
||||
|
||||
# FESA Reference Models
|
||||
# FESA Reference Cases
|
||||
|
||||
Use this skill to define test model portfolios and reference artifact contracts before implementation planning.
|
||||
Use this skill to inventory the minimum stored reference inputs and CSV quantities that a
|
||||
feature actually compares. Abaqus is an external numerical reference, not the FESA formulation
|
||||
or behavior specification.
|
||||
|
||||
## Inputs
|
||||
|
||||
@@ -15,56 +17,67 @@ Read these first:
|
||||
- `docs/SOLVER_AGENT_DESIGN.md`
|
||||
- `docs/reference-models/README.md`
|
||||
- `docs/requirements/<feature-id>.md`
|
||||
- `docs/research/<feature-id>-research.md`
|
||||
- `docs/formulations/<feature-id>-formulation.md`
|
||||
- `docs/numerical-reviews/<feature-id>-review.md`
|
||||
- `docs/io-definitions/<feature-id>-io.md`
|
||||
- Existing files under `reference/`
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Define reference strategy: code verification, solution verification, and benchmark/reference comparison.
|
||||
2. Build a model inventory: smoke, analytical, patch test, benchmark, regression, and negative/invalid-input models.
|
||||
3. For each model, record `model_id`, purpose, verified requirements, analysis type, element type, material, boundary conditions, loads, expected quantities, tolerance, source, and status.
|
||||
4. Define `reference/<model-id>/` artifact bundle requirements.
|
||||
5. Require `model.inp`, the applicable `<model-id>_displacements.csv`, `<model-id>_reactions.csv`, `<model-id>_internalforces.csv`, `<model-id>_stresses.csv`, and `README.md` unless explicitly not applicable. Treat `metadata.json` as optional.
|
||||
6. Define optional `<model-id>_strains.csv`, `<model-id>_energy_or_residual.csv`, and `<model-id>_<quantity>.csv` only when upstream acceptance criteria require them.
|
||||
7. Define metadata provenance, units, coordinate system, output requests, artifact status, reference_csv_schema_version, reference_csv_files, and limitations in the Reference Model Contract. If `metadata.json` exists, inventory it read-only and cross-check overlapping fields.
|
||||
8. Build a Coverage Matrix mapping requirement id, model id, compared quantity, FESA HDF5 dataset, reference CSV file, tolerance, verification method, and status.
|
||||
1. Read the feature requirements and list only blocking and warning-only reference quantities.
|
||||
2. Inventory each existing case using its exact directory, input filename, and required CSV filenames.
|
||||
3. Confirm the input and every required comparison CSV are present and readable.
|
||||
4. Record the FESA HDF5 dataset, source identity column, required component columns, and stable matching rule.
|
||||
5. Require unique source IDs, complete required row sets, and finite comparison values.
|
||||
6. Copy the approved tolerance and blocking/warning behavior without inventing or calibrating values.
|
||||
7. Map each reference-comparison requirement to at least one existing case when the feature requires that coverage.
|
||||
|
||||
Do not require or create:
|
||||
|
||||
- canonical directories or filenames;
|
||||
- legacy-alias approvals;
|
||||
- bundle `README.md` or `metadata.json`;
|
||||
- Abaqus version or generation provenance;
|
||||
- duplicated units, coordinates, step/frame, material, section, thickness, or element-type metadata;
|
||||
- a reference CSV schema version;
|
||||
- CSV files for quantities outside the approved comparison boundary;
|
||||
- an expanded benchmark portfolio unless the feature requirements explicitly require it.
|
||||
|
||||
Read source element type, material, section, loads, constraints, and supported single-step
|
||||
identity from the `.inp`. Do not rename, repair, normalize, or generate reference artifacts.
|
||||
|
||||
## Output Contract
|
||||
|
||||
Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
|
||||
|
||||
- Metadata
|
||||
- Reference Strategy
|
||||
- Model Inventory
|
||||
- Model Record
|
||||
- Abaqus Input Requirements
|
||||
- Artifact Bundle Contract
|
||||
- Reference Metadata Contract and optional `metadata.json` cross-check
|
||||
- Abaqus Reference CSV Requirements
|
||||
- Coverage Matrix
|
||||
- Artifact Acceptance Checklist
|
||||
- Reference Acceptance Scope
|
||||
- Reference Case Inventory
|
||||
- HDF5-to-CSV Comparison Mapping
|
||||
- Tolerance and Blocking/Warning Policy
|
||||
- Readiness Checklist
|
||||
- Open Issues and Downstream Handoff
|
||||
|
||||
## Boundaries
|
||||
|
||||
- Do not implement code.
|
||||
- Do not implement parsers.
|
||||
- Do not implement code or parsers.
|
||||
- Do not design C++ APIs or file ownership.
|
||||
- Do not run Abaqus, Nastran, or any reference solver.
|
||||
- Do not generate or modify Abaqus reference CSV files.
|
||||
- Do not run Abaqus, Nastran, or another reference solver.
|
||||
- Do not generate or modify reference inputs or CSV files.
|
||||
- Do not compare solver results.
|
||||
- Do not approve release readiness.
|
||||
|
||||
## Quality Gate
|
||||
|
||||
- Every `must` requirement maps to at least one model and compared quantity.
|
||||
- `model.inp` stays within the supported Abaqus keyword subset or records an open issue.
|
||||
- The Reference Model Contract includes provenance, Abaqus version/source, units, coordinate system, tolerance, reference_csv_schema_version, and reference_csv_files.
|
||||
- An absent `metadata.json` is allowed and does not change readiness. A present file is read-only supplementary evidence; any conflict with the contract or stored artifacts remains visible as an upstream issue.
|
||||
- Missing required Abaqus reference CSV files keep the model at `needs-reference-artifacts`.
|
||||
- Every blocking or warning-only quantity names an exact input/CSV pair.
|
||||
- Every comparison defines an HDF5 projection, source-ID/component mapping, and tolerance.
|
||||
- Missing, extra, duplicate, and nonfinite required rows have an explicit fail-before-tolerance rule.
|
||||
- Use `needs-reference-artifacts` only when a declared input or required comparison CSV is missing.
|
||||
- Use `needs-user-decision` only when required quantities, matching, or tolerance are undefined.
|
||||
- Canonical naming, README, metadata, provenance, and unrequested portfolio coverage never block readiness.
|
||||
|
||||
## Handoff
|
||||
|
||||
Send model order and tests that should fail first to Implementation Planning Agent. Send FESA HDF5 dataset paths, reference CSV schemas, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
|
||||
Send exact paths, HDF5 projection, source-ID/component matching, row prechecks, and tolerance to
|
||||
Implementation Planning Agent and Reference Verification Agent. Send only feature-required
|
||||
physical expectations to Physics Evaluation Agent.
|
||||
|
||||
Reference in New Issue
Block a user