Quote:
Originally Posted by Rezzir
Thank you for your quick reply. Option 2 seems very handy.
However, what is the significance of the last app 'winning'?
Also, on a different note. I have entered 10 10 vs a hand range. However, as I am entering the range it doesn't allow for two of the 10s already being gone? Can you please help me?
Of course I can help.
Re. "winning" I mean the last app instance you close will have its app state (the scenario, all quick-saved hand ranges, etc.) saved out to the filesystem last, so this app state will overwrite the first app instance's app state which got saved out earlier.
Re. the 1010 vs. range example -
Yes this program takes card removal effects into account, and also range removal effects. It has to in order to calculate correct equity/stats results.
Let's get specific: TsTh vs. {TT+}. In the hand range view, at the top right you can see the number of combos in the range: 30/1326. By default this doesn't include card removal effects because by default people want to see the "neutral" number of combos in the range. E.g. if you're devising a range strategy "I want to open 35% of hands on the button", then to start out you may not want card removal effects to get in the way of the number of combos.
There are two checkboxes under the 4x4 suits grid:
* View Card Removal Effect
* View Hand Combo Counts
Turn these on, and you will then see card removal effect being taken into account i.e. 25/1225 combos. Also in the range grid, each cell's combo count is written in the cell so TT's combo count is now 1 instead of the neutral 6.
This is just card removal effect. At run-time (calc-time), the program also takes into account range removal effects which can get way more complicated. E.g. if you have multiple ranges up against each other where the ranges intersect in complicated ways. You will then probably wind up having non-integer (fractional) combo weights on cells and it's out of scope to show this statically. So the program only shows card removal effect visually (pre-calc time) and saves the effects of range removal only for the calc's end results.
Another way to look at combo counts: after calculating, look at the range's breakdown -> heat map, click ViewDetails, and you will see a text output with each cell's combo count listed. You can also see this in the distribution graph's details text.