So first I am sorry for all the delays. I am travelling this weekend and have access to very spotty internet. This means the delays are bigger than usual and I am not able to run any serious analysis - just answer simple questions. With that disclaimer let me answer some of the things mentioned in recent posts:
Quote:
The problem is went I browse the tree. PioViewer don't like the 1/3 size cbet, which is very hard to believe on a dry 224r flop. He like a combination of 2/3 of the pot cbet (about 40% of the time), 1/2 pot cbet (20% of the time), and 40% of the time check-back, with less then 1% 1/3 of the pot cbet (some K high backdoor fd).
Please refer to some recent posts about posting the config. The description - no matter how careful you are when writing it - will never be enough to replicate the tree. The way to share trees is to provide the full tree config which can then be pasted into PioViewer by going to Tools->paste treebuilding config. This allows for exact replication of the tree, solving it locally and looking at the results.
That being said, the why question is always the hardest one and we are not really better equipped to answer it than poker coaches and experienced players. Our job is to make the solver correct and to allow for displaying various kind of information to make analysis easier. Looking for the answer to the why question is hard and it's a job of poker coaches/players/theoreticians. Sometimes it's just too hard and some underlying pattern is still waiting to be discovered.
Quote:
i tried to create a small script, was already watching the small Youtube intro regarding those scripts.
I think i created one but when i click on ->Script->Run this script
a window pops up like in the youtube vid, but nothing happens.
Basic version doesn't support scripts which is one of its few limitations compared to the pro one.
Quote:
Hey...there is nothing explained how to share a config.
already got it and will share.
Yes, I am sorry for the wrong link.
Quote:
Think I already got the answer, that the OOP range just does not change that much even if IP does not value bet that wide which still amazes me.
Well, there are a lot of things out of those the solver shows which are hard to believe at first. That's the value of the tool: it shows you what is optimal even if it's so counterintuitive no human would come up with that. The problem is the solver doesn't have the concept of "why". I understand people always want explanations - sadly we just don't have them. We can only guarantee the results are correct.
Yes, you didn't fill in turn/river bet sizes. The results with forced check-down on turn/river are going to be way off from really is optimal. It's a good idea to follow the quick start video example and look at sample tree configs provided with the solver.
Quote:
I'd like to know if there is any easy way to force IP or OOP to do a certain action on specific next unknown cards.
It was our design decision to make the betting lines the same regardless of what turn/river cards are. It has so many advantages when it comes to possible features (aggregation along the same line, overall EVs, switching between trees with the same structure, jumping from line to line changing turn/river cards, optimizations when it comes to implementation etc.) that it is worth sacrificing not being able to use different lines on different cards (you can always provide more bet sizes if you really need it).
Quote:
So far I've been manually selecting every turn heart card (3h,4h,6h, etc.. to Ah), then using Lock Node and forcing IP to bet all their hands on the card.
There is not an easier way to do it right now.
Quote:
When I load that tree I'd like it's configuration to automatically go into the Tree Building tab
For that you need a .txt config file which is created along with the save. Make sure to move them along with .cfr files if you change folders etc.
Quote:
Yes, you do! You may only want to browse the flop action but you must specify a complete game tree including turn and river otherwise the flop can't be sensibly solved.
Thanks for answering in comprehensive and clear way, I wouldn't have explained it in a better way
Quote:
ERROR: build_tree not enough memory; needed: 16847 MB; availble 5842 MB.
Again, post the config. In general 16GB postflop tree is so huge it's almost a sure thing you made a mistake or provided like 3 or 4 betsizes everywhere. Postflop trees with one bet size are smaller than 2GB these days and even if you use more sizes you should comfortably be below 5GB if you don't go wild with all the options.