MCP HubMCP Hub
Volver a habilidades

fit-drift-diffusion-model

pjt222
Actualizado 2 days ago
1 vistas
17
2
17
Ver en GitHub
Pruebasreactdata

Acerca de

Esta habilidad ajusta modelos de difusión-deriva de Ratcliff a datos de tiempo de reacción y precisión para tareas de decisión binaria. Estima parámetros cognitivos como la tasa de deriva y la separación de límites, realiza comparación de modelos e incluye validación mediante recuperación de parámetros. Úsela cuando necesite descomponer las compensaciones velocidad-precisión en componentes cognitivos latentes o comparar modelos de muestreo secuencial a partir de datos experimentales.

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/fit-drift-diffusion-model

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

Documentación

Drift-Diffusions-Modell anpassen

Schaetzen der Parameters of a drift-diffusion model (DDM) from reaction time and accuracy data, evaluate model fit gegen observed quantiles, compare candidate model variants, and validate estimation quality durch parameter recovery simulation.

Wann verwenden

  • Modeling binary decision-making with reaction time data
  • Estimating cognitive parameters (drift rate, boundary separation, non-decision time) from experimental data
  • Comparing sequential sampling model variants for a decision task
  • Validating that a DDM fitting pipeline recovers known parameter values
  • Decomposing speed-accuracy tradeoff effects into latent cognitive components

Eingaben

  • Erforderlich: Reaction time data with accuracy labels (correct/error) per trial
  • Erforderlich: Subject and condition identifiers fuer jede trial
  • Erforderlich: Choice of DDM variant (basic 3-parameter, full 7-parameter, or hierarchical)
  • Optional: Prior distributions for Bayesian estimation (default: weakly informative)
  • Optional: Number of simulated datasets for parameter recovery (default: 100)
  • Optional: RT filtering bounds in seconds (default: 0.1 to 5.0)

Vorgehensweise

Schritt 1: Vorbereiten Reaction Time Data

Bereinigen and format the raw behavioral data for DDM fitting.

  1. Laden die Datenset and inspect columns for subject ID, condition, RT, and accuracy:
import pandas as pd

data = pd.read_csv("behavioral_data.csv")
required_columns = ["subject_id", "condition", "rt", "accuracy"]
assert all(col in data.columns for col in required_columns), \
    f"Missing columns: {set(required_columns) - set(data.columns)}"
  1. Filtern outlier RTs using configurable bounds:
rt_lower = 0.1  # seconds
rt_upper = 5.0  # seconds

n_before = len(data)
data = data[(data["rt"] >= rt_lower) & (data["rt"] <= rt_upper)]
n_removed = n_before - len(data)
print(f"Removed {n_removed} trials ({100*n_removed/n_before:.1f}%) outside [{rt_lower}, {rt_upper}]s")
  1. Berechnen summary statistics per subject and condition:
summary = data.groupby(["subject_id", "condition"]).agg(
    n_trials=("rt", "count"),
    mean_rt=("rt", "mean"),
    accuracy=("accuracy", "mean")
).reset_index()
print(summary.describe())
  1. Verifizieren minimum trial counts (DDM needs sufficient data per cell):
min_trials = summary["n_trials"].min()
assert min_trials >= 40, f"Minimum trials per cell is {min_trials}; need at least 40 for stable estimation"

Erwartet: Cleaned dataframe with no RT outliers, mindestens 40 trials per subject-condition cell, and accuracy rates zwischen 0.50 and 0.99.

Bei Fehler: If trial counts are too low, consider collapsing conditions or removing subjects with excessive missing data. If accuracy is at ceiling (>0.99) or floor (<0.55), the DDM may not be identifiable -- check task difficulty.

Schritt 2: Auswaehlen DDM Variant

Waehlen the appropriate model complexity basierend auf the research question.

  1. Definieren the candidate model variants:
model_variants = {
    "basic": {
        "params": ["v", "a", "t"],
        "description": "Drift rate, boundary separation, non-decision time",
        "free_params": 3
    },
    "full": {
        "params": ["v", "a", "t", "z", "sv", "sz", "st"],
        "description": "Basic + starting point bias, cross-trial variability",
        "free_params": 7
    },
    "hddm": {
        "params": ["v", "a", "t", "z"],
        "description": "Hierarchical with group-level and subject-level parameters",
        "free_params": "4 per subject + 8 group-level"
    }
}
  1. Auswaehlen basierend auf data characteristics:
CriterionBasic (3-param)Full (7-param)Hierarchical
Trials per cell40-100200+40+ (pooled)
SubjectsAnyAny10+
Research goalGroup effectsIndividual fitsBoth levels
Error RT shapeSymmetricAsymmetricEither
  1. Konfigurieren the selected variant:
