I'm trying to define a new stat "Folded big blind to blind steal attempt". Read my dilemma here.
Thanks
The Poker Copilot Blog
Tracking the development of Poker Copilot, Mac OS X software for poker analysis and statistics.
Saturday, 24 January 2009
Poker Experts, I need your help again
Subscribe to:
Post Comments (Atom)
Poker Copilot Translation Project
Want to use Poker Copilot in your language? Then help with the Poker Copilot Translation Project.
About This Blog
In May 2008 I started working on Poker Copilot, initially as a product to help me with my own poker playing. Soon I joined a "30-day Challenge", where the participants each aimed to launch a software product in 30 days. As a result of this challenge, Poker Copilot version 1.0 was launched in July 2008.
This blog tracks the ongoing development of Poker Copilot. Who would find this blog interesting? People interested in 1-person software development, in Poker, or in both.
Contact me via email at steve at pokercopilot dot com.
This blog tracks the ongoing development of Poker Copilot. Who would find this blog interesting? People interested in 1-person software development, in Poker, or in both.
Contact me via email at steve at pokercopilot dot com.
Blog Archive
-
►
2012
(96)
-
►
May
(13)
- Lock Poker News
- What do MP, EP, CO mean in the positional stats?
- Adding a new Ongame Network poker room to Poker Co...
- Adding a new Merge Network poker room to Poker Cop...
- PokerStars on iPad and Poker Copilot
- Lock Poker and Poker Copilot
- Phil Gordon's Little Gold Book and Poker Copilot's...
- Poker Copilot 3.10 Now Available
- Crushing the Microstakes and Poker Copilot's HUD
- Early Access Version of the next Poker Copilot Upd...
- How many hands do I need for Poker Copilot's HUD t...
- Coming soon: PFR by position, Aggression by street...
- Comments on this Blog
-
►
April
(18)
- Important information from 2+2 : Two Plus Two Foru...
- Coming in the next update: VPIP by position
- A Nice Email…in French
- Poker Copilot Tip: Move HUD Panels without the Ful...
- Update for Winamax Users
- Poker Copilot 3.08 Now Available
- Poker Copilot Blog: 1000+ blog posts
- Poker Copilot and Zoom Poker: Update
- Poker Copilot 3.07 Now Available
- A poker player uses Poker Copilot to improve
- Coming in the next update: FALSE filters
- Mockup of Potential Poker Copilot Dashboard Concep...
- A Poker Copilot work-around for Merge Network idio...
- Poker Copilot App Updating
- Carbon Poker has its own HUD! (but only on Windows...
- Improving Poker Copilot's App Updating
- Poker Copilot 3.06 Now Available
- False Assumptions
-
►
March
(18)
- How NOT to make money as a software company
- Zoom Poker HUD Early Access Edition
- Changes to the Poker Copilot Hand Formatter
- Coming in the Next Update: Zoom Stats can be separ...
- Poker Copilot and Zoom Poker: played my first sess...
- The Absurdity of Modern Life: Facebook claims trad...
- Poker Copilot and Zoom Poker: Progress Update
- What character is that?
- PokerStars screen names
- Poker Copilot and Zoom Poker
- Poker Copilot 3.05 Now Available
- Ongame and Table Size
- Updated Poker Copilot User Guide
- Coming in the next Update: Unopened PFR Statistic
- Poker Copilot 3.04 Now Available
- Google Analytics Update: Almost a Good Graph
- Poker Copilot Website in Russian
- Downloading Older Poker Copilot Updates
-
►
May
(13)
-
▼
2009
(337)
-
▼
January
(31)
- Sentence of the Day
- Mockups of HUD Layout Customizer
- Poker Copilot Video Demo
- Poker Copilot for Mac OS X...and Windows?
- New Advanced Stats: Early Access Version
- Poker Experts, I need your help again
- Ronald writes: "My poker tracking software, Poker...
- Poker Copilot is "Sitelinked"
- Sentence of the Day
- Which Countries Buy Poker Copilot?
- An Interview about Poker Copilot
- Making sense of my Google traffic
- How do paying customers hear of Poker Copilot?
- Quick Poker Copilot Update
- Poker Copilot 1.55 Released
- Joda: the answer to all Java date questions
- Poker Copilot Review in French
- Poker Copilot: What's Hot, What's Not
- Changes to 3-bet Statistics
- Optimising Customer Support
- Poker Copilot 1.54 Released
- It Makes Me Happy...
- Help Me, Poker Experts!
- Oops...Poker Copilot Working Again
- Feel-Good Comment of the Day
- Don't Take it Personally
- Poker Copilot Review
- Today's Second Updated Poker Copilot Version
- Free Poker Copilot Licenses for Bloggers
- Poker Copilot 1.49 Released
- Poker Copilot: The (Half-)Year in Review
-
▼
January
(31)


4 comments:
Stole this from the wpt site:
Attempt to Steal Percentage:
A hand counts if a player open raises preflop from a position one to the right of the button, on the button, or in the small blind. Denominator is opportunities to steal.
Folded Big Blind to Steal:
A hand counts if the player is in the Big Blind and a player from a steal position (one to the right of the button, on the button, or the small blind) open raises and the player gives up his blind and folds his hand. Denominator is steals attempted against his big blind.
Folded Small Blind to Steal:
A hand counts if the player is in the Small Blind and a player from a steal position (one to the right of the button or on the button) open raises and the player gives up his blind and folds his hand. Denominator is steals attempted against his small blind.
Raise Big Blind Against a Steal:
Similar to “Fold Big Blind to Steal” except instead of folding his hand, the player responds by re-raising from the big blind
Raise Small Blind Against a Steal:
Similar to “Fold Small Blind to Steal” except instead of folding his hand, the player responds by re-raising from the small blind
Personally I think it should include 1 raiser from late position or smal blind when folded to him and small blind should fold his hand.
I would limit it to one-on-one scenarios, the open raiser (button or SB) and the BB. If the SB calls a raise or re-raises, then the BB has a lot more variables to consider. It becomes questionable as to whether this is a simple steal attempt.
Most importantly I think you should calculate this the same way HEM and PT3 calculate it unless you feel there is a significantly better way to do it.
Personally, you use this stat when deciding whether to raise someone's blind. If I'm considering raising their blind, I don't care if they'll fold if the sb 3-bets, and if I want to know if they will raise when the sb calls, I would look at their squeeze frequency. So I think it should only count when there was one raiser, and it was folded to the bb.
As I see this, I could only consider a blind steal attempt as being from the cutoff, button, or small blind as long as no one has entered the pot prior to the action by that position. This of course is only a stat for the big blind position.
The unfortunate part I see is adding the cutoff position. This can skew the stats unfavorably leading a user to believe that they are not defending blinds enough, leading to looser calls from the blinds. Leaving out the cutoff position from the stats would probably be a wise first step in implementing this. If/when future stats on players would include raise by position information, then evaluating a players tendencies would become more accurate.
Of course, changing the attempt to steal blinds stat to reflect any differences of position should also be checked in the resulting release so that statistics remain consistent.
Post a Comment