Hyperspeedcube
Hyperspeedcube copied to clipboard
HactarCE
session times
session times
like how in cstimer you can see ao5 and graphs. this is kinda conflating the thing that shows your ao5 at all times and the more advanced session stats tools.
use cases / requirements
- a session is a collection of solves
- a session should probably only have solves from a single puzzle
- some people put every solve in a single session, others make a new session every actual physical session
- maybe solves can be in multiple sessions? this seems complex and isn't used much
- i want to have a 3^4 session for 3block and cfop to compare them
- view all times, pb, ao5, standard deviation, with graphs for these
- would be nice if graphs displayed physical session boundaries (if you're putting all solves into one session)
- like instead of x-axis being solve count, it could be unix time
- should be able to go from viewing a solve's time to its replay file
replay files and sessions
- i'm assuming that all solves' replays are (auto) saved (locally)
- what is the relation between replay files and sessions?
- want to avoid opening like a thousand relay files just to grab your pb
- probably don't want to store session inside of the replay because replays are also for sharing with other people
- maybe you have a folder of sessions where each session is a txt with a list of paths to replays in that session
- so sessions/session_1.txt (or json or whatever)
- also need to store times to avoid needing to open the replay
- this is duplicated information which is evil
- ig try it without storing times and opening all the replays then benchmark it
- where should a replay be stored?
- a flat folder of files with (hierarchical) tags / names with path is better then nested folders for sometimes
- so you'd have saves/3x3x3x3_solve1.hsc instead of saves/3x3x3x3/solve1.hsc
- this means that you can put data into what would have otherwise been a folder
- so you could put a summary into saves/3x3x3x3.txt
- idk if it this really applies here but i think it's cool
- probably should just be folder of puzzles
- so saves/3x3x3x3/solve1.hsc
- a flat folder of files with (hierarchical) tags / names with path is better then nested folders for sometimes
- what should the name of a replay be?
- unix time of creation is probably best
