search

peter1591 / hearthstone-ai

A Hearthstone AI based on Monte Carlo tree search and neural nets written in modern C++.
301 stars 49 forks source link

move mcts::board::* to engine module #88

Closed peter1591 closed 6 years ago

peter1591 commented 6 years ago

mcts::board::* has some wrap around engine/FlowControl, and contains several helper class to get feedback of the action-parameter callbacks

further, engine/FlowControl/utils also contains some basic helper class from engine's viewpoint

I'm considering to have a new namespace engine under module engine, and outsider of other modules should not use FlowControl anymore

This way, we don't need to modify the flow control unittest largely.

peter1591 commented 6 years ago

several refinements has been done:

  1. refine action parameter getter so MCTS do not need to wrap again
  2. Refine the judger/agent interface

the mcts::board is decided to be untouched, since it now contains only MCTS-related codes