No, it isn't
Quote:
First question :
I don't understand the difference between these 2 stats in red
One shows strategies for action at this point. The other shows averaged frequencies across all runouts (all turns/rivers following this line).
They could be different on a flop as well. The reason for it is a bit complicated:
There are two ways of calculating frequencies:
1)what a player thinks they are doing
2)what really happens
To illustrate the difference between those two imagine that you have AA/KK in your range and your opponent has only AQ. The board is A7522 and you are calling a bet.
You call with AA and fold with KK, how often do you call?
According to 1) it's 50% because you call half of our combos. According to 2) you are calling only about 14.2% because when your opponent has an ace you get AA way less often (1combo vs 6combos of KK).
This effect is not as strong with bigger ranges but it's still there and it's surely there in your example. We show 1) in big rectangles but 2) in the overall frequencies. This is because we think 1) is more useful immediate information but calculating line frequencies only makes sense as 2).
You can change the settings for that in Tools->Configuration->Data presentation on 13x13 grid->show total strategy as real frequency.
Quote:
Here are the stats for raising :
4.09
4.09
4.09
4.09
4.09
4.09
9.14
9.76
9.77
9.87
9.93
9.07
So the average calculation gives 6.84% : it's different from the 2 red statistics. How could this be?
Simple average isn't very interesting because it doesn't take into account how often a given hand is in range at this point. You should weight them somehow. Two ways that make sense is:
1)use current weights of a hand (for example if you had AA 100% on the flop and called 50%, raises 50% you now have AA:50%).
2)weighting by probability of a hand occurring (similar to 2 in the explanation above), this requires taking into account card removal effect of the opponents range.
On your screenshot it's already clear it's not the beginning of the hand (total gets rounded to 0.0 combos) so your average should include weighting.
In the future please attach the config when asking about details in the solutions. It's easier to have the whole tree solved instead making a lot of assumptions looking at selected screenshot. The way to share the config is:
1)use "copy to clipboard" button in the treebuilding and calculation tab
2)paste the text:
-either to pastebin.com and link here
-here but enclose it in [ code ] [ /code ] tabs (without inside spaces)
Quote:
1. Does it accept PPT range syntax?
It doesn't. We will be accepting he simplified version of PPT syntax (the one Monker Solver uses for example), the one which contains combos and weights only.
In general in PLO translating postflop ranges is hopeless (because there are 200k+ hand combos and too many ways to construct a language). If a tool author wants their format to be importable or to export other formats they really should implement a simplistic format for preflop ranges (16432 combos only) preferably containing 16432 numbers in a given order or (less preferably because it takes more space) combo:weight.
We will be accepting (it's currently in dev) PPT format like that.
Quote:
2. I can't have it installed on two computers at once or I just can't use both installations simultaneously?
We will be extending it to 2 activations anyway (today or tomorrow, all the customers up to now will get that as well of course) so it will be 2 computers at the same time.
Last edited by punter11235; 10-09-2017 at 07:48 AM.