-
Notifications
You must be signed in to change notification settings - Fork 46
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
to be checked: Leak in rdeep? #15
Comments
I made an implementation which I think gets a more or less correct player 2 perspective, see 40cb802 in https://github.com/intelligent-systems-course/schnapsen/tree/rdeeppessimist
|
It became clear that the |
It seems that in any case, getting the work done in rdeeppessimist would be beneficial. |
The rdeep bot is making a call to make_assumption, which in turn makes a call to make_assumption on the Deck.
Then, in the deck, a new Deck is created, but that gets initialized with the perspective of player 2.
Finally, rdeep uses this assumption to do random rollouts of the game
I am under the impression that this means that information which player 1 does not have access to is leaking. This information could then potentially be used in the roll-outs, leading to the prediction from the roll-outs to be better as it normally should be.
Note, it might also be that because rdeep, in its current implementation, is using random roll-outs of the game, it does not matter that it sees the perspective of palyer 2. It does not use the information anyway,
The text was updated successfully, but these errors were encountered: