Record "2" moves (eg. L2) as one Turn #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Need to decide if I should do this.
Cube notation generally counts L2 as one 'move'.
However, it still needs to move the face the same amount.
On the other hand though, moving one face 180º is quicker for the robot than moving two different faces 90º unless they are opposite. So in terms of prioritising how quick it is, it would sort of be in between one move and two moves. I actually think there should be a method which converts the turn history into a speed rating for the robot which would rate 180º better than 2x 90º but not as good as 1x 90º or 2x 90º where the faces are opposite. This score can then be used to get the most efficient solve for the robot.