PulseGTO
Blueprints & databases
Recalculating individual nodes
A blueprint is the starting point. Its postflop strategies are replaced or supplemented, spot by spot, by re-solves without hand abstraction. You can save a re-solved node into the blueprint as an override. The .pgb then holds both the trained strategy and the re-solved one for that node and board.
Three things to keep apart
| What it is | Accuracy | |
|---|---|---|
| Blueprint | The trained strategy, preflop and postflop, consistent across the whole game | Postflop limited by the hand abstraction |
| RangeCFR re-solve | A new computation of one postflop spot, per combo, starting from the blueprint's ranges at that spot | No hand abstraction. Heads-up covers every turn and river; three-way does too by default when RAM permits. The reported convergence applies to the configured betting tree. |
| Updated database | The blueprint plus all saved re-solves | Re-solve accuracy where a spot was re-solved, blueprint accuracy everywhere else |
You set the iteration, time or accuracy stopping condition; a short example run is not an iteration limit. On a three-way flop, optional quick preview or insufficient RAM can reduce turn coverage, and the app shows which turns were solved.
How the database improves
- Cloud: PulseGTO re-solves spots on its own servers and updates the published database that Cloud users browse. Coverage grows over time; not every spot has been re-solved.
- Engine: you do the same for your own files. Use Recalculate Node and Save for single spots, or the night batch for many heads-up flop spots in a row.
Local files are not synchronised with the Cloud database in either direction.
How to tell where a strategy comes from
- Green Re-solved badge: this node shows a saved re-solve. Click it to switch to the file strategy; it then reads Re-solved · off.
- No badge: the node shows the blueprint strategy.
- Accuracy: the override keeps the exploitability measured by its re-solve, shown in the badge's description.
- Blueprint toggle: ON shows the blueprint (or its saved override), OFF shows the local re-solve of this node, if one has run.
Saving and the night batch
- Save stores the node on screen for that board, not the whole subtree below it. Heads-up and three-way re-solves use the same format.
- The night batch re-solves heads-up flop spots, most frequently reached first. Each is saved with its accuracy only if it meets the accuracy limit you set. A spot whose tree does not fit in RAM, or does not reach the limit in its time, is skipped and tried again on the next run.
- In the night batch you can turn on Show class representatives for unsolved flops (≈). A flop without its own re-solve then shows the re-solve of a similar flop from the same texture class, and the badge reads Re-solved ≈. That flop itself has not been re-solved.
Overrides are written into the .pgb. Keep a copy of the blueprint before you save experimental re-solves.
To start a re-solve, see Recalculating a node.