跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

pfc5-asphalt-workflow

Orchestrate PFC2D/PFC3D 5.0 asphalt-mixture case handoff, specimen generation, fistPkg26 integration, Burger calibration, Marshall or rutting tests, validation, and reproducible delivery; use whenever a user mentions PFC5 asphalt, AC mixtures, fistPkg, Marshall, wheel tracking, or rutting.

Echo-aloha · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Echo-aloha/asphalt-codex-skills-5 --skill pfc5-asphalt-workflow

技能说明


name: pfc5-asphalt-workflow description: Orchestrate PFC2D/PFC3D 5.0 asphalt-mixture case handoff, specimen generation, fistPkg26 integration, Burger calibration, Marshall or rutting tests, validation, and reproducible delivery; use whenever a user mentions PFC5 asphalt, AC mixtures, fistPkg, Marshall, wheel tracking, or rutting.

PFC5 Asphalt Workflow

Use this skill as the primary entrypoint for a complete asphalt-mixture task that targets PFC 5.0. Keep the PFC5 case internally version-pure and route narrow work to the sibling skills listed below.

When to use

Use this skill when the request includes one or more of:

  • PFC2D/PFC3D 5.0 asphalt, asphalt concrete, AC-13/16/20, mastic, aggregate or voids;
  • fistPkg/FISHTank material generation or its compression, diametral or tension tests;
  • Burger viscoelastic contacts for asphalt mortar;
  • Marshall stability/flow or wheel-tracking/rutting;
  • auditing an existing asphalt case for unsupported-version contamination.
  • migrating, restoring, or resuming an existing private PFC5 asphalt case.

If the user targets another PFC major version, stop and state that this package is out of scope; do not route to a removed sibling or translate commands implicitly.

Required inputs

Before production code, obtain or mark as unresolved:

  1. product (PFC2D or PFC3D 5.0); do not require a particular PFC5.0 subversion;
  2. unit system and stress/strain sign convention;
  3. test type and the complete standard method chain (sampling, preparation, forming, density/void, performance and field-validation methods), including whether a legacy 2011 method must be reproduced;
  4. specimen geometry and dimensional idealization;
  5. sieve-by-sieve gradation, constituent densities, binder/aggregate convention and target air-void content;
  6. aggregate representation (balls/clumps) and minimum resolvable particle size;
  7. contact-pair hypothesis and calibrated macro targets at the test temperature/rate;
  8. legal <FISTPKG_ROOT>, PFC runtime route and run budget;
  9. required saves, histories, raw exports, figures and acceptance tolerances.

Never silently invent missing gradation, standard values, Burger parameters, or measured targets.

Version and evidence gates

Read version-matrix.md, fistpkg-contract.md, and standards-policy.md before writing a case. Use standards-method-map.md to classify each standard as a material method, design input, field validation method or acceptance context. Use standards-source-ledger.json to bind reviewed method claims to a source edition, printed-page locator and file digest without bundling the standards text.

  • PFC5 uses its own cmat, wall and FISH syntax. Reject unsupported newer-major command families instead of attempting an implicit port.
  • Run scripts/check_fistpkg.py "<FISTPKG_ROOT>" before relying on fistPkg.
  • Treat the user's licensed fistPkg files as external inputs. Never vendor their FISH, DLL, PDFs, projects or saves into this skill package.
  • The checker proves file compatibility only. A case is not validated until PFC executes a minimal syntax probe and the intended pilot case.

Workflow

P-1 — Audit an existing private case

When the request starts from an existing project, route first to pfc5-case-handoff. Protect the source, freeze included/excluded branches, verify integrity and portable dependencies, then restore the claimed last-good save and run a bounded audit before any full rebuild. Keep accepted, restart-only, diagnostic-only and obsolete states distinct. Skip this phase for a genuinely new case.

P0 — Freeze the case contract

Copy pfc5-asphalt-intake.yaml into the case directory and complete it. Record every value with units and provenance. Every method_chain item is an independent source record; do not reuse one global edition, source ID or reviewer across aggregate, forming, performance and field methods. Repeat a role when several methods or project records contribute, and use not_applicable rather than deleting a required role.

P1 — Choose the material abstraction

Route to pfc-asphalt-mixture.

  • A homogenized-mastic route normally uses explicit aggregate particles/clumps, unresolved mastic represented by contact laws, and residual pore space.
  • An explicit fine-particle route adds resolvable fine aggregate/filler particles; it is not automatically a literal three-particle-phase binder model.
  • Document which real phase each object/contact represents and what the model cannot resolve.

Perform volume and mass closure before particle generation. Do not assume nominal sieve fractions equal DEM particle radii.

P2 — Build and compact

Route the command skeleton, staged saves, contact installation order and static version audit to pfc5-core-modeling. Route reusable controllers, histories and callbacks to pfc5-fish; every callback still needs a minimal PFC5 runtime probe.

Use separate PFC5 stages:

00_parameters
10_boundaries
20_aggregate_generation
30_settle_or_expand
40_compact
50_install_final_contacts
60_equilibrate_and_instrument
70_test
80_export_and_verify

At every milestone record seed, particle/clump counts, mass/volume closure, void content, coordination/contact counts, equilibrium metric and save name. A target height alone does not prove target void content.

P3 — Install and calibrate contacts

Route Burger work to pfc-burger-viscoelastic and fistPkg baseline tests to pfc-fishtank-tests. Use pfc5-servo-calibration for wall-servo sign probes, gain bounds, parameter ledgers, guarded two-target updates and independent-case confirmation.

  1. verify a two-body or small-RVE contact probe in a PFC5.0 runtime;
  2. separate existing-contact reassignment from future-contact defaults;
  3. equili
阅读完整来源 ↗