Neon22
Member
I was a dedicated cuber in 1981-83, Based at the University of Auckland in New Zealand.
Now very much older, but young neighbourhood kids, who won't get off my lawn, keep asking questions about rubiks.
Back in my day - we used a system I can't find here. My PB was 12secs but routinely 24 to 28.
If some one can help me identify the system, that would be great as the muscle memory seems long gone
and I'd like to recover the operators.
System was:
- solve the base except one corner closest to my right hand in front of me.
- solve the middle except that same corner, which is now a column
- Use that column as a buffer/workspace to shuffle the top and
- perform ops to get all 4 (top and the column) centers in.
- solve for 4 corners at same time.
Only a few options at the end for swapping corners with rotates in one direction or the other and everything pops out.
Because using the column as a buffer can generally get a top corner stable at same time as getting the middles in.
Constraints on possibilities meant hardly ever got a choke state where had to move/rotate twice as you can see it coming.
Operators were, from memory, shorter because we could afford to muck up entire shifting column while working on edges or corners.
I think only maybe 20 operators in total were needed.
So parts of this look like Petrus but can't find a named method for using the column as a dedicated buffer/workspace.
Any ideas ?
Now very much older, but young neighbourhood kids, who won't get off my lawn, keep asking questions about rubiks.
Back in my day - we used a system I can't find here. My PB was 12secs but routinely 24 to 28.
If some one can help me identify the system, that would be great as the muscle memory seems long gone
and I'd like to recover the operators.System was:
- solve the base except one corner closest to my right hand in front of me.
- solve the middle except that same corner, which is now a column
- Use that column as a buffer/workspace to shuffle the top and
- perform ops to get all 4 (top and the column) centers in.
- solve for 4 corners at same time.
Only a few options at the end for swapping corners with rotates in one direction or the other and everything pops out.
Because using the column as a buffer can generally get a top corner stable at same time as getting the middles in.
Constraints on possibilities meant hardly ever got a choke state where had to move/rotate twice as you can see it coming.
Operators were, from memory, shorter because we could afford to muck up entire shifting column while working on edges or corners.
I think only maybe 20 operators in total were needed.
So parts of this look like Petrus but can't find a named method for using the column as a dedicated buffer/workspace.
Any ideas ?
