Quote:
Originally Posted by dfan
Obviously this is a matter of preference for users. I guess you could poll users here if you wanted. Personally I would prefer a "Clear Range" btn on the HandRange screen without the verify process. If there is room to put it up top, accidental clicks would be rare I think. But this issue is obv minor.
Another issue isn't so minor though. Could you change the way you calculate your flop texture made hand stats to correspond to the way flopzilla and other flop analysis sw does? Your current approach of counting board pairs when calc prob of hitting a pair or two pair is quite misleading. For example, your stats for hitting two pair with 75o is ~ 4.0%. But obv we really want to know prob of 2 pair using both hc's (2.02%) giving us a very strong hand and not merge that with hitting 1 card on a paired board which is a very weak hand. Similarly misleading to have unpaired cards hitting a pair on the flop 40% of the time (I wish!). A flop of KQQ isn't really that hot of a flop for 75o.
Same for straights and fh's on the board - technically they should be removed from flop hits, but these happen so rarely its almost irrelevant. And when calc to turn if you miss the board completely but there are 4 of a suit or 4 to a straight on board this shouldn't be calc as a flush/straight draw.
Flopzilla has the best flop analysis layout I've seen as well as a fairly user-friendly interface. I imagine you've checked it out already, but if not it really does have some of the nicest implementations I've seen for flop analyses.
Just want to say I'm impressed with your dedication to improving your software and the speed with which you incorporate your users suggestions. Good business model -wish more of the business world took this approach!
Agree, let's skip/postpone the minor ClearRange button issue and get to the meaty stuff : ) ..
I completely agree that settings like "must use both hole cards", "must use at least 1 hole card", etc. would improve the flop analysis stats. It's on the todo list but I haven't gotten there. A few people have suggested this, the last I remember was customer M.S. (whom I also talked with in person in Vegas later on this issue and other heat map analysis features).
For now, the app has stats that approximate "must use both hole cards" that some customers may not have noticed yet. E.g. if you enter AKo and set DealTo=Flop, the OnePair stat is 40% as you say (includes the cases where the board pairs), but if you tap the "->" S button in the stats view you'll see stat "HitBoard'sTopCard" which shows 32% (tap it once more to see the stats for combination draws). This stat measures the hole cards' "pure" hit %age and doesn't include the cases where only the board pairs. Similarly below this stat is PocketPairAndNoOvercard.
What I'm saying is I should implement a "must use both hole cards" setting as you suggest for generality across all stats not just TopPair, but currently there are some minimal stats to help give you a picture of a "pure" hit.
Yup I've seen the excellent tool FlopZilla and hope PokerCruncher's flop stats can match that tool's someday. But FlopZilla is a special purpose tool with a specific focus, which may be one reason why it does what it does so well (along with, it has desktop real estate to work with). PokerCruncher may be trying to be too much of a jack of all trades - 10 player fully general hand range equity calc, flop texture analysis and stats, DealTo=xxx, heat maps, etc., on a small screen, with a wimpy processor, at a fraction of the price!
But being a general jack of all trades tool does have advantages - e.g. FlopZilla requires 3 specific flop cards to be entered, but in PokerCruncher you can enter just 1 flop card or leave the flop all blank (random), set DealTo=Flop, and see what made hands and draws a given hand range or hole cards can flop and how often.
Again I have a 100% positive opinion of FlopZilla and didn't mean to get into comparisons, but it came up.. In the end the comparisons will improve PokerCruncher (e.g. after I implement "must use both hole cards") so I'm happy. Thank you dfan for writing and bringing up these issues. It's customers like you who make things happen (and there are many on this thread). Best, -RJ
(and stay tuned for an app update early next year)