Cride5
Premium Member
I've been looking for a 'definitive' source on the metrics people are using to measure move counts for big cube algorithms. Unfortunately I couldn't find anything on the Wiki, and information within threads of this forum was pretty sparse to say the least.
This post by qq here seems to cover the range of possible metrics pretty well:
http://www.speedsolving.com/forum/showthread.php?p=288422#post288422
.. but I'm not sure how standardised this sort of system is.
Just as an initial proposition (based on qq's idea) how does this sound:
* STM - Slice [half] Turn Metric - Same meaning as 3x3, counts half/quarter turns of a single slice (layer) as 1 move.
* SQTM - Slice Quarter Turn Metric - As above, but half turns count as two.
* WTM - Wide [half] Turn Metric - A turn of any number of contiguous layers including exactly one outer layer, by the same angle counts as one move.
* WQTM - Wide Quarter Turn Metric - As above, but half turns count as two.
* BTM - Block [half] Turn Metric - A turn of any number of contiguous layers by the same angle counts as one move.
* BQTM - Block Quarter Turn Metric - As above, but half turns count as two.
* ATM - Axial Turn Metric - Any number of turns on one axis count as one move, for example L r2 = 1 atm.
Another possible metric could exist, something between MTM and ATM. It would be like MTM but relaxing the constraints on the slices being contiguous, but requires that each slice is turned by the same angle. Although it's possible I don't think this sort of metric would be useful. What do others think, would this be useful, and for what sort of applications?
So basically, I'm looking for your opinions on creating some sort of standard for bigcube turn metrics, specifically:
* Do the metrics above make sense?
* Do they cover the range of possible applications?
* Are the names appropriate?
* What should we use as the 'standard' metric from a speedsolving perspective - BTM seems to be preferred, but is it the best at approximating algorithm execution time?
This post by qq here seems to cover the range of possible metrics pretty well:
http://www.speedsolving.com/forum/showthread.php?p=288422#post288422
.. but I'm not sure how standardised this sort of system is.
Just as an initial proposition (based on qq's idea) how does this sound:
* STM - Slice [half] Turn Metric - Same meaning as 3x3, counts half/quarter turns of a single slice (layer) as 1 move.
* SQTM - Slice Quarter Turn Metric - As above, but half turns count as two.
* WTM - Wide [half] Turn Metric - A turn of any number of contiguous layers including exactly one outer layer, by the same angle counts as one move.
* WQTM - Wide Quarter Turn Metric - As above, but half turns count as two.
* BTM - Block [half] Turn Metric - A turn of any number of contiguous layers by the same angle counts as one move.
* BQTM - Block Quarter Turn Metric - As above, but half turns count as two.
* ATM - Axial Turn Metric - Any number of turns on one axis count as one move, for example L r2 = 1 atm.
Another possible metric could exist, something between MTM and ATM. It would be like MTM but relaxing the constraints on the slices being contiguous, but requires that each slice is turned by the same angle. Although it's possible I don't think this sort of metric would be useful. What do others think, would this be useful, and for what sort of applications?
So basically, I'm looking for your opinions on creating some sort of standard for bigcube turn metrics, specifically:
* Do the metrics above make sense?
* Do they cover the range of possible applications?
* Are the names appropriate?
* What should we use as the 'standard' metric from a speedsolving perspective - BTM seems to be preferred, but is it the best at approximating algorithm execution time?
Last edited: