pll_trainer: helps you practice PLL's

rjohnson_8ball said:
A programming idea for 3x3 PLL recogition... First, establish the user's preferred colors for ULFRBD. (This can be saved for later runs.) Next, flash a row of 6 colored squares to indicate the up-left and up-front edges. Now the user needs to identify the PLL the pattern indicates. The answer can given as a keyboard character: A,E,F,G,H,J,N,R,T,U,V,Y,Z. The user can, if desired, use the left/right arrows to cycle the U face edge colors in the display. This will not test which of the 4 G patterns (for example) the user recognizes, but that's not so bad. Maybe something can be figured out for that.
Click to expand...
I wrote this over the weekend: http://brunson.com/drillsergeant/ It does pretty much what you describe without the "type your answer" part of it.

Choose your color scheme and "Use only PLLs, no OLLs", then click "drill" and it will show you a PLL. I either recognize it or not, you can rotate the cube with the mouse if you need to see the other sides. Unless you're color neutral like me, you probably don't want to check the random cube rotation before scramble, you'll want to adjust the color scheme to put your opposite cross color on top.
 
fanwuq: I think the point is more that you don't practise one PLL over and over to get it fast at one point in time, but to get a general overview of all your PLL's relative to expected appearance, in a more realistic manner to an actual solve.

(Long sentence, sorry).
 
Dene said:
fanwuq: I think the point is more that you don't practise one PLL over and over to get it fast at one point in time, but to get a general overview of all your PLL's relative to expected appearance, in a more realistic manner to an actual solve.

(Long sentence, sorry).
Click to expand...

Nevermind everything. Let me get off this topic. I don't think PLL is really much of a problem for me. There are many ways to practice it. I don't care what you do. I guess any program is nice, but it's not really necessary.
 
best way to do it maybe is to use something like Brunson's program, and at each run,
1. PLL is displayed
2. The U layer is rotated to simulate a U flick right away, at an adjustable rate. After 1 Uflick you should be able to recognize the PLL, and after 2 for sure you should be able to.
3. All this is time, including execution, timer is running.

Brunson if you make that a timer and have it track times for all PLLs like my app, it could be useful.
 
badmephisto said:
Brunson if you make that a timer and have it track times for all PLLs like my app, it could be useful.
Click to expand...
I really don't care enough about a feature like that to add it. I mentioned to fanwuq in a PM that there would be problems with a Javascript timer starting at the same time the applet displayed since the JS would be under control of the browser and the applet seems to load at its own leisurely pace.

But seriously, a) I hate javascript and b) I don't care. :-) If someone already has a timer I'd be *happy* to donate the PLL and applet code. It's really pretty basic.
 
Still hoping you'd make one for the OLL's. The PLL version helped me a lot learning the PLL's. It is very motivating in my opinion and keeps you going on.
 
krazaeda said:
Still hoping you'd make one for the OLL's. The PLL version helped me a lot learning the PLL's. It is very motivating in my opinion and keeps you going on.
Click to expand...

Google the LL trainer. It scrambles the last layer only. The only drawback is that it gives you 15 seconds of inspection, which is way too much.
 
KevinK said:
krazaeda said:
Still hoping you'd make one for the OLL's. The PLL version helped me a lot learning the PLL's. It is very motivating in my opinion and keeps you going on.
Click to expand...

Google the LL trainer. It scrambles the last layer only. The only drawback is that it gives you 15 seconds of inspection, which is way too much.
Click to expand...

configure->countdown->0, 3, 5, 10, or 15 sec

I recommend zero, and try to avoid looking at the picture. I usually use the task manager to cover up the picture, this gives you a more realistic experience.
 
Ok, so I tried it for a bit and got this:
Corners_Three_Cycle_Clockwise_(A1):_____avg: 3.71, std: 0.65, num: 6
Corners_Three_Cycle_Anti-Clockwise_(A2):avg: 3.42, std: 0.26, num: 13
Parallel_Corners_Swap_(E):______________avg: 0.00, std: 0.00, num: 0
Adjacent_Edges_Swap_(Z):________________avg: 4.20, std: 0.18, num: 5
Opposite_Edges_Swap_(H):________________avg: 4.57, std: 0.06, num: 3
Edges_Three_Cycle_Anti-Clockwise_(U1):__avg: 2.76, std: 0.39, num: 15
Edges_Three_Cycle_Clockwise_(U2):_______avg: 2.85, std: 0.25, num: 14
Push_Push_(J1):_________________________avg: 3.81, std: 0.62, num: 5
Push_Push_Upside_Down_(J2):_____________avg: 3.82, std: 0.64, num: 11
T_perm_(T):_____________________________avg: 3.87, std: 0.63, num: 13
Lucky_7_(R1):__________________________avg: 3.97, std: 0.72, num: 7
Lucky_7_Upside-Down_(R2):______________avg: 4.77, std: 0.00, num: 1
Parallell_Lines_(F):___________________avg: 0.00, std: 0.00, num: 0
Edges+Corners_Three_Cycle_(G1):________avg: 0.00, std: 0.00, num: 0
Edges+Corners_Three_Cycle_(G2):________avg: 0.00, std: 0.00, num: 0
Edges+Corners_Three_Cycle_(G3):________avg: 0.00, std: 0.00, num: 0
Edges+Corners_Three_Cycle_(G4):________avg: 4.15, std: 0.44, num: 5
V_Perm_(V):____________________________avg: 4.35, std: 0.51, num: 17
N_Perm_(N1):___________________________avg: 0.00, std: 0.00, num: 0
N_Perm_(N2):___________________________avg: 0.00, std: 0.00, num: 0
Y_Perm_(Y):____________________________avg: 5.06, std: 0.47, num: 14
Total Average: 2.77

