Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opening book policy for multiple engines tournament #742

Open
gahtan-syarif opened this issue Oct 8, 2024 · 5 comments
Open

opening book policy for multiple engines tournament #742

gahtan-syarif opened this issue Oct 8, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@gahtan-syarif
Copy link
Contributor

in a multiple engines tournament, ideally each pair of engines uses the same openings. so engine A vs Engine B and Engine A vs Engine C should get the same opening order. this is currently not the case as the opening book index is currently incremented by rounds

@Disservin
Copy link
Owner

what is cutechess doing in this case?

@gahtan-syarif
Copy link
Contributor Author

what is cutechess doing in this case?

it has multiple different policys for this but i think we just need to implement the default https://github.com/cutechess/cutechess/blob/master/docs/cutechess-cli.6.txt#L197-L201

@gahtan-syarif
Copy link
Contributor Author

I think the easiest way to do this is to make the matchmaking so that all matches between two engines are played first before it moves on to the next pairing

@Disservin
Copy link
Owner

i think you only need to refetch a new opening if the round increases ? https://github.com/Disservin/fastchess/blob/master/app/src/matchmaking/tournament/roundrobin/match_generator.hpp#L57

@gahtan-syarif
Copy link
Contributor Author

Yeah but rn the round increases every two games so say if engine A vs engine B is round 1 then engine A vs engine C is round 2 so the opening for the 2nd pairing would be different from the first

@Disservin Disservin added the enhancement New feature or request label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants