Exploration Efficiency Kernel Calibration
Exploration Efficiency Kernel Calibration
This note gives dimension-aware calibration rules for the kernel-reweighted router sampler in Exploration efficiency methods. It is agent-drafted and should be treated as a proposal until reviewed against follow-up decoding runs.
The main correction is that and should not be fixed constants across latent dimensions. In the current implementation, the kernel is applied in whitened router coordinates , then mapped back to the original latent by . Therefore the right scale for is the geometry of iid Gaussian samples in whitened dimensions, not the per-coordinate scale of the original router distribution.
Setup
Let be independent whitened router samples, let be the number of previous samples at the step being calibrated, and let
The rejection sampler uses
The calibration problem is to choose so is neither numerically zero nor globally large, then choose so the resulting acceptance probabilities have a desired amount of downweighting without excessive rejection or fallback.
RBF Activity Criterion
For the actual RBF kernel, the most direct scale diagnostic is the expected pairwise kernel overlap:
At a history length , the expected kernel density is
Given a target expected density at the chosen horizon , solve for
This is the most useful first calibration rule for the current sampler. For an exploratory rejection sampler, a reasonable first target is often at the final evaluation horizon, then refine by empirical acceptance diagnostics.
For the z64 exploration-efficiency sweep with and , this gives:
| target | |
|---|---|
| 0.1 | 3.19 |
| 0.5 | 3.81 |
| 1.0 | 4.20 |
| 2.0 | 4.73 |
The failed sweep used , for which the maximum expected final-step density is only . That makes almost irrelevant because for every proposal.
Hard-Ball Affected-Mass Criterion
If the question is literally "what fraction of proposals fall within radius of any previous sample?", use the pairwise distance distribution
The probability that a new proposal falls within a hard ball of radius around one prior sample is
The probability that it falls within radius of at least one of independent history samples is approximately
Given a target affected mass , solve
This criterion answers the volume question directly, but it should not be confused with the softer RBF-density criterion. In high dimension it produces much larger radii. For , affecting even 1% of proposals by a hard ball requires , and affecting 10% requires .
Beta Calibration
After choosing , choose using an acceptance target at a reference density . Rearranging the sampler's acceptance function gives
where is the desired acceptance probability at density .
For , examples are:
| reference density | target acceptance | |
|---|---|---|
| 0.1 | 0.8 | 2.28 |
| 0.1 | 0.5 | 7.14 |
| 0.5 | 0.8 | 0.457 |
| 0.5 | 0.5 | 1.43 |
| 1.0 | 0.8 | 0.228 |
| 1.0 | 0.5 | 0.714 |
This shows why can be either inert or very aggressive depending on . With , is effectively zero, so does nothing. With , the CPU sweep estimates median acceptance around 0.10 at , which would be far more aggressive.
Lower target acceptance means stronger repulsion. Higher target acceptance means gentler repulsion.
CPU-Only Calibration Protocol
Before running GPU decoding, run a calibration pass that uses only sampled or saved whitened vectors:
- Fix the coordinate system and effective dimension. For the current implementation this is full whitened latent space, so for z64 runs. If future work uses PCA, angular features, or a strategy-relevant subspace, use that effective dimension instead.
- Fix the evaluation horizon . For a 32-sample exploration budget, use for final-step calibration and optionally inspect earlier steps.
- Choose an RBF-density target , such as , , or , and compute the corresponding analytically.
- Compute empirical quantiles from stored or simulated iid whitened samples for the candidate values.
- Choose by targeting median or upper-quantile acceptance, then verify expected rejection attempts, fallback probability, and the fraction of proposals with acceptance below thresholds such as 0.95 and 0.8.
- Only after this CPU pass, run a small decoding pilot and evaluate external strategy coverage as in Exploration efficiency coverage metrics.
For the z64 Qwen2.5 sweep, the CPU-only calibration artifacts are in path:experiments/synthetic_sequences/disentangled/analysis/aggregates/synthetic-pretrained-exploration-efficiency-from-entangled-v2-z64-qwen25-global-token-kernel-calibration_20260604, with the repo-side report at path:experiments/synthetic_sequences/disentangled/analysis/aggregates/synthetic-pretrained-exploration-efficiency-from-entangled-v2-z64-qwen25-global-token-kernel-calibration_20260604/report.md.
Recommended Pilot Grid For z64
The calibration sweep suggests this paired pilot grid before any broad GPU evaluation. The first six settings target moderate RBF activity. The final six settings target larger hard-ball affected mass; their values are much smaller because the implemented sampler still uses RBF density, which is already large at these radii.
| tag | criterion | target | target acceptance | ||
|---|---|---|---|---|---|
rbf0p1_acc0p8 | RBF density | 3.19 | 2.28 | 0.8 | |
rbf0p1_acc0p5 | RBF density | 3.19 | 7.14 | 0.5 | |
rbf0p5_acc0p8 | RBF density | 3.81 | 0.457 | 0.8 | |
rbf0p5_acc0p5 | RBF density | 3.81 | 1.43 | 0.5 | |
rbf1p0_acc0p8 | RBF density | 4.20 | 0.228 | 0.8 | |
rbf1p0_acc0p5 | RBF density | 4.20 | 0.714 | 0.5 | |
ball0p01_acc0p8 | hard-ball affected mass | 1% | 8.04 | 0.0195 | 0.8 |
ball0p01_acc0p5 | hard-ball affected mass | 1% | 8.04 | 0.0611 | 0.5 |
ball0p10_acc0p8 | hard-ball affected mass | 10% | 8.67 | 0.0171 | 0.8 |
ball0p10_acc0p5 | hard-ball affected mass | 10% | 8.67 | 0.0534 | 0.5 |
ball0p50_acc0p8 | hard-ball affected mass | 50% | 9.31 | 0.0153 | 0.8 |
ball0p50_acc0p5 | hard-ball affected mass | 50% | 9.31 | 0.0478 | 0.5 |
This grid is not a claim that these settings improve task-local strategy coverage. It is a calibrated way to test the intended mechanism: unlike the original grid, these settings should actually change the proposal distribution in 64D whitened space while keeping rejection behavior measurable.
Caveats
The RBF calibration only ensures that the sampler is active in whitened Euclidean geometry. It does not ensure that whitened Euclidean distance is aligned with strategy identity. The failed sweep also showed that same-strategy and different-strategy sample pairs have very similar full-space distances, so follow-up work should also test angular repulsion, lower-dimensional strategy-relevant subspaces, or candidate reranking methods if calibrated RBF repulsion still fails to improve coverage.