[Feature request] Estimated Total Knowledge over time

Expertium · December 18, 2024, 11:58am

Also, can you make the x axis in dates? Like, November 2024.

Anon_0000 · December 18, 2024, 12:56pm

As a sidenote / question: Is there a reason why the graphes in anki have no x and y axis titles? Normally in maths and sciences you’re required to add those so that it’s obvious what the graph is showing.

E.g.

Here the x axis would be something like date or x days ago and the y axis something like amount of cards. The old graphs apparently had that, see the picture called old here.

Danika_Dakika · December 18, 2024, 5:46pm

I assume it’s just a stylistic choice, since all of that units information is captured (and with specificity) in the hover/tap pop-up. It might seem unusual from a math/science perspective – but from a data-presentation perspective, I don’t mind that it gives the graph a chance to stand alone as a visual.

Anon_0000 · December 18, 2024, 6:15pm

I guess that makes sense.

I’d still prefer the “scientific way” since it allows me to see all the important information at a glance without having to hover over every graph. And while I personally can deduce the meaning of the axis most of the time, I don’t think it’s that obvious for everyone.

But that’s a discussion for another topic. I’ll open one in the near future if there isn’t already one.

rossgb · December 18, 2024, 6:43pm

I guess part of it might be the requirement that they work well on small screens.
On a mobile phone the axis labels may eat a significant amount of the available space.

If that is the issue you could make them responsive so the labels only show when you have plenty of screen space.

sorata · December 18, 2024, 8:17pm

Yup, we already have text overflow issues in this screen and in the simulator too where we have a label for y-axis.

It actually looks better without the labels according to me.

A_Blokee · December 19, 2024, 10:05pm

I got the memorised data from the simulator showing. Looks like it doesn’t include the memorised value from the cards before its first simulated review though making the graph somewhat useless.

branch:

L.M.Sherlock · December 20, 2024, 3:17am

Oops. I find a bug when I analyze this problem… We forgot to update memorized_cnt_per_day when learning new cards in the last refactor.

Edit: Yep, this problem does exist because we only update the memorized_cnt_per_day when the card is reviewed in the simulator. I will submit a PR to improve it.

PR:

sorata · December 20, 2024, 6:57am

Can you rename “count” to “reviews”? The y-axis title in the image is also “memorised count” which makes it a bit confusing because it’s not clear what “count” is.

And if you’re willing to make some other UI changes, the radio buttons and the “Simulate”/“Clear last simulation” should have some gap between them.

A_Blokee · December 20, 2024, 1:20pm

Works great now!

PR:

L.M.Sherlock · December 20, 2024, 1:24pm

I invited you to join OSR, and I hope you can help me review the code.

Expertium · December 20, 2024, 1:43pm

Well, now I want a native “Estimated total knowledge over time” (historical, not simulated) even more

A_Blokee · December 20, 2024, 9:24pm

The graphs values are close enough that I assume its all working as intended.

Fully zoomed out:

A_Blokee · December 31, 2024, 3:32pm

Note the difference between the end value and “Estimated total knowledge”

I have spent longer than I probably should have trying to get this to work.
Does it matter that there’s a discrepancy between SSE and native Anki?

Here’s the code in case someone wants to check if I’ve done something stupid. (I get the feeling its something to do with manual reviews)

github.com

Luc-Mcgrady/Anki-Search-Stats-Extended/blob/master/src/ts/MemorisedBar.ts

import _ from "lodash"
import { type Card, createEmptyCard, type FSRS, fsrs as Fsrs } from "ts-fsrs"
import type { DeckConfig } from "./config"
import { dayFromMs, IDify, today } from "./revlogGraphs"
import type { CardData, Revlog } from "./search"

export function getMemorisedDays(
    revlogs: Revlog[],
    cards: CardData[],
    configs: typeof SSEother.deck_configs,
    config_mapping: typeof SSEother.deck_config_ids
) {
    let deckFsrs: Record<number, FSRS> = {}
    let fsrsCards: Record<number, Card> = {}

    let cards_by_id = IDify(cards)

    function getFsrs(config: DeckConfig) {
        const id = config.id
        if (!deckFsrs[id]) {

This file has been truncated. show original

The tests pass at least?!?

github.com

Luc-Mcgrady/Anki-Search-Stats-Extended/blob/6ee11752e13f8a2499cf2d90847470595c112238/test/memorised.test.ts#L38-L60


      
          test("Stability", ()=>{
              const card = new RevlogBuilder()
              const FSRS = fsrs()
          
              const revlogs = [
                  card.review(1, 1),
                  card.review(3, 3),
                  card.review(21, 3),
                  card.review(80, 3),
              ] as Revlog[]
          
              const memorised = getMemorisedDays(revlogs, [{
                  ...card.card(),
                  did: 1
              } as any],
              configs,
              mappings)
          
              const OFFSET = 10

This file has been truncated. show original

My real question is,
is this worth including in SSE in what appears to me to be a somewhat broken state? Or should I skip it, release the other graphs/features I did ages ago, and include it when its completely correct?

Maybe I should even ditch it as an SSE graph and try to put it in native Anki like I probably should have from the start.

Expertium · December 31, 2024, 6:01pm

@L.M.Sherlock

L.M.Sherlock · January 1, 2025, 2:55am

It’s good enough to ship! I will check the code later.

Expertium · January 1, 2025, 2:21pm

Well, my original idea was having an estimated total knowledge graph in Anki itself.
Btw, why candlestick charts? I think they are hard to read for most people (aside from people who are into trading/investing, lol). A curve is preferable, like in the SuperMemo image that I posted at the very beginning.

A_Blokee · January 1, 2025, 4:20pm

You can opt in for a bar chart but I find that makes it harder to see the small daily differences.

Also bars and candlesticks are the 2 charts I already have programmed in XD.

Expertium · January 1, 2025, 6:09pm

Why not a curve?
Btw, it would be neat to have Last week/Last month/Last year/All time
Also, nitpick: round the numbers. It doesn’t make much sense to display non-integer numbers, since this is supposed to be interpreted as “the number of cards”.

A_Blokee · January 1, 2025, 6:29pm

Curve would probably be better but it would be different from the rest of the addon and take time to implement.

Oh and you can get the “last week” and such if you scroll the graph though it might be annoying.

Yeah I should round the number really but I feel like that would be hard to explain why the graph would go down as the number stays the same.

Instead I opted to try and explain what the graph actually represents. Probably poorly but oh well.

Topic		Replies	Views
Let's make the True Retention table look better FSRS	49	790	December 16, 2024
Estimated Total Knowledge graph over time Suggestions	35	1057	February 19, 2026
Due Column - Changing Days (from Whole Numbers to Decimals in Scheduling) Suggestions	59	807	December 9, 2024
"Card Retrievability" Graph range Suggestions	40	577	November 9, 2025
25.02 possible bug - minimum recommended retention 0.70 FSRS	19	575	February 27, 2025

[Feature request] Estimated Total Knowledge over time

Related topics