Quote:
Originally Posted by lestro
Do keep avg strategy (street) and EV (street) do the same thing? For mw trees, it is okay to set both to 0?
Would you explain what exactly they mean?
No, they don't do the same thing. It may be okay to set both to zero depending on the circumstances.
EV allows you to see the EV of hands on the specified number of streets. It will not affect the strategy in any way.
Avg strategy is needed for exact frequencies, as the current strategy (which will be shown if no average is available on the street) tends to oscillate around the correct frequency.
An example of this would be the nut/bluff vs bluffcatcher river spot, where the nut/bluff player has a pot bet left. The equilibrium would be to bet 100% nut, and 50% bluff. The bluffcatchers correct frequency would be to call 50%. However, the solver will not reach this equilibrium without averaging, but instead the bluff and bluffcatch frequencies (which are not dominated) will oscillate around 50%.
In practice, it's often enough to know whether a hand is mixed or not. Also, in Omaha, due to the large number of combos, it's less important. It's also less important (and potentially harmful) in multiway games as there are no exact non-exploitable frequencies. In this case, the aim should be to remove dominated actions, which is done without the averaging process.
Both of the settings will impose a RAM and speed overhead, which is why the default settings are 1 street.
Quote:
Originally Posted by lestro
EV disappeared from strategy view (in Solve) with the recent update.
Could you elaborate on this? Possible, it's due to changing the EV (streets) setting.
Quote:
Originally Posted by lestro
Could you add some sort of copy/paste from one subtree onto another? What I mean is, I often run a preflop tree with 2 sizes to compare them and I have to create both postflop scenarios. Since I'm using %s for postflop bets, copy/pasting them would be very useful and would save a lot of time.
I'm reluctang to add this feature as copying subtrees from one spot to another may add unneeded or too few actions to the new tree. The intended way of doing this is to use a custom filter (which can be saved) to populate the postflop spot, and then reuse the filter in the new spot. This allows the actions to adjust to the specific postflop tree.
Quote:
Originally Posted by lestro
When I compress a save, it's barely a dozen KB large. Is it supposed to be this small?
When I load it up, it throws me a NullPointerException in the status bar.
When unchecking "Regret", saves will be very small. I assume this is the reason. However, you will not be able to continue solving the tree efficiently, or view the solution on streets other than the amount of streets specified by "avg streets". This should be explained by the tooltip (especially when changing defualt settings, it's recommended to check for tooltips.)
The bug has been fixed, thanks for the report.
Quote:
Originally Posted by ZenFish
Has Monkersolver been used to compute accurate multiway pre flop ranges for sale by anyone? The BTN/SB/BB equilibrium would be interesting to look at.
Solutions (including 3-way) are available for purchase in MonkerViewer.
Quote:
Originally Posted by Hoopster81
preflop estimates appear to be quite off for larger trees.. the largest ones I am able to get off the ground with 128gb are <90gb
Could you send an email to support with game and settings? We've had some reports of inaccurate estimates, but unfortunately very little feedback on when they occur.
Quote:
Originally Posted by lestro
Just to make sure, to include 5% rake we just put "5.0" in the Settings, not 0.05. Right?
Right.