Quote:
Originally Posted by scylla
Ah, I see what you mean. When using a subset, the buttons that allow you to add more trees are disabled. I would strongly recommend not adding trees to your subsets. The subsets are designed to reflect the total 1755 possible flops as closely as possible. Adding more trees to them will not make them more accurate; they will become (much) less accurate. This is because suddenly there's disproportionally more/less 2flush/paired/etc board, or A,K,Q,etc hands. Adding more trees simply throws off the entire balance. Adding more trees will only improve databases that were built with the "Add X random flops" feature.
So when we solve for a subset, it solves for that subset as a whole? If I add another flop it would have to recalculate all flops to re-balance the strategy? Is that correct?
How can I do a hand review then if the flop isnt present? For example..
Hero opens bu, bb flats hu to flop
Ah9h3c is flop in game
The subset has AT5r,A86 two tone
You see how the texture is different?
I dont know if A93 twotone was the exact flop, but it was something very similar. I was trying to see how a certain hand was played and ended up using flop strength ( ie. A pair below TP but above mid pair) and guessing or estimating I guess would be a better word on how/if I played a hand correctly.
That's why I wanted to add in a flop texture that I seem to find tricky.
*edit*
As of now, I solve those spots individually when I do session reviews but wanted to addin some of the more common spots to my db.
Should I continue solving each of those individually if the texture isnt represented well in the subset?
Or
Should I use the estimation process I mentioned above using the subset ?
Or
Both lol
Or something completely different?
Sent from my SM-G975U using Tapatalk