PulseGTO

Guides

Console: PulseGTO without the window

PulseGTO_cli.exe runs the desktop app's engine from a command prompt or a script. A command prints its answer and nothing else: the engine's own log goes to a file. It uses the Engine licence on this computer, as the app does.

Start it

  • Start menu → PulseGTO → PulseGTO Console opens it with a pulse> prompt. help lists the commands, help node the options of one.
  • From a command prompt or a script: "%LOCALAPPDATA%\Programs\PulseGTO\app\PulseGTO_cli.exe" node BTN runs one command and exits; -f commands.txt runs a file of commands, one per line.
  • Answers are tables. --json gives one JSON document, --csv CSV, and --out file.csv saves the whole table to a file.

Read a blueprint

pulse> blueprints
pulse> open 2
pulse> node BTN
pulse> node "BTN r2.5 BB c" Kh7d2c
pulse> node "BTN r2.5 BB c x b33" Kh7d2c --hand AQs
pulse> range "BTN r2.5 BB c x" Kh7d2c --seat BB
pulse> ev "BTN r2.5 BB c x" Kh7d2c
pulse> report "BTN r2.5 BB c x" --out flops.csv

A line is written like the action strip. A seat folds everyone who acts before it preflop, so BTN r2.5 BB c means UTG, HJ, CO and SB fold. f, x and c are fold, check and call, r2.5 raises to 2.5 bb, b33 bets 33% of the pot and jam is all-in. The blueprint's nearest size is used, and the console says when it differs from what you wrote. The board goes anywhere in the line: Kh7d2c, or Kh7d2c5s with the turn.

  • node: the actions and their sizes, how often the range takes each one, and every hand class with its frequencies, EV and equity. EV is in bb from the decision, folding = 0. --grid prints a 13×13 chart, --combos one row per combo.
  • range: how much of each hand is in a player's range at the node.
  • ev: every player's EV at the node, heads-up and in three- and four-way pots.
  • report: the decision on every flop, turn card or river card, as in the app's Reports.

Train and continue

PulseGTO_cli train my6max --like 2 --iterations 5m --threads 10
PulseGTO_cli continue 5 --iterations 2m
PulseGTO_cli progress
PulseGTO_cli stop

train takes the game of blueprint N (players, stacks, rake and bet sizes) or of a tree_config.json; --level and --textures set the abstraction as in Preflop Settings. A line shows the iterations, the speed, the time left and the accuracy. Ctrl+C asks whether to stop the run (it saves a checkpoint and a blueprint first), keep watching, or leave it running in the background, where progress and stop find it later.

Note

The console starts its own engine on a free port and closes it when it exits, unless a training is running; that engine closes itself when the training ends. --app uses the engine of the open app instead, so the console and the app share the open blueprint. --verbose shows the engine's log, which is always written to %LOCALAPPDATA%\PulseGTO\logs\console_engine.log.