• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easy — create your account today.

    Already a member? Log in here to hide this message and start participating.

Prisma Puzzle Timer

ok i use sessions just to keep apart my progress every time i solve the cube, for example if i do an average of 12 today and tomorrow i do an average of 5 getting better times, the puzzle timer tell me that i have a new best avg of 12 wich is not logical, because i just did 5 solves, and the other thing is because sometimes i like to see my progress so i search the sessions i did some time ago, but in the puzzle timer it shows all the times together.
But maybe other people prefer it that way, is hard to keep everyone happy :P

The times are ordered by date in the history. You can select only the times in which you're interested and the histogram/graph/statistics will be updated accordingly.
 
The only thing I miss, is that you can insopect de cube 15 seconds, or so long you want.
And sound when you press the space bar or your last 3 seconds the timer counts down.
I put something for the screen so I can't be nervous.

Yeah, I would comment the same. Cubetimer.com and the Bellon cube timer both have very nice "count down" features with variable inspection time. I use those both and it's a good feature to have. I don't use a stackmat, but I can imagine if you do, you wouldn't use this feature. Still, would be a nice one to add.

It's done and it'll be in the next release. It works with stackmat timer too.
 
I'm not sure if anybody reported this, but there are rounding problems with the average of 12. (maybe with average of 5, too)

Here are examples
Code:
First of all WCA Regulations states

[I]9f1) All timed results under 10 minutes, and corresponding averages/means are measured in hundredths of a second, with averages/means rounded to the nearest hundredth of a second (x.004 becomes x.00, x.005 becomes x.01).[/I]

----------------------------------------------------
These are taken from session history of [I]Puzzle Timer[/I].

Mean:               0.11
Standard deviation: 0.05
Best Time:          0.06
Worst Time:         0.21

Best average of 5: 0.06
  5-9 - 0.06 (0.11) 0.06 (0.06) 0.08

Best average of 12: [B][U]0.11[/U][/B]
  1-12 - 0.15 0.18 (0.21) 0.18 0.06 0.11 0.06 (0.06) 0.08 0.13 0.08 0.08

----------------------------------------------------
0.15+0.18+0.18+0.06+0.11+0.06+0.08+0.13+0.08+0.08=1.11
1.11/10 = 0.111

[B]Average of 12 is 0.11 and it is.
[/B]
----------------------------------------------------
Mean:               0.11
Standard deviation: 0.04
Best Time:          0.06
Worst Time:         0.21

Best average of 5: 0.06
  4-8 - 0.06 (0.11) 0.06 (0.06) 0.08

Best average of 12: [B][U]0.10[/U][/B]
  1-12 - 0.15 (0.21) 0.18 0.06 0.11 0.06 (0.06) 0.08 0.13 0.08 0.08 0.15

----------------------------------------------------
0.15+0.18+0.06+0.11+0.06+0.08+0.13+0.08+0.08+0.15=1.08
1.08/10 = 0.108
[B]
So average of 12 is [U]0.11[/U] but iT shows up as 0.10.[/B]
----------------------------------------------------

Looks like average of 5, too.

Best average of 5: [B][U]0.06[/U][/B]
  4-8 - 0.06 (0.11) 0.06 (0.06) 0.08

0.06+0.06+0.08=0.2
0.2 / 3 = 0.0666666667

[B]So average should be rounded up to 0.07[/B]

Thanks Davee. The times were being truncated rather than rounded. It's now fixed.
 
i have a problem adding manually a solution using History -> Add solutions...
It doesn't accept values like 16.04, 15.07, ecc., i mean values starting with zero in the decimal part. It always reverts the values in 16.40, 15.70, ecc., even using the edit button after import.

I'm using the latest mercurial repository version.

Thanks otsyke. It's a bug. I'll fix it as soon as possible.
 
The Mefferts scheme for the one I got is:

F: Green
B: Blue
U: Yellow
D: Orange
L: Red
R: Pink

So if we include skewb as an official event my skrewb should be scrambled with green front and yellow top as yellow is the lightest color in my scheme.
 
I think that new configuration stuff broke the backwards compatibility with the database. I get a null pointer if I start the timer with an old database. But then I run it from the source code and perhaps this is why Walter hasn't released it yet :)
 
Back
Top