القائمة
Use when the user asks to debug Dirac_solver execution, verify OpenClaw execution capability, or validate state synchronization across queue, bridge, and progress sync files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when running Octopus DFT/TDDFT calculations — select optimal mpirun -np and ParStates/ParDomains/OMP configuration for the system size. For new molecules or large systems, run a quick parallel scaling benchmark first.
Use when the user asks to debug Dirac_solver execution, verify OpenClaw execution capability, or validate state synchronization across queue, bridge, and progress sync files.
Use for Dirac execution stage to run harness and Octopus with endpoint fallback and audit artifacts.
Use for Dirac benchmark planning when selecting case scope, tolerance gates, and execution budgets before running harness/Octopus.
Use for strict production gate reviews of Dirac orchestration outputs across physics quality, KB quality, UI readiness, and contract completion.
Use when the user asks to build, refresh, validate, or inspect the Dirac DFT/TDDFT vector knowledge base, including ingestion status and retrieval quality.
| name | dirac-debug-ops |
| description | Use when the user asks to debug Dirac_solver execution, verify OpenClaw execution capability, or validate state synchronization across queue, bridge, and progress sync files. |
scripts/run_dirac_debug_ops.py# Snapshot only (non-intrusive)
python scripts/run_dirac_debug_ops.py --mode snapshot
# Dispatch only (route + execute)
python scripts/run_dirac_debug_ops.py --mode dispatch --task "Dirac_solver 调试" --execute --auto-replan
# Full check: snapshot -> dispatch -> snapshot
python scripts/run_dirac_debug_ops.py --mode full --task "Dirac_solver 调试 /auto smoke" --execute --auto-replan
pid, alive).execution_bus.last_task snapshot.state/dirac_solver_progress_sync.json) phase/checks.step, time, total_energy)--mode snapshot first when diagnosing production issues.dispatch_status and failure_reason from tool output.