MCP HubMCP Hub
Volver a habilidades

simulate-stochastic-process

pjt222
Actualizado 2 days ago
7 vistas
17
2
17
Ver en GitHub
Metaaidesign

Acerca de

Esta habilidad simula procesos estocásticos como cadenas de Markov, caminos aleatorios y EDEs para estimación, predicción y visualización cuando no hay soluciones analíticas disponibles. Ofrece características clave que incluyen diagnósticos de convergencia, técnicas de reducción de varianza y visualización de trayectorias muestrales. Los desarrolladores deben usarla para estimación Monte Carlo con garantías, validar resultados analíticos o muestrear de posteriores complejos mediante MCMC.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/simulate-stochastic-process

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Simulate Stochastic Process

Simulate sample paths from stochastic processes -- discrete Markov chains, continuous-time processes, stochastic differential equations, MCMC samplers -- with convergence diagnostics, variance reduction, trajectory visualization.

When Use

  • Need generate sample paths from stochastic process for estimation, prediction, or visualization
  • Analytical solutions intractable; simulation only feasible approach
  • Running Monte Carlo estimation, need convergence guarantees and uncertainty quantification
  • Want validate analytical results (stationary distributions, hitting times) against empirical simulation
  • Need sample from complex posterior distribution using MCMC
  • Prototyping stochastic model before committing to full analytical treatment

Inputs

Required

InputTypeDescription
process_typestringType of process: "dtmc", "ctmc", "random_walk", "brownian_motion", "sde", "mcmc"
parametersdictProcess-specific parameters (transition matrix, drift/diffusion coefficients, target density, etc.)
n_pathsintegerNumber of independent sample paths to simulate
n_stepsintegerNumber of time steps per path (or total MCMC iterations)

Optional

InputTypeDefaultDescription
initial_statescalar/vectorprocess-specificStarting state or distribution for each path
dtfloat0.01Time step size for continuous-time discretization
seedintegerrandomRandom seed for reproducibility
burn_inintegern_steps / 10Number of initial steps to discard (MCMC)
thinninginteger1Keep every k-th sample to reduce autocorrelation
variance_reductionstring"none"Method: "none", "antithetic", "stratified", "control_variate"
target_functioncallablenoneFunction to evaluate along paths for Monte Carlo estimation

Steps

Step 1: Define Process Model and Parameters

1.1. Identify process type, gather all required parameters:

  • DTMC: Transition matrix P and state space. Validate P is row-stochastic.
  • CTMC: Rate matrix Q. Validate rows sum to 0 and off-diagonal entries are non-negative.
  • Random walk: Step distribution (e.g., {-1, +1} with equal probability), boundaries if any.
  • Brownian motion: Drift mu, volatility sigma, dimension d.
  • SDE (Ito): Drift function a(x,t), diffusion function b(x,t).
  • MCMC: Target log-density, proposal mechanism (random walk Metropolis, Hamiltonian, Gibbs components).

1.2. Validate parameter consistency:

  • Matrix dimensions match state space size.
  • SDE coefficients satisfy growth and Lipschitz conditions (at least informally) for the chosen solver.
  • MCMC proposal is well-defined for the support of the target distribution.

1.3. Set the random seed for reproducibility.

Got: Fully specified stochastic model with validated parameters and reproducible random state.

If fail: Parameters inconsistent (e.g., non-stochastic matrix)? Correct before proceeding. SDE coefficients pathological? Consider different discretization scheme.

Step 2: Select Simulation Method

2.1. Choose appropriate algorithm based on process type:

ProcessMethodKey Property
DTMCDirect sampling from transition rowExact
CTMCGillespie algorithm (SSA)Exact, event-driven
CTMC (approx.)Tau-leapingApproximate, faster for high rates
Random walkDirect sampling of incrementsExact
Brownian motionCumulative sum of Gaussian incrementsExact for fixed dt
SDE (general)Euler-MaruyamaOrder 0.5 strong, order 1.0 weak
SDE (higher order)MilsteinOrder 1.0 strong (scalar noise)
SDE (stiff)Implicit Euler-MaruyamaStable for stiff drift
MCMC (general)Metropolis-HastingsAsymptotically exact
MCMC (gradient)Hamiltonian Monte Carlo (HMC)Better mixing for high dimensions
MCMC (conditional)Gibbs samplerExact conditionals when available

2.2. For SDE methods, choose dt small enough for numerical stability. A useful heuristic: start with dt = 0.01 and halve it until results stabilize.