I notice my total average is 2.77, because I took a few PLLs out.
Would it be possible to stop it from counting PLLs with no tries to your average? Also, if we flip the PLLs to an orientation that's easier for us, will it mess up the program at all? (Like rotate 90 degrees)
 
Last edited:
I suck at normal PLLs so I just did OH PLL practice...

Corners_Three_Cycle_Clockwise_(A1):_____avg: 3.82, std: 0.80, num: 4
Corners_Three_Cycle_Anti-Clockwise_(A2):avg: 4.09, std: 0.51, num: 6
Parallel_Corners_Swap_(E):______________avg: 5.26, std: 0.74, num: 3
Adjacent_Edges_Swap_(Z):________________avg: 3.56, std: 0.00, num: 1
Opposite_Edges_Swap_(H):________________avg: 0.00, std: 0.00, num: 0
Edges_Three_Cycle_Anti-Clockwise_(U1):__avg: 2.63, std: 0.42, num: 5
Edges_Three_Cycle_Clockwise_(U2):_______avg: 2.26, std: 0.43, num: 5
Push_Push_(J1):_________________________avg: 4.16, std: 0.67, num: 5
Push_Push_Upside_Down_(J2):_____________avg: 3.05, std: 0.51, num: 12
T_perm_(T):_____________________________avg: 4.47, std: 0.56, num: 10
Lucky_7_(R1):__________________________avg: 4.31, std: 0.12, num: 3
Lucky_7_Upside-Down_(R2):______________avg: 5.35, std: 0.81, num: 11
Parallell_Lines_(F):___________________avg: 5.09, std: 0.35, num: 7
Edges+Corners_Three_Cycle_(G1):________avg: 4.21, std: 0.66, num: 7
Edges+Corners_Three_Cycle_(G2):________avg: 4.43, std: 0.72, num: 6
Edges+Corners_Three_Cycle_(G3):________avg: 4.76, std: 1.14, num: 10
Edges+Corners_Three_Cycle_(G4):________avg: 4.21, std: 0.36, num: 5
V_Perm_(V):____________________________avg: 5.31, std: 0.59, num: 5
N_Perm_(N1):___________________________avg: 0.00, std: 0.00, num: 0
N_Perm_(N2):___________________________avg: 0.00, std: 0.00, num: 0
Y_Perm_(Y):____________________________avg: 5.76, std: 0.92, num: 3
Total Average: 3.84

I never knew Ns were so rare...
 
ohh this thread was resurrected?

Lord Voldemort said:
I notice my total average is 2.77, because I took a few PLLs out.
Would it be possible to stop it from counting PLLs with no tries to your average? Also, if we flip the PLLs to an orientation that's easier for us, will it mess up the program at all? (Like rotate 90 degrees)
Click to expand...

It should not include those that you took out in the average? But then how is the average so low... looks like a bug maybe? Weird!

The code is somewhere on my external hdd, but i dont think i have visual basic installed anymore lol... so i cant really change it hah
 
Badmephisto, would you mind posting the source code so someone else can make an OLL version out of it? A friend of mine is willing to make it, he's into programming a lot.
 
Lord Voldemort said:
Also, if we flip the PLLs to an orientation that's easier for us, will it mess up the program at all? (Like rotate 90 degrees)
Click to expand...

No, just go into the file where all the images are, scroll through and rotate the ones you need. That's what I did, and it worked just fine :)
 
krazaeda said:
Badmephisto, would you mind posting the source code so someone else can make an OLL version out of it? A friend of mine is willing to make it, he's into programming a lot.
Click to expand...

ok i found the source code.
technically to make it an OLL trainer I'd just have to increase number of boxes, and put in more images into that folder.

and yes the calculation for the average was done incorrectly.

IamWEB said:
Nice panda.
Click to expand...
thx :p
 
You must log in or register to reply here.

Similar threads

Averageof12
Specific alg trainer?
Replies
4
Views
1,146
Deleted member 36445
D
Roman
PLL Recognition trainer (bestsiteever)
Replies
0
Views
722
Roman
Roman
melvynp
Algs trainer
Replies
17
Views
6,693
melvynp
melvynp
Vivaldo Roque
Android app to train F2L, OLL, PLL, COLL and WV.
Replies
0
Views
1,740
Vivaldo Roque
Vivaldo Roque
Cuberstache
Megaminx PLL Trainer?
Replies
15
Views
4,567
Alexander
Alexander
Back
Top