If I managed a 4BLD success in ANY time, I’d be super excited. Well done. Looks like a decent overall weekend at the competition.Another comp from this weekend. http://cubecomps.com/live.php?cid=3961&compid=48
Was happiest about sub-10:00 4BLD. Wasn't sure I could do that in comp.
Got a OPWR (old people world record) with a lucky skewb single (4.34). Had a +2 in the average.
A non-lucky sub-16 3x3 single, but sub-20 average still eludes me. Second round, did the wrong PLL on one solve, and put multiple F2L pairs in the wrong slot on two solves.
Had a decent 3BLD success. The two DNF's were in the 2:10's, one was 3 corners, one was 3 edges.
One bad round of clock, one good round of clock, 2nd best avg and single.
Still don't care about OH, but got PBs there.
Another comp from this weekend. http://cubecomps.com/live.php?cid=3961&compid=48
Was happiest about sub-10:00 4BLD. Wasn't sure I could do that in comp.
Got a OPWR (old people world record) with a lucky skewb single (4.34). Had a +2 in the average.
A non-lucky sub-16 3x3 single, but sub-20 average still eludes me. Second round, did the wrong PLL on one solve, and put multiple F2L pairs in the wrong slot on two solves.
Had a decent 3BLD success. The two DNF's were in the 2:10's, one was 3 corners, one was 3 edges.
One bad round of clock, one good round of clock, 2nd best avg and single.
Still don't care about OH, but got PBs there.
Wow! That’s some good 6x6 work there! I struggle to get under 6:00 still. Someday I’ll take the time to get good with bigger cubes. I’d like to, it just takes SO long to practice those—especially when it takes so long to solve it just once.My at-home 6x6 is making up for the official disappointment: Just finished a 4:10.02 Ao5 with a 4:06.34 Mo3.
1. (3:56.38) @2019-02-07 11:28:53
2. 4:06.57 @2019-02-07 11:36:34
3. 4:16.06 @2019-02-07 22:00:20
4. 4:07.43 @2019-02-07 22:05:58
5. (4:40.73) @2019-02-07 22:20:18
I just saw the Great Lakes Championship in May. It's sorely tempting. I am likely to be busy planting corn, or getting ready to, about then, but if I just took Friday I could 4BLD, 5BLD, FMC, and Feet. Surely I could get big blind down my then. It's probably not worth the $50 plus the trip to Madison, but it is tempting.
Any chance you’re going to Nationals in Baltimore this year?
Ahhhh makes sense.No, I’m afraid. It’s hard enough to get away from the farm to go to a close by competition, Baltimore is much too far away to be worth it. That’s why I organize comps: so I can hold them close enough that I can get there to compete.
If I were to reconstruct the full solve and analyse it in detail, I could probably find 20+ mistakes, but just watching this at normal speed, your solve seemed to be fine overall.I figured out how to record me solving, so I recorded a fairly typical 6x6 solve. I’m surprised at my turning speed when I do turn, and at how long and frequent my pauses are.
Good job. Someday I’ll be able to solve 6x6 that fast, but for now, I’ll live vicariously through your speed improvements.I figured out how to record me solving, so I recorded a fairly typical 6x6 solve. I’m surprised at my turning speed when I do turn, and at how long and frequent my pauses are.
The cumulative limit is the total time allowed for all attempts.May anybody explain me "cumulative limit" at comps? The question is about what will be stored in WCA profile in case of not passing those limit. F.e. cumulative limit is 20 mins and attempts are 5:20-5:00-10:05, or 9:10-5:50-5:05.
Thanks! The meaning of the cumulative limit is quite understandable. Does this means that there will be single DNF for the event in the profile?The cumulative limit is the total time allowed for all attempts.
To follow your example, if the cumulative limit is 20 mins and your first two attempts are 5:20 and 5:00, then you only have 9:40 to complete your third attempt. In the case that it took 10:05, as your example, then you would be awarded a DNF for the third attempt.
Likewise for your second example, you would have missed by 5 seconds on the third attempt and would be awarded a DNF.
In neither example would you receive a mean of three due to the final being officially a DNF.
I don’t think the database distinguishes between running out of time and an unsuccessful attempt.
My local comps favour a 10 min cumulative 3BLD limit. Which is fine for me to get 2 valid attempts but adds a lot of pressure if I want to get a mean of 3. So, even if I get 3:30 and 3:30, I would then be allowed 3:00 for my final attempt. Anything more would DNF.
Technically the judge is supposed to stop the attempt when you hit the time limit, so it would be literally "did not finish" and there's no distinction to make.I don’t think the database distinguishes between running out of time and an unsuccessful attempt.
I think yes. Similarly to the single attempt time limit. The difference is that you have an opportunity to maneuver to pass limit within several attempts instead of one.Thanks! The meaning of the cumulative limit is quite understandable. Does this means that there will be single DNF for the event in the profile?
Thanks! This is some fantastic feedback!If I were to reconstruct the full solve and analyse it in detail, I could probably find 20+ mistakes, but just watching this at normal speed, your solve seemed to be fine overall.
(i) For the last two centres, don't solve the inner bars first. Do a 2×4 on the left, then the remaining inner bar, then the remaining outer bar. This avoids the situation where you need to use multiple commutators to solve the stray centre pieces at the end.
(ii) During edge pairing, it looks like you're holding the cube with the sliced centres on the S slice (U, R, D, L) rather than the E slice (F, R, B, L). I don't know if this is just an artifact of the camera angle you used, though. In any case, S-slice is super bad because you have to rotate almost every time you insert an edge; with M-slice or E-slice edge pairing, you only need to rotate to deal with "misoriented" edges.
(iii) In L4E you're constantly rotating between having the edges on M and having the edges on S. As above, by sticking to E-only or M-only, you can reduce the number of rotations used a lot.
(iv) The FU moves on the last F2L pair are… interesting. I think most people would consider doing a y' rotation to convert it to RU 2-gen, but this isn't a big deal.
(v) Yikes, that U perm. Just because you can do M slices on magnetic big cubes doesn't mean you should. (I'm not sure if the R2 you did at the start was because you were going to execute the RU alg, but weren't confident in it.)