Board: restore the dropped "mean" qualifier on #940's 25 %/9 % contribution figures (CodeRabbit Minor on #941) - #942
Conversation
…lifier on the 25%/9% contribution figures The source RUN entry and the committed JSON's fitted_contribution_Pa_per_km keys report MEANS over the 19 storms (mean |c_geo*P_geo| / mean |c_bow*P_bow| vs mean |D|); the #940 summary rows dropped the qualifier. PR_ARC's merged entry gets an appended dated correction line (append-only rule -- the entry merged via #941 before the finding landed, not edited in place); LATEST_STATE's living shipped-table row is fixed in place (precedent: the N-vs-n_qualifying fix on #939). Fourth instance of the same summarization defect class this week: a qualifier or operand pairing true in the source, lost in the summary. The figure itself was never wrong -- its aggregation scope went unstated. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_226cb81a-82ae-4153-b2b6-c0651d08858f) |
|
Warning Review limit reached
Next review available in: 45 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
… feel at home (regime x geometry x calibration) Operator framing, three messages: hold different situations constant (over water) vs flatland vs storm with high velocity differences/turbulence; good geometry vs badly calibrated; then find out where the substrate formulas feel at home. Hypothesis to falsify: a badly-calibrated substrate that maps DYNAMICALLY beats a well-calibrated absolute one in strong storms -- miscalibration as a regime-dependent property, not a uniform defect. Not fresh speculation. Three already-measured findings converge here: Fisher-z's opposite verdicts (8.3x better in the storm tail, 4.7x worse on ring means, #926); the three-register result that rank-normalised palette256 is the ONLY frame where cross-variable distance is defined (so "no absolute anchor" and "the only frame that works" are one property seen from two sides); and the operator-ruled golden index floor (#932), reused as the geometry axis's pre-existing good/bad split rather than inventing a new quality scale. SS1 PREFLIGHT ALREADY RUN -- the W6 lesson applied prospectively for the first time, and it corrected the plan before any bar existed: 1. "Flatland" is NOT one regime. It spans calmer-than-ocean (Amazon |grad p|=10.2) to 3x-ocean (W Siberia 43.8). Defining the middle regime by its surface-type LABEL would have scored two physically opposite fields as one condition. The regime axis is now defined by MEASURED |grad p|; surface labels are only the a-priori strategy for finding boxes along it. 2. Elevation confounds MSLP -- it is extrapolated over terrain, so its gradient is partly a reduction-formula artifact. Only elev sigma <= 150 m admissible, excluding US Great Plains (698 m), Argentine pampas (792 m), N European plain (319 m), Sahara (299 m) on evidence. 3. Wind SPEED does not discriminate (ocean 5.33 vs flatland 5.47 m/s); |grad p| separates them 14.96 vs 39.90. Scoring uses |grad p| and speed VARIANCE, never mean speed. Adopted ladder: R1 Amazon 10.2 -> R2 ocean 14.9 -> R3 W Siberia 43.8 -> R4 storm 95.6, a 9.3x dynamic range. Bars, controls first: C0 two controls (shuffled codebook + degenerate geometry), each cheap-smoke-tested for LOSABILITY before the full run (the E-A-CONTROL-THAT-CANNOT-LOSE lesson, plus W5's cannot-DIFFER twin); C1 ladder stability across >=3 timesteps; C2 THE CROSSOVER, two-sided with both failure directions pre-registered as reportable; C3 miscalibration penalty vs turbulence; C4 geometry floor on a sampling-fidelity metric (a NULL is expected-plausible per W5's B4 and must be said plainly); C5 the comfort matrix as the deliverable. Output contract carries raw operands, codebook edges actually used, drawn sample counts (equal-budget proof not intent), and units on every dimensional field -- the artifact-completeness and c_bow-is-km^-1 lessons. Board hygiene: INTEGRATION_PLANS prepend + STATUS_BOARD rows D-CZ-0..6 (D-CZ-0 already DONE -- the preflight). ~150 MB, minutes. Doc-only, nothing run beyond the preflight. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
#942 was mixed -- the CodeRabbit "mean"-qualifier fix AND the new substrate-comfort-zones-v1 plan -- so it gets its own arc entry (the termination clause covers hygiene-only PRs, not this). The entry records what a future session needs the "why" for: the plan states the operator's hypothesis as an INTERACTION term, not a main effect (worse-everywhere-but-least-worse-in-storms and better-only-in- storms are different findings), and D-CZ-0's three preflight corrections are this session's own lessons applied rather than re-learned -- sample-composition arithmetic before the first fetch, both controls smoke-tested for losability, units annotated at coefficient definition. Also records what is NOT done: the report SS10 reconciliation sweep. SS10.2's model is disconfirmed, SS10.5's "gather-design unblocked" is retracted, SS10.6's roadmap still shows pre-wave gates -- the corrections live in plan RUN sections and epiphanies, and the report itself is stale. Named in Deferred so it does not get lost. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
…arvest-rfii13 Board hygiene for merged #942 — arc entry + shipped row
One-word-class fix, handled per governance
CodeRabbit's Minor on #941 (which merged before the finding landed): the 25 %/9 % contribution figures in #940's summary rows dropped the mean qualifier the source RUN entry and the committed JSON's
fitted_contribution_Pa_per_kmkeys carry (means over the 19 storms).PR_ARC_INVENTORY.md— appended dated correction line to the merged W6 RUN — the vector-sum dipole model is VOID by its own control, and the stranded stratum is empty for a structural reason #940 entry (append-only rule: merged entries get appended corrections, not in-place edits).LATEST_STATE.md— living shipped-table row fixed in place (precedent: the N-vs-n_qualifying fix on Board hygiene for merged #938 — W5 v2 results + the 3 same-day codex fixes #939).Fourth instance this week of the same summarization defect class: a qualifier or operand pairing true in the source, lost in the summary. The figure was never wrong — its aggregation scope went unstated.
Doc/board only.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
Generated by Claude Code