So many great ideas! I’d have to alter the processing a bit to allow choosing between cumulative and non-cumulative, but that’s doable I think.
As for the split out app/guru that data is totally available (I’m currently summing them). Hmm, dates first though. I may have some time tomorrow.
Yes, the vertical lines are fixed. Now if you see a line to 0, it means there’s actually a zero somewhere… or reviews done before 2017 when WK first started tracking them
Version 1.0.5 is out
@Eekone, @Marifly, @sporadic
There is now a basic ‘start at date’ in the options. It’s not completely the functionality I had envisioned, but it does work for the time being (more advanced zoom may come later).
Thank you, @rwesterhof!
The Start date even if basic is nice to have (especially with the fact that I had those large gaps) Great Work!
May I suggest a finer graduation for the chronological axis, perhaps unlabeled marks per month or trimester? After level 60, there are only the marks for entire years.
That’s a good idea! I’ll put it on the list!
A slow start, plus few resets and breaks when life happened.
Thanks for the cool script, @rwesterhof!
We should start a club for us spiky boys and girls
Resets make for interesting graphs, that’s for sure. My last spike wasn’t a reset, but a “I’m determined to get through this backlog without resetting” kind of spike. I think it ended taking longer to clear than resetting back 5 - 10 levels.
Version 1.1 includes
- option to turn off cumulative view
- option to split out apprentice/guru stages
- option to add monthly or quarterly chronological x axis label markers
Wow, it’s really beautiful with the detail stages. If I turn off the cumulative view it gets a little messy, like a seismograph during an earthquake :
Yeah, cumulative + detail stages is not a great combination. But there was no good reason to specifically exclude it - it does work so far anyway
My new favorite is the coloring of the difficulty graph. It’s much more obvious where I’ve gotten to with my burns, and why there’s such a spike in errors
The non-cumulative with detailed stages is certainly noisy, but if you turn up the running average, it shows some interesting things.
For example. That my Guru 1 has been increasing and tops out above my App1&2. I’ve long had the sense that I have a lot of reviews that bounce between App3 and Guru2 (my mid to long term memory is not as good as my shorter term), and this bears it out. This isn’t visible in any of the other graphs.
And yeah, the detailed stages cumulative is just so pretty. I love this chart.
@rwesterhof I have updated the review cache to not round the epoch to the minute. It now saves dates with full accuracy. You probably want to update the review cache url to take advantage of the extra accuracy.
The new version number is 952514
@rwesterhof 952514 had a bug, the new version number is 952556.
Look to be working smoothly with the update. Thanks!
Published version 1.1.1 dependent on 952556
I think there is something wrong with error percentage with this script, I am sure to be making way more mistakes since lvl 22, I am at 24 now, but with this graph it shows otherwise
I can take a look, but your graph looks pretty normal to me. It takes a while for items from a level to reach the higher stages (guru II, master, enlightened), and those tend to be the stages with lower accuracy because you haven’t seen the items in a while. So I would expect the error percentage to be higher for levels that are a little further back, as opposed to the most recent levels, for which you’ve done mostly apprentice and guru reviews.
For your current level, there won’t have been a lot of reviews at all yet, and pretty much exclusively apprentice level reviews. Your current review sessions will still contain a lot of lower level items, so any mistakes on those count towards the lower levels.
If you add the stage colors and hit redraw, you will usually see color changes exactly at the point the accuracy takes a hit because the items for that level are coming up for enlightened or burn stages.
But I’ll take another look at the code and let you know if I find something.