selected_variant = "basic"  # adjust based on criteria above
model_config = model_variants[selected_variant]
print(f"Selected: {selected_variant} ({model_config['free_params']} free parameters)")
print(f"Parameters: {', '.join(model_config['params'])}")

Erwartet: A model variant selected with justification basierend auf trial counts, subject count, and research question.

Bei Fehler: If unsure zwischen variants, start with the basic model and add complexity only if residual diagnostics indicate systematic misfit (e.g., error RT distribution mismatch).

Schritt 3: Schaetzen Parameters

Fit the DDM to data using maximum likelihood or Bayesian estimation.

  1. For MLE fitting using the fast-dm or Python pyddm approach:
import pyddm

model = pyddm.Model(
    drift=pyddm.DriftConstant(drift=pyddm.Fittable(minval=0, maxval=5)),
    bound=pyddm.BoundConstant(B=pyddm.Fittable(minval=0.3, maxval=3.0)),
    nondecision=pyddm.NonDecisionConstant(t=pyddm.Fittable(minval=0.1, maxval=0.5)),
    overlay=pyddm.OverlayNonDecision(nondectime=pyddm.Fittable(minval=0.1, maxval=0.5)),
    T_dur=5.0,
    dt=0.001,
    dx=0.001
)
  1. For Bayesian estimation using HDDM:
import hddm

hddm_model = hddm.HDDM(data, depends_on={"v": "condition"})
hddm_model.find_starting_values()
hddm_model.sample(5000, burn=1000, thin=2, dbname="traces.db", db="pickle")
  1. Extrahieren and store estimated parameters:
params = hddm_model.get_group_estimates()
print("Group-level parameter estimates:")
for param_name, stats in params.items():
    print(f"  {param_name}: {stats['mean']:.3f} [{stats['2.5q']:.3f}, {stats['97.5q']:.3f}]")
  1. Check convergence (Bayesian only):
from kabuki.analyze import gelman_rubin

convergence = gelman_rubin(hddm_model)
max_rhat = max(convergence.values())
print(f"Max Gelman-Rubin R-hat: {max_rhat:.3f}")
assert max_rhat < 1.1, f"Chains have not converged (R-hat = {max_rhat:.3f})"

Erwartet: Parameter estimates with standard errors or credible intervals. For Bayesian fits, Gelman-Rubin R-hat < 1.1 for all parameters. Drift rate typischerweise 0.5-4.0, boundary 0.5-2.5, non-decision time 0.15-0.50s.

Bei Fehler: If estimation fails to converge, try: (a) tighter parameter bounds, (b) better starting values via grid search, (c) longer chains with more burn-in. If MLE hits boundary values, das Modell kann misspecified.

Schritt 4: Bewerten Modellieren Fit

Vergleichen predicted and observed RT distributions using quantile-based diagnostics.

  1. Generieren predicted RT quantiles from the fitted model:
import numpy as np

quantiles = [0.1, 0.3, 0.5, 0.7, 0.9]

predicted_rts = model.simulate(n_trials=10000)
pred_quantiles = np.quantile(predicted_rts[predicted_rts > 0], quantiles)  # correct
pred_quantiles_err = np.quantile(np.abs(predicted_rts[predicted_rts < 0]), quantiles)  # error
  1. Berechnen observed RT quantiles:
obs_correct = data[data["accuracy"] == 1]["rt"]
obs_error = data[data["accuracy"] == 0]["rt"]

obs_quantiles = np.quantile(obs_correct, quantiles)
obs_quantiles_err = np.quantile(obs_error, quantiles) if len(obs_error) > 10 else None
  1. Erstellen a quantile-probability plot (QP plot):
import matplotlib.pyplot as plt

fig, ax = plt.subplots(1, 1, figsize=(8, 6))
ax.scatter(obs_quantiles, quantiles, marker="o", label="Observed (correct)")
ax.scatter(pred_quantiles, quantiles, marker="x", label="Predicted (correct)")
if obs_quantiles_err is not None:
    ax.scatter(obs_quantiles_err, quantiles, marker="o", facecolors="none", label="Observed (error)")
    ax.scatter(pred_quantiles_err, quantiles, marker="x", label="Predicted (error)")
ax.set_xlabel("RT (s)")
ax.set_ylabel("Quantile")
ax.legend()
ax.set_title("Quantile-Probability Plot")
fig.savefig("qp_plot.png", dpi=150)
  1. Berechnen fit statistic (chi-square on quantile bins):
from scipy.stats import chisquare

