Bkushigian/issue14 Serialize Tree/Card Configurations

[bkushigian]

Saving/loading tree/card configurations should be easy. The following data needs to be present when running a solve:

• CardConfig: contains
  • ranges (OOP and IP)
  • flop cards
  • turn card
  • river card
• TreeConfig: used to build an ActionTree, this contains:
  • initial_state: BoardState
  • starting_pot
  • effective_stack
  • rake info
  • flop_bet_sizes
  • turn_bet_sizes
  • river_bet_sizes
  • turn_donk_sizes
  • river_bet_sizes
  • add_allin_threshold
  • force_allin_threshold
  • merging_threshold

A couple things to think about:

1. Data Duplication: card_config's flop/turn/river determine tree_config's initial_state value, and this might be annoying for a user to fill out/can lead to buggy configurations.
2. Sometimes, as in the case of a batch solve where we run over many different boards, the flop/turn/river cards aren't known in the configuration.

• Pio handles this by just specifying dummy cards and then having the batch solve module accept a set of flops separately.

For now, having an easy way to load/save configs and use to solve sets of flops will be very useful

[bkushigian]

jfc github will NOT stop sending PRs to this repo. This has been a bug in github for years. Closing