w34z3l's Free Database / Stat Analysis Thread
•Edited 1 year ago
If the thread is not clear, you can post your stats for analysis here. Seeing as it may not always be super obvious what exactly needs posting for a basic stat review, here is a rough guide. You can post here as often as you like and it is completely free.
Forum Rule - You must have 10 good posts or be a valued PokerVIP member to receive this free analysis.
1. Have a Sample
I don't mind looking at small samples, but when it gets to below about 20k you are probably wasting everyone's time and not getting a lot of benefit in return. See if you can have at least 20k hands. If you can have 50k or 100k even better. The sweet spot is usually somewhere between 50k and 150k. (Sample sizes more than this often contain conflicting data where our play style has change, but not always. Assuming no big changes in game plan, the more hands the merrier!)
2. Post stats by position.
Both HM2 and PT4 have the option to view stats broken down by position.Please make sure you include this in your screenshot. It's possible for an overall stat to look fine, yet serious problems are identified when analysed positionally.
3. Feel free to include results graph showing both the red and blue line.
This is not 100% necessary. Actually, what we are saying is that there is basically no point in posting your graph unless the red and blue lines (showdown and non-showdown winnings) are included. If you do post a graph, put it in big-blinds ideally, but feel free to include $ alongside it if you prefer.
Ok, now for the stats we need for some solid basic analysis.
Fold-to-3bet (for PT4 make sure this is "fold to 3bet after raise)
cold-call (for PT4 make sure this is "call PF 2bet" not cold-call
Fold to cbet on flop/turn/river (Include for 3bet pots if you think it's a problem)
Cbet on flop/turn/river (Include for 3bet pots if you think it's a problem)
Raise vs Flop Cbet
4bet range (not frequency)
Fold to 4bet
River call efficiency
The following is not mandatory, but for more advanced analysis you can include.
Bet vs missed cbet on the flop (In PT4 this is called "float flop")
Bet vs missed cbet on the turn (In PT4 this is called "float turn")
Bet vs missed cbet on the river (In PT4 this is called "float river")
Bet vs missed cbet OOP on turn (In PT4 this is called "probe turn")
Bet vs missed cbet OOP on river (In PT4 this is called "probe river")
Delayed Cbet IP
Delayed Cbet OOP
Fold to Delayed Cbet IP
Fold to Delayed CBet OOP
Skip flop/turn/river cbet and check/fold (In PT4 "fold vs flop/turn/river float")
Skip flop/turn/river cbet and check/raise (In PT4 " raise vs flop/turn/river float")
Skip flop/turn/river cbet and check/call (In PT4 "raise vs flop/turn/river float")
Ok, so we are not saying this is everything we need for a complete DB analysis. It's obviously way more complex, and once problems are found we need to run filters and understand those problems in more depth. Anyway this should be a good starting point.
Feel free to disregard any of the above information. It doesn't bother me that much, it's you that will miss out