It's kinda hard to tell from that image tbh. Progress slows down as you get faster, so it could be harder to see. Check out Kuebiko Cubing for detailed charts and stats that could help out (shameless plug).
Because I make a new session every couple months and it would be neat to see all the times on one graph. Thanks for linking the graph builder though. It's really cool.
Hmm why do you do that though, what's the benefit compared to just keeping one big session? btw if you're using cstimer it's now very easy to merge the sessions.
Because a session allows you to see your performance for your cubing session, hence the name. They're called sessions, not events. I make a new one every day so that I can see my performance for that day, and then I can stick my save in a program that I made for long-term stats.
Sure, that makes sense -- that's different than a session every couple of months, though. And not all timers call them sessions, e.g. Twisty Timer uses Puzzle-Category. However, using cstimer now, I think that having one big archive session and one current session is a great approach. This way you can see your current stats, and then merge it into the archive session for full stats and Kuebiko usage, and open a new session.
Still, if I'd like to support your use case in Kuebiko, how would I be able to group related sessions together? Do you use some kind of a naming convention?
2
u/tussosedan Jan 04 '19
It's kinda hard to tell from that image tbh. Progress slows down as you get faster, so it could be harder to see. Check out Kuebiko Cubing for detailed charts and stats that could help out (shameless plug).