2.3. For MCMC, tune the proposal scale to achieve an acceptance rate of approximately:

  • 23.4% for high-dimensional random walk Metropolis
  • 57.4% for one-dimensional targets
  • 65-90% for HMC (depends on trajectory length)

2.4. If variance reduction is requested, configure it:

  • Antithetic variates: For each path with random increments Z, also simulate with -Z.
  • Stratified sampling: Partition the probability space and sample within each stratum.
  • Control variates: Identify a correlated quantity with known expectation to reduce variance.

Got: Selected simulation algorithm matched to process type with appropriate tuning parameters.

If fail: Chosen method unstable (e.g., Euler-Maruyama diverging)? Switch to implicit method or reduce dt.

Step 3: Implement and Run Simulation

3.1. Allocate storage for n_paths trajectories, each length n_steps (or dynamic for event-driven methods like Gillespie).

3.2. For each path i = 1, ..., n_paths:

DTMC / Random Walk:

  • Set x[0] = initial_state
  • For t = 1, ..., n_steps: sample x[t] from the transition distribution given x[t-1]

CTMC (Gillespie):

  • Set x[0] = initial_state, time = 0
  • While time < T_max:
    • Compute total rate lambda = -Q[x, x]
    • Sample holding time tau ~ Exp(lambda)
    • Sample next state from transition probabilities Q[x, j] / lambda for j != x
    • Update time += tau, record transition

SDE (Euler-Maruyama):

  • Set x[0] = initial_state
  • For t = 1, ..., n_steps:
    • dW = sqrt(dt) * N(0, I) (Wiener increment)
    • x[t] = x[t-1] + a(x[t-1], t*dt) * dt + b(x[t-1], t*dt) * dW

