Release pass: wording, colour-blind-safe colours, map visibility, phone layout
Walked every tab on desktop and phone, clicked every link and button:
- Colours: new map inks and page colours, checked with simulated
protanopia/deuteranopia/tritanopia (worst pair ~12 CIEDE2000, was 1.4 for
Red/Green on the map and 9.7 for Orange/Brown on the page). Map label text
is always dark ink; dragon colour goes on borders. docs/COLOURS.md and
research/python/check_colours.py.
- Valley map: dragons get a paper halo and a visibility floor (faded ones never
drop below 0.3; bonding dragons start at 0.5); "no shadow" roll labelled
correctly.
- Wording: methods updated (strata, the newer form's questions, missing
answers, a new section on the solver, The Odds cards and genuine attempts);
findings use readable factor names and no longer claim a date adjustment;
'Load a newer route export above'; code links include solver.js and
explorer.js; The Odds shows 93% instead of '1 in 1'.
- Deep Dive route map treats all six dragons alike ('Bond a dragon' row,
default 'Bond any dragon'; rare sightings separate).
- Phone: Deep Dive no longer overflows (sections and selects can shrink).
- scripts/qa/crawl.js and mapcheck.js for future release checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
0ac5dfd971
commit
7366af2f7d
+16
-10
@@ -10,7 +10,7 @@
|
||||
color-scheme: dark;
|
||||
--bg: #170911; --surface: #210f19; --raised: #2a1420; --ink: #f6e8d6; --muted: #cba890; --faint: #8e7069; --line: #4b2a36;
|
||||
--accent: #e8b483; --accent-ink: #1d0a12; --good: #8fc98a; --warn: #f0a55a; --bad: #ef6b6b;
|
||||
--dr-red: #e4566d; --dr-green: #84c27c; --dr-orange: #f29a4c; --dr-brown: #c8976b; --dr-blue: #82a8f2; --dr-black: #b9abd3; --dr-any: #e0a9c6;
|
||||
--dr-red: #e8435e; --dr-green: #3fc0a8; --dr-orange: #ff9533; --dr-brown: #d1a47a; --dr-blue: #7ea6ff; --dr-black: #e0d8ea; /* checked for colour-blind separation (see docs/COLOURS.md) */ --dr-any: #e0a9c6;
|
||||
--link-low: #4f2f3c; --death: #9fb6c3; --ember: #e3692f; --death-bg: #1b0811; --frame: var(--accent);
|
||||
--font-display: "Marcellus", "Iowan Old Style", Georgia, serif;
|
||||
--font-crest: "Marcellus", "Iowan Old Style", Georgia, serif;
|
||||
@@ -171,6 +171,8 @@ body::before { content: ""; position: fixed; inset: 0 0 auto; height: env(safe-a
|
||||
.tab[aria-selected="true"] { background: var(--bg); color: var(--ink); border-top-color: var(--accent); }
|
||||
.tab:focus-visible { outline: 2px solid var(--accent); outline-offset: -2px; }
|
||||
.tabpanel { display: grid; gap: 44px; }
|
||||
.tabpanel > section, .tabpanel > section > * { min-width: 0; }
|
||||
select { max-width: 100%; }
|
||||
.tabpanel[hidden] { display: none !important; }
|
||||
section h2 { font-family: var(--font-crest); letter-spacing: 0.03em; }
|
||||
|
||||
@@ -471,11 +473,11 @@ footer { border-top-color: var(--line); }
|
||||
</div>
|
||||
<div class="controls" id="map-controls">
|
||||
<div class="target-group">
|
||||
<span class="lbl small muted">Rare dragons</span>
|
||||
<span class="lbl small muted">Bond a dragon</span>
|
||||
<div class="targets" id="targets-rare"></div>
|
||||
</div>
|
||||
<div class="target-group">
|
||||
<span class="lbl small muted">Other outcomes</span>
|
||||
<span class="lbl small muted">Rare sightings</span>
|
||||
<div class="targets" id="targets-other"></div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -581,13 +583,13 @@ footer { border-top-color: var(--line); }
|
||||
</section>
|
||||
<section id="share" aria-labelledby="h-share">
|
||||
<div class="section-head"><span class="eyebrow">Open by design</span><h2 id="h-share">Share & reproduce</h2>
|
||||
<p class="muted small">Everything on this page is recomputed in your browser from the raw form export. To update it, download the latest responses sheet (File → Download → Microsoft Excel) and load it with "Load a newer export" at the top. Column order does not matter, because questions are matched by their wording.</p></div>
|
||||
<p class="muted small">Everything on this page is recomputed in your browser from the raw form export. To update it, download the latest responses sheet (File → Download → Microsoft Excel) and load it with "Load a newer route export" above. Column order does not matter, because questions are matched by their wording.</p></div>
|
||||
<div class="grid2">
|
||||
<div class="panel"><h3>Copy the outputs</h3>
|
||||
<div class="btnrow"><button type="button" id="cp-reddit" class="primary">Copy Reddit post (Markdown)</button><button type="button" id="cp-csv">Copy coded runs (CSV)</button><button type="button" id="cp-json">Copy all results (JSON)</button></div>
|
||||
<p class="small muted">The Reddit post is written from the current numbers and filters.</p></div>
|
||||
<div class="panel"><h3>Read the code</h3>
|
||||
<div class="btnrow"><button type="button" data-src="engine.js">engine.js (all rules and statistics)</button><button type="button" data-src="app.js">app.js (this page)</button><button type="button" data-src="python/clean.py">clean.py</button><button type="button" data-src="python/analyze.py">analyze.py</button><button type="button" data-src="python/stats_core.py">stats_core.py</button><button type="button" data-src="register.js">register.js</button><button type="button" data-src="README.md">README</button></div>
|
||||
<div class="btnrow"><button type="button" data-src="engine.js">engine.js (all rules and statistics)</button><button type="button" data-src="app.js">app.js (this page)</button><button type="button" data-src="python/clean.py">clean.py</button><button type="button" data-src="python/analyze.py">analyze.py</button><button type="button" data-src="python/stats_core.py">stats_core.py</button><button type="button" data-src="solver.js">solver.js (best routes)</button><button type="button" data-src="explorer.js">explorer.js (the valley map)</button><button type="button" data-src="register.js">register.js</button><button type="button" data-src="README.md">README</button></div>
|
||||
<p class="small muted">The Python files are an independent second implementation. The test scripts confirm that both produce identical coded runs and identical odds ratios, p-values and model estimates.</p>
|
||||
<pre id="srcview" hidden></pre></div>
|
||||
</div>
|
||||
@@ -603,7 +605,7 @@ footer { border-top-color: var(--line); }
|
||||
<li><b>Cadet encounter.</b> Split into the scream choice (help, investigate and leave, or ignore) and its resolution (killed the bullies, squadmate's revenge, left them to the dragons, tourniquet, left the cadet, took their weapons). The fork in the road only exists after helping, so other branches are coded "(no fork)".</li>
|
||||
<li><b>Encounter branch.</b> A tree run with a Blue or Black recorded took the shadow. A tree run with Greens recorded descended slowly, and one with only a Red descended quickly. A valley run with an Orange, Brown or Blue recorded (or a Red marked "Changed my mind") passed the Red and reached the meadow.</li>
|
||||
<li><b>Outcome.</b> Bonded to the one dragon marked "Bonded!". Otherwise incinerated by the last dragon marked "Incinerated" in encounter order, or died before the hour. "Saved by another" on the Greens plus a bonded Orange or Brown counts as a rescue bond.</li>
|
||||
<li><b>Flags.</b> Rows are flagged, not deleted, when answers contradict each other: several directions or wings, Greens in the valley, two bonds, or a first sighting outside the documented pool. You can drop flagged rows with the checkbox above the map.</li>
|
||||
<li><b>Flags.</b> Rows are flagged, not deleted, when answers contradict each other: several directions or wings, Greens in the valley, two bonds, or a first sighting outside the documented pool. You can drop flagged rows with the checkbox on Deep Dive's route map.</li>
|
||||
</ul>
|
||||
<h3>2. Rates and their uncertainty</h3>
|
||||
<p>A rate is k events out of n runs that could have had that event. The denominator matters. The meadow Blue rate divides by runs that reached the meadow, not by all runs. Intervals are 95% Wilson score intervals, which behave well for small n and for rates near 0%:</p>
|
||||
@@ -611,7 +613,7 @@ footer { border-top-color: var(--line); }
|
||||
centre = (p̂ + z²/2n) / (1 + z²/n)
|
||||
half = z·√(p̂(1−p̂)/n + z²/4n²) / (1 + z²/n)
|
||||
CI = centre ± half</div>
|
||||
<p>With 0 events in n runs, the upper end is still informative. For example, 0 shadows in 367 bulk-log tree climbs gives an upper bound near 1.0%.</p>
|
||||
<p>With 0 events in n runs, the upper end is still informative. For example, 0 shadows in a few hundred bulk-log tree climbs still gives an upper bound near 1%.</p>
|
||||
</div>
|
||||
<div class="method">
|
||||
<h3>3. Comparing choices</h3>
|
||||
@@ -627,18 +629,22 @@ q = Benjamini–Hochberg: sort p, q(i) = min over j≥i of p(j)·m/j</div>
|
||||
<div class="formula">logit P(event) = β₀ + Σ βⱼ·xⱼ (x = 0/1 indicators; reference = most common answer)
|
||||
fitted by Newton–Raphson with a small ridge penalty λ = 1 on the slopes
|
||||
adjusted OR = exp(βⱼ), 95% CI = exp(βⱼ ± 1.96·SEⱼ)</div>
|
||||
<p>The ridge penalty keeps estimates finite when an answer has 0 events. It shrinks extreme odds ratios slightly toward 1, which makes the model more cautious. Route rankings use the Mantel–Haenszel odds ratio across four strata (bulk logs, form runs chasing Blue, chasing Black, everything else) for the same reason.</p>
|
||||
<p>The ridge penalty keeps estimates finite when an answer has 0 events. It shrinks extreme odds ratios slightly toward 1, which makes the model more cautious. Route rankings use the Mantel–Haenszel odds ratio across strata of data source and chase goal (bulk logs; form runs chasing Blue, Black, or "Blue or Black" on the newer form; everything else) for the same reason.</p>
|
||||
<h3>5. What this data cannot tell you</h3>
|
||||
<ul>
|
||||
<li>It is self-reported and self-selected. Runs worth bragging about are over-represented, and that inflates every rare-dragon rate. Bulk logs are the least selected rows.</li>
|
||||
<li>Runs are not independent. One player may log dozens of runs, and the form has no player ID, so intervals are somewhat too narrow.</li>
|
||||
<li>The form records only stage-level choices. It does not record how you reacted to the first dragon (lower eyes, hold still…) or most choices inside an encounter, so route claims that depend on those cannot be tested here.</li>
|
||||
<li>The form records mostly stage-level choices. The newer form asks how you reacted to the first dragon, but most riders answer "unsure", and it does not record the answers given inside a bonding encounter, so route claims that depend on those cannot be tested here.</li>
|
||||
<li>The form records dragons you <i>attempted</i>. A player who saw the Blue but chose the Orange would not record the Blue, so Blue sightings are slightly undercounted.</li>
|
||||
<li>Step-by-step survival inside an encounter comes from the community PDF, which coded the free-text answers by hand. It is shown as published and cannot be recomputed here.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<h3>Missing answers</h3>
|
||||
<h3>6. Best routes, the valley map and The Odds</h3>
|
||||
<p class="small">The valley map and The Odds come from a solver (<code>solver.js</code>) that treats a run as a decision tree. Your choices are decisions (company, direction, the cadet encounter, the fork, tree or valley, how to climb down, whether to face the valley Red, and at every bonding encounter whether to attempt the bond or die on purpose). The game's rolls are chance events: which dragon appears first, whether you die at the sighting, in the fight or before the hour, whether the shadow appears and which dragon it is, which dragon waits in the meadow, and how the bonding encounter ends.</p>
|
||||
<p class="small">Each roll's probability may depend on the choices before it. It is estimated with hierarchical Dirichlet back-off: the estimate for a full history is pulled toward the estimate for a shorter history, which is pulled toward the overall rate. How strongly is chosen from the data for each roll (empirical Bayes), so the solver does not chase noise in small groups. The best route is then found by backward induction, for two goals: the chance of bonding the dragon on this attempt, and, for riders who die on purpose whenever a run goes wrong, the chance that the account eventually ends on that dragon rather than another (maximised by Dinkelbach iteration). Ranges come from 200 posterior draws; "stays best in N%" is how often the recommended choice is still best across those draws.</p>
|
||||
<p class="small">Encounter outcomes use only genuine attempts: runs where the rider wanted that colour, any dragon, or said they would not seek Malek. The two summary cards on The Odds use the same rule in reverse: runs where the rider died on purpose at an encounter they did not want are left out, so they describe cadets who went into the valley and either bonded or died. The "low-bias" numbers use only bulk logs and form runs from riders who were not chasing a rare dragon.</p>
|
||||
<h3>Missing answers</h3>
|
||||
<p class="small">"Unsure", blank answers, conflicting answers and questions an older version of the form did not ask are treated as missing information, never as a choice. Each comparison uses the runs that answered that question; models use runs that answered every question in them (complete cases). "I've lost count" counts as a later attempt. The only exception is the chase goal used to adjust for reporting bias: runs from before that question existed stay in the models as their own adjustment group, but that group is not shown as a finding. The solver and the valley map ignore missing steps in the same way.</p>
|
||||
</section>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user