メニュー
Debug and tune the echo state network reservoir. Use when diagnosing spectral radius issues, chaotic dynamics problems, sparse weight anomalies, or reservoir-to-hypervector projection failures.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | debugging-reservoir |
| description | Debug and tune the echo state network reservoir. Use when diagnosing spectral radius issues, chaotic dynamics problems, sparse weight anomalies, or reservoir-to-hypervector projection failures. |
The reservoir is a sparse Echo State Network in src/reservoir.rs:
Reservoir: core ESN with sparse adjacency-list weightsChaoticReservoir: wrapper adding noise perturbation for edge-of-chaos dynamicsWeights are Vec<Vec<(usize, f32)>> — each row is a list of (column_index, weight).
w_in): 32 connections per neuronw_res): 64 connections per neuron (or min(64, size))dot_sparse_row(&weights[i], &values)The spectral radius controls chaos level. Must be in [0.9, 1.1].
| Symptom | Likely Cause |
|---|---|
| State saturates to all ±1 | Radius too high (> 1.1) |
| State decays to all ~0 | Radius too low (< 0.9) |
| Non-deterministic test failures | Using new() instead of new_seeded() |
| Different results across runs | Unseeded RNG |
Power iteration (16 steps) in estimate_spectral_radius():
vv = W * v, then normalizev^T W v / v^T vIf radius is wrong after init, check:
scale = target / current)current_radius returning 0? (degenerate weights)Projects reservoir state → HVec10240. Requires size >= 10240.
InvalidDimension { expected: 10240, actual: N } — reservoir too smallstep() first)ChaoticReservoir adds uniform noise ±chaos_strength to each input element.
Uses a separate RNG seeded with seed ^ 0xA5A5_5A5A_F0F0_0F0F for independence.
step() being called before to_hypervector()?reset() between independent sequences?size >= 10240 for projection?[0.9, 1.1] after construction?new_seeded(..., 42) for determinism?GOAP-based orchestrator for managing GitHub issues, creating action plans, and executing workspace operations with branch/PR workflow.
Configure and troubleshoot npm OIDC Trusted Publishing for GitHub Actions. Use when npm publish fails with E404, OIDC errors, or provenance issues.
GitHub release management, crates.io trusted publishing, npm provenance, and GitHub Pages documentation. Use when creating releases, publishing packages, or deploying docs.
Git commit conventions, validation gates, and CI/CD workflows. Use when committing changes, verifying gates, or working with GitHub Actions.
Validate merge readiness with atomic commits and GitHub Actions checks using gh CLI; use for pre-merge verification and CI truth validation.
Apply TRIZ inventive principles to solve problems that seem to have no good solution. Use after triz-analysis has identified contradictions.