PFC5 Standard Tests
Use this skill for PFC5 material/calibration tests that support asphalt specimen
and contact-model validation. Prefer the legal external fistPkg baseline when its
test family fits.
Required Inputs
- PFC2D/PFC3D 5.0, units and sign convention;
- test type, geometry, boundary/contact assumptions and the complete standard method
chain, including specimen forming, density/void method and performance method;
- load/displacement/rate/hold/recovery path;
- required stress/strain definitions and experimental targets;
- external fistPkg root when used.
Workflow
- Select compression, diametral, direct tension, or creep-recovery.
For JTG 3410-2025 work, distinguish T 0713/T 0714 compression, T 0738 dynamic
modulus, T 0742 shear, T 0715 flexure, T 0716 splitting and T 0745 repeated
compression; do not infer one test from a generic controller name.
- Run the unmodified external fistPkg baseline when applicable.
- Prove boundary motion, wall IDs, axes and sign with a small pilot.
- Initialize duplicate force/displacement measures and histories before loading.
- Retain pre-load, peak/hold and final/recovery states.
- Export a stable CSV and run
scripts/extract_test_metrics.py.
- Compare the full curve and failure/deformation mode, not peak alone.
- Run seed, resolution, rate, timestep and boundary sensitivity.
Read test-contracts.md for measurement contracts.
Working Rules
- Marshall remains in
pfc-marshall-test; wheel tracking remains in pfc-rutting-test.
- Do not call a diametral controller a Marshall model without the Marshall geometry and metric contract.
- Test formulas require declared dimensional thickness/area conventions.
- The laboratory-method value, project acceptance threshold and DEM calibration target
are separate records even when they share a symbol.
- Offline metric extraction does not validate the PFC solve.
Output Contract
Return test definition, geometry/boundaries, histories, CSV schema, extracted
metrics, experimental comparison, sensitivity evidence and runtime status.
Local Contents
references/test-contracts.md — PFC5 calibration-test contracts.../pfc5-asphalt-workflow/references/standards-method-map.md — method-chain and standard-role routing.scripts/extract_test_metrics.py — deterministic curve/peak/stiffness extractor.agents/openai.yaml — interface metadata.
1---2name: pfc5-standard-tests3description: Plan, audit, and post-process PFC 5.0 asphalt calibration tests, including compression, diametral loading, direct tension, creep-recovery, test geometry, histories, peak metrics, stiffness, and fistPkg handoff.4---56# PFC5 Standard Tests78Use this skill for PFC5 material/calibration tests that support asphalt specimen9and contact-model validation. Prefer the legal external fistPkg baseline when its10test family fits.1112## Required Inputs1314- PFC2D/PFC3D 5.0, units and sign convention;15- test type, geometry, boundary/contact assumptions and the complete standard method16 chain, including specimen forming, density/void method and performance method;17- load/displacement/rate/hold/recovery path;18- required stress/strain definitions and experimental targets;19- external fistPkg root when used.2021## Workflow22231. Select compression, diametral, direct tension, or creep-recovery.24 For JTG 3410-2025 work, distinguish T 0713/T 0714 compression, T 0738 dynamic25 modulus, T 0742 shear, T 0715 flexure, T 0716 splitting and T 0745 repeated26 compression; do not infer one test from a generic controller name.272. Run the unmodified external fistPkg baseline when applicable.283. Prove boundary motion, wall IDs, axes and sign with a small pilot.294. Initialize duplicate force/displacement measures and histories before loading.305. Retain pre-load, peak/hold and final/recovery states.316. Export a stable CSV and run `scripts/extract_test_metrics.py`.327. Compare the full curve and failure/deformation mode, not peak alone.338. Run seed, resolution, rate, timestep and boundary sensitivity.3435Read [test-contracts.md](references/test-contracts.md) for measurement contracts.3637## Working Rules3839- Marshall remains in `pfc-marshall-test`; wheel tracking remains in `pfc-rutting-test`.40- Do not call a diametral controller a Marshall model without the Marshall geometry and metric contract.41- Test formulas require declared dimensional thickness/area conventions.42- The laboratory-method value, project acceptance threshold and DEM calibration target43 are separate records even when they share a symbol.44- Offline metric extraction does not validate the PFC solve.4546## Output Contract4748Return test definition, geometry/boundaries, histories, CSV schema, extracted49metrics, experimental comparison, sensitivity evidence and runtime status.5051## Local Contents5253- `references/test-contracts.md` — PFC5 calibration-test contracts.54- `../pfc5-asphalt-workflow/references/standards-method-map.md` — method-chain and standard-role routing.55- `scripts/extract_test_metrics.py` — deterministic curve/peak/stiffness extractor.56- `agents/openai.yaml` — interface metadata.
Echo-aloha