PFC5 Marshall Stability and Flow
Use this skill after a load-ready specimen exists. The PFC5 fistPkg dc.fis
controller can provide a two-head setup/loading skeleton, but Marshall is not converted
into a validated test merely by replacing planar platens, and it must not be interpreted
as a Brazilian tensile-strength calculation.
When to use
- create or audit curved Marshall loading heads in PFC5;
- adapt a private fistPkg26 DiamCompTest working copy;
- extract load-deformation histories, peak load and edition-correct flow;
- compare PFC results against a laboratory Marshall test;
- diagnose wall IDs, axes, sign, head contact, smoothing or stopping logic.
Use pfc-asphalt-mixture for specimen generation and pfc5-asphalt-workflow for the
complete case.
Required inputs
- PFC2D/PFC3D 5.0 and the unit system;
- legal
<FISTPKG_ROOT> plus a passing dependency check/baseline run;
- governing standard edition, method ID and clauses;
- specimen dimensions, conditioning and test temperature;
- head geometry/radius/width and PFC5-compatible wall representation;
- prescribed loading rate/control mode and stop condition;
- head-particle contact properties and friction;
- definition/correction procedure for stability and flow;
- laboratory curve/targets, tolerances and desired crack/failure outputs.
For current work use JTG 3410-2025 T 0709-2025, effective 2025-10-01, and trace the
specimen to the selected T 0702-2025 forming route. JTG E20-2011 T0709 is retained only
for declared legacy reproduction. Do not mix current curve correction/reporting rules
with legacy apparatus or conditioning values.
Audited fistPkg26 contract
The inspected dc.fis:
- calls
_dcMakeWalls during dcSetupPhase;
- expects head pointers
dcWp0 and dcWp1, normally found from wall IDs 1 and 2;
- uses the second coordinate as axial position/velocity;
- initializes wall-force and wall-strain callbacks;
- can stop after force falls to a fraction of the recorded peak.
_dcMakeWalls is the minimum geometry hook. A complete adapter must also verify:
- wall IDs/pointers and head initial gap;
- curved-facet orientation, head translation and prohibited rotations;
- PFC5 wall import/generation syntax;
- current and future grain-head contact laws;
- suitability of
ft_SmoothGrainWallInterface;
- force, displacement and sign conventions in 2D/3D;
- peak capture, sampling rate and post-peak termination;
- edition-specific flow correction and unit conversion.
Workflow
- Run the unmodified fistPkg DiamCompTest baseline in a PFC5.0 runtime.
- Copy the project privately and preserve an upstream/change manifest.
- Replace the planar-head construction through a separately documented override.
- Run a no-particle/head-motion probe, then a small-particle contact probe.
- Install the actual specimen, remove unintended overlap without altering the intended
fabric, equilibrate and save the pre-load state.
- Initialize independent reaction-force and head-separation/displacement histories.
PFC5
wall.force.contact is the global-coordinate sum of contact forces acting on
each wall; keep both heads and verify their equal/opposite balance before deriving
a scalar load. Set a displacement reference explicitly because wall.disp is an
accumulated wall displacement and is writable.
- Load at the edition-specific rate; retain enough post-peak data for the selected stop
and flow procedure.
- Preserve the raw curve, apply the selected edition's origin correction, and branch
explicitly when the peak is not obvious; never replace the current correction with
raw peak displacement or a fixed post-peak fraction.
- Compare the full curve, peak/flow and failure pattern against laboratory data and run
seed/resolution/rate sensitivity.
Working rules
- Keep all case commands PFC5-pure; newer geometry/FISH syntax requires an explicit port.
- Do not claim
dc_wfa/dc_wda automatically equal final normative stability/flow;
independently audit sign, units, sampling and correction.
- Do not add the signed forces from two opposed heads and call the cancellation a
specimen load. Resolve both forces on the declared loading axis, compare magnitudes,
and state the scalar-load convention.
- Treat dry stability, immersed stability and vacuum-saturation stability as distinct
protocols. A dry DEM solve cannot be relabeled as water sensitivity.
- Do not claim that
_dcMakeWalls is the only required change.
- Keep setup, equilibrated pre-load and loaded milestone saves.
- If the standard text or runtime is unavailable, deliver the raw curve and mark the
normative result/runtime gate pending.
Output contract
- PFC2D/PFC3D 5.0, units, standard edition/method/clause and source manifest;
- specimen/head geometry and audited PFC5 head construction;
- wall/contact/control/stop parameter tables;
- baseline, no-particle and contact-probe results;
- load-deformation history, raw peak load/displacement and standard-corrected metrics;
- equilibrium and sensitivity evidence;
- laboratory validation and
runtime_validated status.
Local contents
references/overview.md — legacy fistPkg dc.fis parameters and adapter notes.
references/jtg-t0709-note.md — legacy 2011 checklist; not a current numeric source.
references/jtg-3410-2025-t0709.md — current method chain, raw/corrected curve contract and PFC5 mapping.
../pfc5-asphalt-workflow/references/standards-policy.md — current/legacy policy.
scripts/marshall_head_contact_pilot.p3dat — executable curved-head PFC3D 5.0 contact pilot; not a normative Marshall model.
dependencies.json — package-level sibling-skill assets required for the complete workflow.
agents/openai.yaml — Agent metadata.
1---2name: pfc-marshall-test3description: Adapt and audit a PFC 5.0 asphalt Marshall stability/flow simulation using the external fistPkg26 dc.fis two-head controller as a starting skeleton; use for curved-head geometry, PFC5 wall/contact kinematics, load-deformation histories, peak stability, edition-specific flow processing, and validation against laboratory data.4---56# PFC5 Marshall Stability and Flow78Use this skill after a load-ready specimen exists. The PFC5 fistPkg `dc.fis`9controller can provide a two-head setup/loading skeleton, but Marshall is not converted10into a validated test merely by replacing planar platens, and it must not be interpreted11as a Brazilian tensile-strength calculation.1213## When to use1415- create or audit curved Marshall loading heads in PFC5;16- adapt a private fistPkg26 DiamCompTest working copy;17- extract load-deformation histories, peak load and edition-correct flow;18- compare PFC results against a laboratory Marshall test;19- diagnose wall IDs, axes, sign, head contact, smoothing or stopping logic.2021Use `pfc-asphalt-mixture` for specimen generation and `pfc5-asphalt-workflow` for the22complete case.2324## Required inputs2526- PFC2D/PFC3D 5.0 and the unit system;27- legal `<FISTPKG_ROOT>` plus a passing dependency check/baseline run;28- governing standard edition, method ID and clauses;29- specimen dimensions, conditioning and test temperature;30- head geometry/radius/width and PFC5-compatible wall representation;31- prescribed loading rate/control mode and stop condition;32- head-particle contact properties and friction;33- definition/correction procedure for stability and flow;34- laboratory curve/targets, tolerances and desired crack/failure outputs.3536For current work use JTG 3410-2025 T 0709-2025, effective 2025-10-01, and trace the37specimen to the selected T 0702-2025 forming route. JTG E20-2011 T0709 is retained only38for declared legacy reproduction. Do not mix current curve correction/reporting rules39with legacy apparatus or conditioning values.4041## Audited fistPkg26 contract4243The inspected `dc.fis`:4445- calls `_dcMakeWalls` during `dcSetupPhase`;46- expects head pointers `dcWp0` and `dcWp1`, normally found from wall IDs 1 and 2;47- uses the second coordinate as axial position/velocity;48- initializes wall-force and wall-strain callbacks;49- can stop after force falls to a fraction of the recorded peak.5051`_dcMakeWalls` is the minimum geometry hook. A complete adapter must also verify:52531. wall IDs/pointers and head initial gap;542. curved-facet orientation, head translation and prohibited rotations;553. PFC5 wall import/generation syntax;564. current and future grain-head contact laws;575. suitability of `ft_SmoothGrainWallInterface`;586. force, displacement and sign conventions in 2D/3D;597. peak capture, sampling rate and post-peak termination;608. edition-specific flow correction and unit conversion.6162## Workflow63641. Run the unmodified fistPkg DiamCompTest baseline in a PFC5.0 runtime.652. Copy the project privately and preserve an upstream/change manifest.663. Replace the planar-head construction through a separately documented override.674. Run a no-particle/head-motion probe, then a small-particle contact probe.685. Install the actual specimen, remove unintended overlap without altering the intended69 fabric, equilibrate and save the pre-load state.706. Initialize independent reaction-force and head-separation/displacement histories.71 PFC5 `wall.force.contact` is the global-coordinate sum of contact forces acting on72 each wall; keep both heads and verify their equal/opposite balance before deriving73 a scalar load. Set a displacement reference explicitly because `wall.disp` is an74 accumulated wall displacement and is writable.757. Load at the edition-specific rate; retain enough post-peak data for the selected stop76 and flow procedure.778. Preserve the raw curve, apply the selected edition's origin correction, and branch78 explicitly when the peak is not obvious; never replace the current correction with79 raw peak displacement or a fixed post-peak fraction.809. Compare the full curve, peak/flow and failure pattern against laboratory data and run81 seed/resolution/rate sensitivity.8283## Working rules8485- Keep all case commands PFC5-pure; newer geometry/FISH syntax requires an explicit port.86- Do not claim `dc_wfa`/`dc_wda` automatically equal final normative stability/flow;87 independently audit sign, units, sampling and correction.88- Do not add the signed forces from two opposed heads and call the cancellation a89 specimen load. Resolve both forces on the declared loading axis, compare magnitudes,90 and state the scalar-load convention.91- Treat dry stability, immersed stability and vacuum-saturation stability as distinct92 protocols. A dry DEM solve cannot be relabeled as water sensitivity.93- Do not claim that `_dcMakeWalls` is the only required change.94- Keep setup, equilibrated pre-load and loaded milestone saves.95- If the standard text or runtime is unavailable, deliver the raw curve and mark the96 normative result/runtime gate pending.9798## Output contract99100- PFC2D/PFC3D 5.0, units, standard edition/method/clause and source manifest;101- specimen/head geometry and audited PFC5 head construction;102- wall/contact/control/stop parameter tables;103- baseline, no-particle and contact-probe results;104- load-deformation history, raw peak load/displacement and standard-corrected metrics;105- equilibrium and sensitivity evidence;106- laboratory validation and `runtime_validated` status.107108## Local contents109110- `references/overview.md` — legacy fistPkg dc.fis parameters and adapter notes.111- `references/jtg-t0709-note.md` — legacy 2011 checklist; not a current numeric source.112- `references/jtg-3410-2025-t0709.md` — current method chain, raw/corrected curve contract and PFC5 mapping.113- `../pfc5-asphalt-workflow/references/standards-policy.md` — current/legacy policy.114- `scripts/marshall_head_contact_pilot.p3dat` — executable curved-head PFC3D 5.0 contact pilot; not a normative Marshall model.115- `dependencies.json` — package-level sibling-skill assets required for the complete workflow.116- `agents/openai.yaml` — Agent metadata.