Testing
AuraScore 81/100

Stochastic Simulation Validation Matrix

Validate high-dimensional Monte Carlo simulations through convergence stress testing and variance reduction analysis.

Use this template when assessing statistical modeling engines, financial pricing algorithms, or physics simulations. It generates a structured testing grid that measures estimator convergence rates and boundary performance.

Template

Role: Lead Quantitative Validation Analyst specializing in stochastic calculus and numerical simulation testing.

Context

  • Simulation Engine Core: {{simulation_engine}}
  • Stochastic Input Parameters: {{stochastic_variables}}
  • Convergence Criteria: {{convergence_criteria}}
  • Variance Reduction Schemes: {{variance_reduction_methods}}
  • Computational Sample Limits: {{sample_scale_limits}}
  • Reference Datasets: {{historical_baseline_data}}

Task

Construct a comprehensive Monte Carlo and Stochastic Simulation Validation Matrix to rigorously benchmark convergence behavior, estimator bias, variance reduction efficacy, and extreme-quantile stability across high-dimensional parameter spaces.

Method

  1. Discretize the stochastic processes governed by {{stochastic_variables}} into measurable dimensional states and paths.
  2. Establish the theoretical asymptotic convergence rates for {{simulation_engine}} based on the chosen discretization scheme.
  3. Cross-reference each variance reduction technique in {{variance_reduction_methods}} against high-kurtosis and fat-tailed regimes.
  4. Define stress-test parameter sweeps that push input variables to their mathematical limits (e.g., extreme volatility, near-zero correlation).
  5. Map convergence stability across sample sizes defined in {{sample_scale_limits}} to identify optimal batching sizes and bias cliffs.
  6. Formulate backtesting verification rows that compare output distributions against {{historical_baseline_data}}.
  7. Populate the matrix with explicit statistical goodness-of-fit tests (Kolmogorov-Smirnov, Anderson-Darling, Chi-Square).
  8. Detail standard error upper bounds and confidence interval coverage rates matching {{convergence_criteria}}.

Constraints

  • MUST evaluate both path-dependent and terminal-state convergence behaviors separately in the matrix.
  • MUST NOT omit extreme quantile tests (e.g., 99.9th percentile value-at-risk or tail-loss scenarios).
  • All test vectors MUST specify sample path counts, seed generation policies, and pseudorandom generator requirements.
  • Execution costs per matrix cell must stay strictly within {{sample_scale_limits}}.

Output format

Deliver the testing documentation in three precise sections:

  1. Theoretical Bound Specification: Mathematical formulation of expected estimator variance and convergence order.
  2. Simulation Testing Matrix: Table containing Test Scenario ID, Stochastic Parameter Regime, Sample Size (N), Variance Reduction Tactic, Goodness-of-Fit Metric, and Acceptance Threshold.
  3. Boundary Degradation Playbook: Step-by-step guidance for diagnosing slow convergence, sample degeneration, and numerical bias.

Self-review

  • Verify all variables in {{stochastic_variables}} are subjected to stressed volatility and extreme correlation tests.
  • Confirm convergence tolerances directly align with {{convergence_criteria}}.
  • Ensure variance reduction methods are explicitly evaluated against raw crude Monte Carlo baselines.
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.

developers
developers-testing
complex-reasoning-analysis-math
monte-carlo
quantitative-finance
statistical-validation