Quote:
I am using PioSolver 2 on an old computer using the CustomBuild "oldCPU". I have an issue node locking pre-flop trees. I'll stop a tree at .35 bb/100 then I lock the OOP player's decisions vs a complete or a raise. Then I restart the simulation and stop it again at say 1 bb/100. What I've found is that my In Position player never changes his strategy even though a different strategy clearly has a higher EV. I've confirmed before starting the sims that the In Position player's decisions are not locked.
It would be useful if you could send me the tree config (support@piosolver.com) with a descriptino of what you are locking so I can re-run locally.
Maybe it's a good idea to do it this way:
1)Build a new tree
2)Lock
3)Solve
as well.
Quote:
Is it possible to solve for 6-max LHE ranges?
It isn't. It's a solver for HU spots.
Quote:
I would have thought it was the opposite because only one betsize. Is it just because the postflop ranges are wider?
It's because in no-limit you don't get 4 possible bets on all streets (because you are all-in quite quickly) so overall the number of lines is smaller unless you use a lot of bet sizes.
Quote:
I have two preflop trees. One with a 4x 3bet size. The other with a 5x 3bet size. I am wondering how I check the EV difference. Do I look here and compare OOP's EVs:
Yes, the only mathematically correct way is to compare EV in the root node (not at any other part of the tree).
Comparing in any other node is meaningless because the ranges that go there might be completely different.
Quote:
Hi, how can i modify a range (weight of all hands) in a node?
I understand node-locking is for changing frequencies only...
I cant find the command in UPI doc.
thanks
This is not possible.
The reason is that it would require creativity from the solver when it comes to ensuring enough combos even go to a node you lock strategies at. This is a judgement call and would produce unexpected consequences ("I only wanted to have AA:0.9, why it stopped cbetting flop with AA?").
This is why strategy locking is the only sensible option.