Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added a fancy chart.md #517

Merged
merged 2 commits into from
Nov 4, 2023
Merged

Added a fancy chart.md #517

merged 2 commits into from
Nov 4, 2023

Conversation

Expertium
Copy link
Collaborator

It illustrates how workload changes with retention.

It illustrates how workload changes with retention.
@L-M-Sherlock
Copy link
Member

I think it would be better:

image

@Expertium
Copy link
Collaborator Author

Expertium commented Nov 1, 2023

I was using 1/interval to approximate the workload. If you want to take into account the fact that for lower values of retention, workload increases due to the user having to relearn more forgotten cards, then this probably will require using the simulator to make an accurate chart.

@L-M-Sherlock
Copy link
Member

OK. I will draw one with simulator.

@Vilhelm-Ian
Copy link

I don't get this chart. The optimizer gives different values for a smaller workload

@Expertium
Copy link
Collaborator Author

I don't get this chart. The optimizer gives different values for a smaller workload

As I said, I was just using 1/interval. This takes into account how intervals themselves changes, but doesn't take into account the fact that as intervals become shorter, the user has to re-learn more.

@L-M-Sherlock
Copy link
Member

image

R = range(60, 98)
cost_per_memorization = [118.46067691245344,
 117.996435848432,
 116.9026381695129,
 116.90439453733136,
 117.0676543398416,
 116.87291721228723,
 116.31486268004336,
 115.85366389346582,
 116.4216439101658,
 115.19567302651005,
 114.87530852659273,
 113.53655325213391,
 115.13691533864515,
 115.62138703770871,
 114.76960076774199,
 115.40369340768487,
 115.82480378468483,
 114.9575330411633,
 116.94736342126731,
 117.58531651606509,
 117.36775574433011,
 119.32339071100732,
 120.45015145509191,
 122.19685831432899,
 124.6350740547518,
 126.99968537807649,
 129.70336675687713,
 132.41933601503496,
 136.80095507331478,
 142.44879085247103,
 148.0477921109703,
 157.41139358191,
 167.33382956745544,
 181.09913246821685,
 199.26041948396235,
 225.03989356583492,
 264.3108002037564,
 337.1411969520337]

@Expertium, could you help me draw one with above data?

@Expertium
Copy link
Collaborator Author

You mean with colors? Ok, I'll do it later.

@L-M-Sherlock
Copy link
Member

You mean with colors? Ok, I'll do it later.

I mean the style of your original chart. Thanks!

@Expertium
Copy link
Collaborator Author

Is workload in minutes or reviews?

@L-M-Sherlock
Copy link
Member

It's in minutes. However, it's better to keep the specific values hidden and only show the relative sizes on the chart.

@Expertium
Copy link
Collaborator Author

It's in minutes. However, it's better to keep the specific values hidden and only show the relative sizes on the chart.

I agree about not showing exact values, but I think it's best to specify what units (time or reviews) is workload measured in

@Expertium
Copy link
Collaborator Author

Expertium commented Nov 4, 2023

Workload and retention, more accurate
Also, mention that the exact shape of the curve depends on the user's parameters and habits.

@Expertium
Copy link
Collaborator Author

Oh, and I also recommend adding the add-on compatibility table to the second guide (about built-in FSRS) too.

@L-M-Sherlock
Copy link
Member

Could you update this branch? I will merge it.

@L-M-Sherlock L-M-Sherlock added this pull request to the merge queue Nov 4, 2023
Merged via the queue into open-spaced-repetition:main with commit 73b5c7b Nov 4, 2023
@L-M-Sherlock
Copy link
Member

Oops. The chart seems misleading. Do you set the y axis' intercept to zero?

image

@Expertium
Copy link
Collaborator Author

Expertium commented Nov 4, 2023

What do you mean?
Ah, ok I see. Yeah, it makes it seem like the workload will increase from barely above zero to much higher values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants