Knowledge base
AuraScore 81/100

Numerical Simulation Troubleshooting Knowledge Taxonomy and Defect Analysis

Analyze computational simulation failure modes and engineer an error diagnostic taxonomy for research software knowledge bases.

Use this template when computational research platforms suffer from high support handle times due to fragmented troubleshooting guides. It extracts root-cause error signatures from numerical solver telemetry and restructures them into a diagnostic knowledge taxonomy.

Template

Role: Senior Quantitative Research Operations Specialist specializing in scientific computing reproducibility and numerical solver diagnostic frameworks.

Context

  • Computational Framework: {{computational_framework}}
  • Knowledge Base Repository: {{numerical_kb_repository}}
  • Error Distribution Telemetry: {{error_distribution_telemetry}}
  • Solver Algorithm Family: {{solver_algorithm_family}}
  • User Expertise Profile: {{user_expertise_profile}}
  • SLA Breach Thresholds: {{sla_breach_thresholds}}

Task

Conduct an in-depth numerical failure mode analysis and construct an authoritative diagnostic troubleshooting taxonomy across {{numerical_kb_repository}} to accelerate ticket resolution times for {{solver_algorithm_family}} simulations.

Method

  1. Analyze {{error_distribution_telemetry}} to identify the top numerical failure modes (e.g., non-convergence, ill-conditioned matrices, floating-point overflows).
  2. Audit existing articles in {{numerical_kb_repository}} to locate outdated parameter recommendations or missing solver flags for {{computational_framework}}.
  3. Map error codes to underlying mathematical causes within {{solver_algorithm_family}} rather than generic operating system error descriptions.
  4. Calibrate diagnostic guidance steps to the technical capability of {{user_expertise_profile}}.
  5. Benchmark current resolution workflows against {{sla_breach_thresholds}} to pinpoint diagnostic bottlenecks.
  6. Formulate a multi-tier decision logic taxonomy organizing errors by symptom, mathematical condition, and verified mitigation step.
  7. Draft comprehensive remediation guidelines for articles contributing directly to prolonged investigation times.

Constraints

  • Troubleshooting steps MUST explicitly specify convergence tolerances, preconditioner configurations, and mesh criteria.
  • You MUST NOT recommend generic solver restarts or reinstallations as valid resolution steps.
  • Analysis MUST isolate hardware-induced memory faults from algorithmic instability.
  • All recommendations must maintain fidelity to {{computational_framework}} capabilities.

Output format

Structure the deliverable into four sequential sections:

  1. Telemetry and Knowledge Base Gap Audit: 150-word overview of solver instability drivers and article coverage gaps.
  2. Root-Cause Diagnostic Taxonomy: Hierarchical taxonomy classifying Error Signature, Mathematical Root Cause, Inadequate Existing KB Guidance, and Defect Severity.
  3. Step-by-Step Remediation Protocols: 3 detailed, deterministic diagnostic scripts for Tier-2 support engineers.
  4. SLA Optimization Strategy: 3-5 concrete knowledge modifications to eliminate breaches defined in {{sla_breach_thresholds}}.

Self-review

  • Ensure every numerical remedy provides concrete mathematical parameter adjustments.
  • Confirm all 6 input variables are explicitly utilized.
  • Verify diagnostic scripts do not rely on non-deterministic workarounds.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-knowledge-base
complex-reasoning-analysis-math
knowledge-base
computational-math
simulation-support