Difference between revisions of "Move count"
From Speedsolving.com Wiki
m |
|||
| (18 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
| − | '''Move count''' is | + | '''Move count''' is the number of [[move]]s that a [[method]] or a [[substep]] uses. The number of moves can be measured according to several different [[metric]]s: |
| + | # Half turns ([[HTM]]), also sometimes called 'face turns' ([[FTM]]) | ||
| + | # Slice turns ([[STM]]) | ||
| + | # Outer block turns ([[OBTM]]) | ||
| + | # Execution movements ([[ETM]]) | ||
| + | # Quarter turns ([[QTM]]) | ||
| + | # Axial turns ([[ATM]]) | ||
| + | # Quarter-Slice turns ([[QSTM]]) | ||
| − | How the steps are solved | + | How the steps are solved or the type of algorithms that are used may affect the move count. For example, using a [[blockbuilding]] approach during early stages of a solve is known to be very move efficient. On the other hand, if a method uses many 2-gen algs it will have a higher move count than if all sides are used. Move count efficiency is important in speedsolving, but it is often necessary to sacrifice move efficiency to improve recognition and execution. However, in fewest moves solving ([[FMC]]) move count efficiency is the sole objective. |
| − | [[Category: | + | == See also == |
| − | + | * [[Fewest Moves]] | |
| + | * [[Metric]] | ||
| + | * [[HTM]] | ||
| + | * [[QTM]] | ||
| + | * [[STM]] | ||
| + | * [[ATM]] | ||
| + | * [[ETM]] | ||
| + | |||
| + | [[Category:Terminology]] | ||
Latest revision as of 02:17, 3 January 2018
Move count is the number of moves that a method or a substep uses. The number of moves can be measured according to several different metrics:
- Half turns (HTM), also sometimes called 'face turns' (FTM)
- Slice turns (STM)
- Outer block turns (OBTM)
- Execution movements (ETM)
- Quarter turns (QTM)
- Axial turns (ATM)
- Quarter-Slice turns (QSTM)
How the steps are solved or the type of algorithms that are used may affect the move count. For example, using a blockbuilding approach during early stages of a solve is known to be very move efficient. On the other hand, if a method uses many 2-gen algs it will have a higher move count than if all sides are used. Move count efficiency is important in speedsolving, but it is often necessary to sacrifice move efficiency to improve recognition and execution. However, in fewest moves solving (FMC) move count efficiency is the sole objective.