MCMC (Metropolis-Hastings):

  • Set x[0] = initial_state
  • For t = 1, ..., n_steps:
    • Propose x' ~ q(x' | x[t-1])
    • Compute acceptance ratio alpha = min(1, p(x') * q(x[t-1]|x') / (p(x[t-1]) * q(x'|x[t-1])))
    • Accept with probability alpha: x[t] = x' if accepted, else x[t] = x[t-1]
    • Record acceptance decision

3.3. If target_function is provided, evaluate it at each state along each path and store the values.

3.4. Apply thinning: keep every thinning-th sample.

3.5. Discard burn_in samples from the beginning of each path (primarily for MCMC).

Got: n_paths complete trajectories stored in memory, optional function evaluations. MCMC acceptance rate within target range.

If fail: Simulation produces NaN or Inf values? Reduce dt for SDE methods or check parameter validity. MCMC acceptance rate near 0% or 100%? Adjust proposal scale.

Step 4: Apply Convergence Diagnostics

4.1. Trace plots: Plot the value of each component over time for a subset of paths. Visual inspection for stationarity (no trends, stable variance).

4.2. Gelman-Rubin diagnostic (R-hat): For MCMC with multiple chains:

  • Compute within-chain variance W and between-chain variance B.
  • R_hat = sqrt((n-1)/n + B/(n*W))
  • Convergence indicated by R_hat < 1.01 (strict) or R_hat < 1.1 (lenient).

4.3. Effective sample size (ESS):

  • Estimate autocorrelation at increasing lags.
  • ESS = n_samples / (1 + 2 * sum(autocorrelations))
  • Rule of thumb: ESS > 400 for reliable posterior summaries.

4.4. Geweke diagnostic: Compare the mean of the first 10% and last 50% of each chain. The z-score should be within [-2, 2] for convergence.

4.5. For non-MCMC processes: Verify that time-averaged statistics (mean, variance) stabilize as path length increases. Plot running averages.

4.6. Report a summary table:

DiagnosticValueThresholdStatus
R-hat (max)...< 1.01...
ESS (min)...> 400...
Geweke z (max abs)...< 2.0...
Acceptance rate...0.15-0.50...

Got: All convergence diagnostics pass thresholds. Trace plots show stable, well-mixing chains.

If fail: R-hat > 1.1? Run longer chains or improve proposal. ESS very low? Increase thinning or switch to better sampler (e.g., HMC). Geweke fails? Extend burn-in.

Step 5: Compute Summary Statistics with Confidence Intervals

5.1. For each quantity of interest (state occupancy, function expectation, hitting times):

  • Compute the point estimate as the sample mean across paths (after burn-in and thinning).
  • Compute the standard error using the effective sample size: SE = SD / sqrt(ESS).

5.2. Construct confidence intervals:

  • Normal approximation: estimate +/- z_{alpha/2} * SE
  • For skewed distributions, use percentile bootstrap or batch means.

5.3. If variance reduction was applied, compute the variance reduction factor:

  • VRF = Var(naive estimator) / Var(reduced estimator)
  • Report the effective speedup.

5.4. For Monte Carlo integration estimates:

  • Report the estimate, standard error, 95% CI, ESS, and number of function evaluations.

5.5. For distribution estimates:

  • Compute empirical quantiles (median, 2.5th, 97.5th percentiles).
  • Kernel density estimates for continuous quantities.

5.6. Tabulate all summary statistics with their uncertainties.

Got: Point estimates with associated standard errors and confidence intervals. Variance reduction (if applied) yields VRF > 1.

If fail: Confidence intervals too wide? Increase n_paths or n_steps. Variance reduction worsens estimates (VRF < 1)? Disable it -- control variate or antithetic scheme may not suit problem.

Step 6: Visualize Trajectories and Distributions

6.1. Trajectory plots: Plot a representative subset of sample paths (5-20 paths) over time. Use transparency for overlapping paths.

6.2. Ensemble statistics: Overlay the mean trajectory and pointwise 95% confidence bands across all paths.

6.3. Marginal distributions: At selected time points, plot histograms or density estimates of the state distribution across paths.

6.4. Stationary distribution comparison: If an analytical stationary distribution is available, overlay it on the empirical histogram from the final time slice.

6.5. Autocorrelation plots: For MCMC, plot the autocorrelation function (ACF) for each component up to a reasonable lag.

6.6. Diagnostic dashboard: Combine trace plots, ACF plots, running mean plots, and marginal densities into a single multi-panel figure for comprehensive assessment.

6.7. Save all figures in both vector (PDF/SVG) and raster (PNG) formats for documentation.

Got: Publication-quality figures show trajectory behavior, distributional convergence, diagnostic summaries. Analytical solutions (where available) match empirical results.

If fail: Visualizations reveal non-stationarity or multimodality not expected from model? Revisit Steps 1-2 for parameter or method errors. Plots cluttered? Reduce number of displayed paths or increase figure size.

Checks

  • All simulated trajectories remain in valid state space (no out-of-bounds values, no NaN/Inf)
  • DTMC/CTMC: empirical stationary distribution converges to analytical one (within expected Monte Carlo error)
  • SDE: halving dt does not qualitatively change results (convergence order check)
  • MCMC: R-hat < 1.01, ESS > 400, Geweke z-scores within [-2, 2]
  • Confidence interval widths decrease proportional to 1/sqrt(n_paths) (central limit theorem)
  • Variance reduction techniques yield VRF > 1 (estimates improve, not worsen)
  • Reproducibility: re-running with same seed produces identical results

Pitfalls

  • Insufficient burn-in for MCMC: Starting from poor initial state needs long burn-in before samples represent target distribution. Always inspect trace plots and use convergence diagnostics rather than guessing burn-in length.
  • Euler-Maruyama instability for stiff SDEs: Drift term has large gradients? Explicit Euler-Maruyama can diverge. Switch to implicit methods or use adaptive step sizing.
  • Confuse strong and weak convergence for SDEs: Strong convergence measures pathwise error (important for individual trajectories); weak convergence measures distributional error (sufficient for expectations). Euler-Maruyama has weak order 1.0 but strong order 0.5.
  • Pseudorandom number generator quality: Very long simulations? Low-quality RNGs can produce correlated samples. Use well-tested generator (Mersenne Twister, PCG, or Xoshiro), verify independence.
  • Ignore autocorrelation in MCMC: Treating autocorrelated MCMC samples as independent underestimates uncertainty. Always use effective sample size, not raw sample count, for standard errors.
  • Antithetic variates for non-monotone functions: Antithetic sampling reduces variance only when estimand is monotone function of underlying uniforms. Non-monotone functions? Can increase variance.
  • Memory for large simulations: Storing all time steps of many long paths can exhaust memory. Use online statistics (running mean, variance) when full trajectories not needed for visualization.

See Also

  • Model Markov Chain -- provides transition matrices and analytical solutions that simulation validates
  • Fit Hidden Markov Model -- simulation from fitted HMMs enables posterior predictive checking and synthetic data generation

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman/skills/simulate-stochastic-process
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

content-collections

Meta

Esta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.

Ver habilidad

polymarket

Meta

Esta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.

Ver habilidad

creating-opencode-plugins

Meta

Esta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.

Ver habilidad

sglang

Meta

SGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.

Ver habilidad