observed_proportions = np.diff(np.concatenate([[0], quantiles, [1]]))
predicted_proportions = np.diff(np.concatenate([[0], quantiles, [1]]))
chi2, p_value = chisquare(observed_proportions, predicted_proportions)
print(f"Chi-square fit: chi2={chi2:.3f}, p={p_value:.3f}")

Erwartet: QP plot shows predicted quantiles closely tracking observed quantiles for both correct and error RTs. Chi-square test is non-significant (p > 0.05), indicating adequate fit.

Bei Fehler: If das Modell systematically misses fast or slow quantiles, consider adding cross-trial variability parameters (sv, st). If error RT shape is wrong, add starting point variability (sz). Refit with the extended model.

Schritt 5: Vergleichen Models

Use information criteria to select among candidate DDM variants.

  1. Fit each candidate model and collect fit statistics:
model_results = {}
for variant_name in ["basic", "full"]:
    fitted_model = fit_ddm(data, variant=variant_name)
    model_results[variant_name] = {
        "log_likelihood": fitted_model.log_likelihood,
        "n_params": fitted_model.n_free_params,
        "bic": fitted_model.bic,
        "aic": fitted_model.aic
    }
  1. Berechnen and compare BIC values:
print("Model Comparison (BIC):")
print(f"{'Model':<15} {'LL':>10} {'k':>5} {'BIC':>12} {'delta_BIC':>12}")
print("-" * 55)

best_bic = min(r["bic"] for r in model_results.values())
for name, result in sorted(model_results.items(), key=lambda x: x[1]["bic"]):
    delta = result["bic"] - best_bic
    print(f"{name:<15} {result['log_likelihood']:>10.1f} {result['n_params']:>5} "
          f"{result['bic']:>12.1f} {delta:>12.1f}")
  1. Interpret BIC differences using standard guidelines:
# BIC difference interpretation (Kass & Raftery, 1995):
# 0-2:   Not worth mentioning
# 2-6:   Positive evidence
# 6-10:  Strong evidence
# >10:   Very strong evidence
  1. For Bayesian models, use DIC or WAIC:
dic = hddm_model.dic
print(f"DIC: {dic:.1f}")

Erwartet: A clear winner among models with BIC difference > 6, or a justified decision to retain the simpler model when the difference is < 2.

Bei Fehler: If models are indistinguishable (BIC difference < 2), prefer the simpler model (parsimony). If the full model wins by a large margin, ensure the basic model was not misspecified due to data issues.

Schritt 6: Validieren with Parameter Recovery Simulation

Verifizieren the estimation pipeline recovers known parameter values from simulated data.

  1. Definieren the ground-truth parameter grid:
true_params = {
    "v": [0.5, 1.0, 2.0, 3.0],
    "a": [0.6, 1.0, 1.5, 2.0],
    "t": [0.2, 0.3, 0.4]
}
  1. Simulieren datasets and re-estimate fuer jede combination:
from itertools import product

recovery_results = []
n_simulated_trials = 500  # match empirical trial count

for v_true, a_true, t_true in product(true_params["v"], true_params["a"], true_params["t"]):
    simulated_data = simulate_ddm(v=v_true, a=a_true, t=t_true, n=n_simulated_trials)
    fitted = fit_ddm(simulated_data, variant="basic")
    recovery_results.append({
        "v_true": v_true, "v_est": fitted.params["v"],
        "a_true": a_true, "a_est": fitted.params["a"],
        "t_true": t_true, "t_est": fitted.params["t"]
    })
  1. Berechnen recovery statistics:
recovery_df = pd.DataFrame(recovery_results)
for param in ["v", "a", "t"]:
    correlation = recovery_df[f"{param}_true"].corr(recovery_df[f"{param}_est"])
    bias = (recovery_df[f"{param}_est"] - recovery_df[f"{param}_true"]).mean()
    rmse = np.sqrt(((recovery_df[f"{param}_est"] - recovery_df[f"{param}_true"])**2).mean())
    print(f"{param}: r={correlation:.3f}, bias={bias:.4f}, RMSE={rmse:.4f}")
  1. Generieren recovery scatter plots:
fig, axes = plt.subplots(1, 3, figsize=(15, 5))
for idx, param in enumerate(["v", "a", "t"]):
    ax = axes[idx]
    ax.scatter(recovery_df[f"{param}_true"], recovery_df[f"{param}_est"], alpha=0.5)
    lims = [recovery_df[f"{param}_true"].min(), recovery_df[f"{param}_true"].max()]
    ax.plot(lims, lims, "k--", label="Identity")
    ax.set_xlabel(f"True {param}")
    ax.set_ylabel(f"Estimated {param}")
    ax.set_title(f"Recovery: {param} (r={recovery_df[f'{param}_true'].corr(recovery_df[f'{param}_est']):.3f})")
    ax.legend()
