I've persuaded Claude to make a few changes:
1) instead of dividing by (actual + expected) / 2, it will divide by (actual + expected + 2) / 2, effectively downgrading extremely low count events
2) low count cells are also marked with '?' (fewer than 7 instances) and '??' (fewer than 4)
3) there is a tooltip that shows the actual and the expected, should activate by hovering the mouse on a desktop and via a long press on touchscreens. The tooltip doesn't work very well on touchscreens, but I'm afraid if I start arguing with Claude on this one, it will only make it worse.
By default the page is cached locally, so you may need to refresh the page a couple of times before you get the latest version. All past statistics will not be recalculated automatically, so they probably should be deleted and recomputed if needed.
Edit: also Claude made a few attempts of fixing the problem with wrong counts when looking for characters that are already present in the string, I accepted the version that I found the most plausible. It involves reducing the count of available characters by the count of the character in the search string times the count of the search string in the text, but not including this character if it's the last in the search string for preceding characters mapping and the first for the following characters mapping. It probably sounds complicated, but it's the cleanest that Claude offered and it probably works fine in most cases.
1) instead of dividing by (actual + expected) / 2, it will divide by (actual + expected + 2) / 2, effectively downgrading extremely low count events
2) low count cells are also marked with '?' (fewer than 7 instances) and '??' (fewer than 4)
3) there is a tooltip that shows the actual and the expected, should activate by hovering the mouse on a desktop and via a long press on touchscreens. The tooltip doesn't work very well on touchscreens, but I'm afraid if I start arguing with Claude on this one, it will only make it worse.
By default the page is cached locally, so you may need to refresh the page a couple of times before you get the latest version. All past statistics will not be recalculated automatically, so they probably should be deleted and recomputed if needed.
Edit: also Claude made a few attempts of fixing the problem with wrong counts when looking for characters that are already present in the string, I accepted the version that I found the most plausible. It involves reducing the count of available characters by the count of the character in the search string times the count of the search string in the text, but not including this character if it's the last in the search string for preceding characters mapping and the first for the following characters mapping. It probably sounds complicated, but it's the cleanest that Claude offered and it probably works fine in most cases.


![[+]](https://www.voynich.ninja/images/collapse_collapsed.png)