Screen tree, register rows in the master list, and bot runs coded from the picks that were played
CI / test (pull_request) Canceled after 0s
CI / test (pull_request) Canceled after 0s
- analysis/tree/build_tree.py -> data/public/tree.json, analysis/reports/TREE.md: every screen the bot has seen, every option, where each led (fixed or dice, with ranges), best known picks per colour chosen cautiously, where any picks end, and the untested options. solver.js screenPick(): least-tried and Thompson picks from the tree. - The bot logs a pick it then overrode as a step: 37 runs were coded with choices they never made. Importer and graph.js now use the played steps only. - runs_clean.csv: the Unofficial Dragon Register's 288 bonded dragons are in the master list as outcome-only rows, flagged (no analysis uses them). - Cycle, refresh and the bot kit rebuild and carry the tree; tests check every generated report is current. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014jqCC2LZ4x1WHQ1V57nTsv
This commit is contained in:
co-authored by
Claude Fable 5.2
parent
d01ec46fcc
commit
f8e4f575f4
@@ -78,3 +78,22 @@ holding its gaze are unexplained, and the screens before it are where the explan
|
||||
the difference is something the site knows about the account, and these are the candidates we can see.
|
||||
|
||||
The plan updates itself from the runs: a finished experiment stops being assigned and its share goes to the others.
|
||||
|
||||
## The screen tree, and two things found in the logs (16 November)
|
||||
|
||||
`tree.json` is now in the kit: every screen the bot has stood on, every option on it, how often each was played and
|
||||
where it led (`analysis/reports/TREE.md` is the readable version). 47 of the 116 options seen have never been played.
|
||||
|
||||
- **Picking from the tree.** `Solver.screenPick(tree, sceneId, offeredTexts, { mode, seed })` returns the option to
|
||||
pick. `plan.screenPicks` says when: `least-tried` in the mapping experiment (fills the gaps first), `thompson`
|
||||
while bonding the target dragon (tries untested answers, drops the ones that kill). The four deadly screens of the
|
||||
Blue encounter have only ever been answered one way each, so their other answers are unknown.
|
||||
- **Overridden picks are in the logs as if they were played.** In 37 runs the bot logged the atlas's pick with
|
||||
`to: "BURNED"` and then, on the same screen, the pick its own rule made (91 steps: first direction 37, the fork 33,
|
||||
the dagger 11, the first dragon 9). The atlas now drops such steps, in the importer and in `graph.js`
|
||||
(`playedSteps`), so the runs are coded with the choices that were made. Two things for the bot: log an overridden
|
||||
recommendation as something other than a step, and note that in those runs the atlas's direction and fork advice
|
||||
never took effect (`ENTER_TOWARDS_FOREST_CENTER` and `ROAD_FORK_DEEPER_FOREST` won). The experiments need the
|
||||
plan's picks to win over those rules.
|
||||
- **The best-reported route has already been played 64 times on later attempts** (alone, west, engage the smaller
|
||||
cadet, squadmate's revenge, fork west) with no shadow, which matches riders' 1 in 80.
|
||||
|
||||
Reference in New Issue
Block a user