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

I'm curious if noise takes effect in search_best_move #68

Open
shengkelong opened this issue Jun 16, 2023 · 2 comments
Open

I'm curious if noise takes effect in search_best_move #68

shengkelong opened this issue Jun 16, 2023 · 2 comments
Labels
question Further information is requested

Comments

@shengkelong
Copy link

I observed that the policy will be set to noise in "expand_node", but the "update_policy" used during inference (in "process_mini_batch") will directly update the policy to the result of network calculations, so that there will be no randomness at all except selfplay games.

@CGLemon
Copy link
Contributor

CGLemon commented Jun 17, 2023

The noise is not set in expand_node(). It is tentative policy. It will be replaced by NN policy in process_mini_batch(). So you are right. The MCTS process is not random.

@kobanium kobanium added the question Further information is requested label Jun 20, 2023
@kobanium
Copy link
Owner

CGLemon is right. There is little randomness when executing as a normal MCTS player. If you want to add randomness to TamaGo, I modify TamaGo to be able to run like AlphaZero (dirichlet noise and move generation from distribution of the number of visits).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants