You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
Presently, moves are sorted in the search function with sort_by_cached_key(). This was fine initially, but will be a source of slowdowns in the future.
Because of how branches are pruned in the a/b search, we are not necessarily searching all available moves. We are likely (and ideally) only searching a small fraction. So, if we are not searching all moves, why are we sorting all of them?
Rustic has a good page about this in it's book. You can use a modified version of selection sort to do this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Presently, moves are sorted in the search function with
sort_by_cached_key()
. This was fine initially, but will be a source of slowdowns in the future.Because of how branches are pruned in the a/b search, we are not necessarily searching all available moves. We are likely (and ideally) only searching a small fraction. So, if we are not searching all moves, why are we sorting all of them?
Rustic has a good page about this in it's book. You can use a modified version of selection sort to do this.
The text was updated successfully, but these errors were encountered: