NINI
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
---
|
|
description: Guide or validate addition of a new stored reference benchmark.
|
|
---
|
|
|
|
# /benchmark-add
|
|
|
|
## Preflight
|
|
|
|
- Read `/AGENTS.md`, `/PROGRESS.md`, `/PLAN.md`, `/docs/VERIFICATION_PLAN.md`, `/docs/RESULTS_SCHEMA.md`, and `/docs/ABAQUS_INPUT_SUBSET.md`.
|
|
- Use `$fesa-reference-onboarding` when available.
|
|
- Do not run Abaqus locally.
|
|
|
|
## Task
|
|
|
|
- Help organize the benchmark input, solved reference values such as `*_displacements.csv`, tolerance metadata, unit notes, result fields, and provenance.
|
|
- Check that Abaqus keywords are within the Phase 1 subset or explicitly documented as unsupported.
|
|
- Ensure comparison values can be tied to step/frame/field/history result paths.
|
|
|
|
## Verification
|
|
|
|
- Parse any JSON metadata if present.
|
|
- For `*_displacements.csv`, check the required Abaqus displacement/rotation columns.
|
|
- Run `python scripts/validate_workspace.py` when files are changed.
|
|
|
|
## Result
|
|
|
|
- **Action**: added or validated benchmark artifact
|
|
- **Status**: ready | partial | blocked
|
|
- **Details**: benchmark name, files, missing metadata, and validation result
|