fig.tight_layout()
fig.savefig("parameter_recovery.png", dpi=150)

Erwartet: Recovery correlations r > 0.85 for all parameters, bias close to zero (< 5% of parameter range), and RMSE innerhalb acceptable bounds for die Anwendung.

Bei Fehler: Low recovery for a specific parameter normalerweise means: (a) insufficient trials -- increase n_simulated_trials, (b) parameter tradeoffs -- drift rate and boundary can trade off; fix one to test recoverability, (c) flat likelihood surface -- consider reparameterization or Bayesian estimation with informative priors.

Validierung

  • Input data has RT and accuracy columns with correct types
  • Outlier filtering removed fewer than 10% of trials
  • Every subject-condition cell has mindestens 40 trials
  • Parameter estimates are innerhalb plausible ranges (v: 0-5, a: 0.3-3.0, t: 0.1-0.6)
  • Convergence diagnostics pass (R-hat < 1.1 for Bayesian, gradient near zero for MLE)
  • QP plot shows predicted quantiles innerhalb 50ms of observed quantiles
  • Modellieren comparison yields a clear ranking or justified parsimony decision
  • Parameter recovery correlations exceed r = 0.85 for all free parameters
  • Recovery bias is less than 5% of der Parameter range

Haeufige Stolperfallen

  • Insufficient trial counts: DDM estimation is data-hungry. Fewer than 40 trials per cell leads to unstable estimates and poor recovery. Always verify trial counts vor fitting.
  • Ignoring error RTs: The DDM jointly models correct and error RT distributions. Discarding error trials throws away information about boundary separation and starting point bias.
  • Not filtering fast guesses: RTs unter 100ms are likely contaminants (anticipatory responses). Einschliessen them and they distort non-decision time estimates.
  • Confusing DDM variants: The basic model assumes no cross-trial variability. If error RTs are systematically faster than correct RTs, you need the full model with sv and sz parameters.
  • Overfitting with the full model: The 7-parameter DDM can overfit sparse data. Use BIC (which penalizes complexity) anstatt AIC for model selection with DDMs.
  • Skipping parameter recovery: Without recovery validation, you cannot distinguish estimation bias from true experimental effects. Always run recovery vor interpreting condition differences.

Verwandte Skills

  • analyze-diffusion-dynamics - mathematical analysis of the diffusion process underlying the DDM
  • implement-diffusion-network - generative diffusion models that share the forward-process framework
  • design-experiment - experimental design considerations for collecting DDM-quality data
  • write-testthat-tests - testing parameter estimation pipelines in R

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/de/skills/fit-drift-diffusion-model
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

evaluating-llms-harness

Pruebas

Esta Skill de Claude ejecuta el benchmark lm-evaluation-harness para evaluar modelos de lenguaje en más de 60 tareas académicas estandarizadas como MMLU y GSM8K. Está diseñada para que los desarrolladores comparen la calidad de los modelos, realicen seguimiento del progreso del entrenamiento o reporten resultados académicos. La herramienta admite varios backends, incluidos modelos de HuggingFace y vLLM.

Ver habilidad

cloudflare-cron-triggers

Pruebas

Esta habilidad proporciona conocimiento integral para implementar Cron Triggers de Cloudflare y programar Workers mediante expresiones cron. Cubre la configuración de tareas periódicas, trabajos de mantenimiento y flujos de trabajo automatizados, manejando problemas comunes como expresiones cron inválidas y inconvenientes de zonas horarias. Los desarrolladores pueden utilizarla para configurar manejadores programados, probar activadores cron e integrar con Workflows y Green Compute.

Ver habilidad

webapp-testing

Pruebas

Esta habilidad de Claude proporciona un kit de herramientas basado en Playwright para probar aplicaciones web locales mediante scripts de Python. Permite verificación de frontend, depuración de interfaz de usuario, captura de pantallas y visualización de registros, mientras gestiona los ciclos de vida del servidor. Úsela para tareas de automatización de navegadores, pero ejecute los scripts directamente en lugar de leer su código fuente para evitar contaminación del contexto.

Ver habilidad

finishing-a-development-branch

Pruebas

Esta habilidad ayuda a los desarrolladores a completar el trabajo terminado verificando que las pruebas pasen y luego presentando opciones estructuradas de integración. Guía el flujo de trabajo para fusionar, crear PRs o limpiar ramas después de que se completa la implementación. Úsala cuando tu código esté listo y probado para finalizar sistemáticamente el proceso de desarrollo.

Ver habilidad