Quote:
Would a player following a strategy that is very hard to be exploited, against actual real-life opponents be crushing over a big sample of hands?
Probably
Quote:
Do these high-stakes professionals use Pio to ONLY understand what the equilibrium is? Or are they able to use it to discover exploitative strategies too?
The best to ask them. A lot of people use node-locking although I do feel it's overrated as adjustments are usually pretty obvious once you understand where the equilibrium is and in which direction the opponent is deviating. It never hurts to see some examples though so it's beneficial to at least look at some solutions with node-locking to confirm your intuition.
Quote:
Had a question about node locking. For example on AQ7r in 3b pot BTN vs UTG I node locked OOP player to have no raises which made us cbet 100% instead of x 95%+.
This makes sense but when I arrive to the turn in these types of spots the sim starts to x 100% or a very high frequency since we made their range stronger by having no raises.
Before I answer this it seems something doesn't check out. You wrote you lock UTG to have no raises so I presume you have chose some check-calling and some check-folding range. Then you say IP cbets 100% instead of checking most of the time which doesn't seem to be very realistic unless IPs range is very weak. Then you show a screenshot of OOP decision (not IP) which checks all 95%+ of hands but you say you start checking and not them.
It looks to me like you confused players on the turn so please to re-read it and let me know what the problem is.
Quote:
Now, let's say OOP player adjusts to IP balanced calling range and only check-raises a tight solid value range.
Now IP player will lose a tonn of $ calling a balanced range vs the check raises.
But given that this is not the optimal strategy Pio calculated for OOP player, does this mean that OOP player makes more EV by check raising a balanced range than only check raising a value range?
It's not like IP loses tons of $ calling a balanced range. They just lose opportunity to make more (or lose less) money by not adjusting. You can look at EVs of hands for OOP before their decision. Usually it will be pretty close between calling and raising. You can see exactly how much OOP is losing by not raising certain weaker hands - this will be a small amount but it will open them to a huge possible exploit (if IP just starts folding everything after being raised).
I understand that you feel EV disappears somewhere and you are wondering where. The answer is it disappears in calling branch. Now the range of OOP is much weaker for a call and IP makes "tons" of money vs that range in a call branch which is a bit bigger "ton" than what they now lose in raise branch.
Quote:
It might sound like a dumb question but I hope your answer regarding my example will help me understand how the GTO mecanisms work.
It's not dumb. Once you realize that now IP makes more in the call branch it makes more sense intuitively. During solving process both players know which action with every hand has the higher EV and they adjust in that direction. Equilibrium is a state where no player can make a profitable adjustment yet. Focus on this:
"No player can make a profitable adjustment"
This means in particular that moving weak hands from a raise to a call branch does not result in higher overall EV. The math behind it solving makes sure of that.
Quote:
2/ is it possible to run a script on multiple flops with node locking?
For example, I might set that OOP player only check raises a value range I would determine.
It's not possible right now and it's unlikely in the near future. Unfortunately this kind of functionality would require a whole new language to describe ranges so you can describe "value range" in a way independent of the flop. We have a framework for that but it's a long way till it's available in the solver.
Quote:
What line do I add to this portion of the script to cause it to node lock OOP's flop bet frequency at 100%? Do I need to add a line for each flop?
Every time you want to node-lock something at 100% must better way is to just built a tree with only this action possible. You can do that by using add/remove line feature in the treebuilding config described here:
https://www.youtube.com/watch?v=zLGpcZavxeQ (point 1, see the video description)