Ah crap. Full Tilt has introduced a new feature called "Run It Twice". "Run It Twice" hands seriously screws things up for Poker Copilot.
There's a sample hand history below in which I've changed the names to protect the innocent. One game number, one flop, two turns, two turns, two rivers, two pots. This doesn't fit into Poker Copilot's database, model or user interface.
I'm not sure what to do about this. Any smart readers got a nifty suggestion?
Full Tilt Poker Game #1111111: Table ZZZZZZ (heads up) - $5/$10 - No Limit Hold'em - 11:11:11 ET - 2009/11/11
Seat 1: XXXXXX ($1,029.50)
Seat 2: YYYYYY ($1,273.50)
YYYYYY posts the small blind of $5
XXXXXX posts the big blind of $10
The button is in seat #2
*** HOLE CARDS ***
Dealt to XXXXXX [3d Ad]
YYYYYY raises to $30
XXXXXX calls $20
*** FLOP *** [4c Qd 6d]
XXXXXX checks
YYYYYY bets $50
XXXXXX raises to $150
YYYYYY has 15 seconds left to act
YYYYYY has requested TIME
YYYYYY raises to $390
XXXXXX raises to $999.50, and is all in
YYYYYY calls $609.50
Players agree to Run It Twice
XXXXXX shows [3d Ad]
YYYYYY shows [Qh Th]
*** TURN 1 *** [4c Qd 6d] [8h]
*** RIVER 1 *** [4c Qd 6d 8h] [4h]
*** TURN 2 *** [4c Qd 6d] [As]
*** RIVER 2 *** [4c Qd 6d As] [Kh]
*** SHOW DOWN 1 ***
XXXXXX shows a pair of Fours
YYYYYY shows two pair, Queens and Fours
*** SHOW DOWN 2 ***
XXXXXX shows a pair of Aces
YYYYYY shows a pair of Queens
YYYYYY wins pot 1 ($1,029) with two pair, Queens and Fours
XXXXXX wins pot 2 ($1,029) with a pair of Aces
*** SUMMARY ***
Total pot $2,059 | Rake $1
*** SUMMARY 1 ***
Pot 1 $1,029
Board: [4c Qd 6d 8h 4h]
Seat 1: XXXXXX (big blind) showed [3d Ad] and lost with a pair of Fours
Seat 2: YYYYYY (small blind) showed [Qh Th] and won ($1,029) with two pair, Queens and Fours
*** SUMMARY 2 ***
Pot 2 $1,029
Board: [4c Qd 6d As Kh]
Seat 1: XXXXXX (big blind) showed [3d Ad] and won ($1,029) with a pair of Aces
Seat 2: YYYYYY (small blind) showed [Qh Th] and lost with a pair of Queens
The Poker Copilot Blog
Tracking the development of Poker Copilot, Mac OS X software for poker analysis and statistics.
Thursday, 19 November 2009
Full Tilt's New "Run It Twice" Gimmick
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
(31)
-
►
January
(29)
- Coming in the Next Update: Ignore Old Hand History...
- Coming in the Next Update: Poker Copilot can forma...
- From the "It's About Time, Too" Department
- Poker Copilot Business Cards
- Playing on Entraction Network?
- Unofficial Update for Ongame Players
- One Person with Two Accounts Playing on Ongame?
- Small Tweaks in Poker Copilot Preferences
- Ongame Network and Poker Copilot
- Buy Poker Copilot via Bank Transfer
- Improvement to Appearance of HUD Popup
- Improvement for Poker Copilot Translators
- Coming in the Next Update: HUD Layout has an extra...
- Unofficial Poker Copilot Update for Ongame Network...
- Poker Copilot Demo Video in French
- Reason I Like My Mac #17,823
- Updated Poker Copilot Demo Video
- Poker Copilot 3 Coming...
- News for Poker Copilot Translators
- Updated Poker Copilot Translations
- New Poker Copilot Screenshots Reveal How Version 2...
- Poker Copilot Translation Project: Update
- PokerStars now has built-in Auto-Hotkeys
- Reflection on the PokerStars Update that Broke Pok...
- Poker Copilot 2.101 Now Available
- Poker Copilot Website in French
- Spanish Website Translation
- Poker Copilot Website in Spanish
- Update for PokerStars Denmark Users (PokerStarsDK)...
-
►
January
(29)
-
►
2011
(154)
-
►
December
(10)
- New Unofficial Update
- Poker Copilot Discussion Forum in French
- Coming in the next update: multiple HUD layouts
- Poker Copilot Fact of the Day
- Unofficial Poker Copilot Update for the Brave
- Coming in the next update: All-in Equity in $ or B...
- Who uses BarrierePoker.fr?
- Coming in the next update: Filter tournaments by t...
- Help Wanted: BlazingStars or AHK for Merge Network...
- Coming in the next update: choose a language for P...
-
►
November
(13)
- MacKeeper's "Real-time protection" breaks Poker Co...
- PokerStars Playing History Audit CSV Problems with...
- Poker Copilot 2.99 Now Available
- HUD not working on PokerStars in update 2.98?
- PartyPoker support in Poker Copilot
- End of a Troublesome Week
- Poker Copilot 2.97 Problem Fixed?
- Desperately Seeking Help to Solve the Crashing Pro...
- Is Poker Copilot 2.97 Crashing For You?
-
►
December
(10)
-
▼
2009
(337)
-
▼
November
(44)
- ServerPronto: The Hotel California of Server Hosti...
- The Ongame Network Problem
- Bob Walsh's Top 5 Tips for Improving Your Software...
- Show Mucked Hands Only on Showdown?
- Finding Leaks with Colour and Bars
- The Tao of Programming
- Preview of Poker Copilot 2.20
- PowerPC Issue Resolved
- Mac: It Just Works...Except When It Doesn't
- Queues, the Software Panacea
- You know someone likes your software when...
- Java Then And Now
- Sentence(s) of the Day
- Nifty iPhone Poker App
- I was interviewed for a podcast...
- 30 Day Trial AND Money Back Guarantee
- Full Tilt's New "Run It Twice" Gimmick
- How to Be Rich
- Problems with PowerPC Macs and Poker Copilot 2.19
- What hands does a player take to showdown?
- Documentation Week
- Preview of Poker Copilot 2.19 Ready to Download
- "Sticky Columns" in Next Poker Copilot Update
- "In the Money" in Next Poker Copilot Update
- UltimateBet Tournament Summaries?
- When to Make a Blind Steal Attempt
- How are Table Statistics Calculated in Poker Copil...
- Fluid: Turning Websites into Desktop Apps
- Top Ten Blog Posts
- Deadly Drugs
- Preview of Poker Copilot Update
- Poker Copilot Sales Breakdown
- Japanese Launch of Windows 7
- What I Really Hate...
- UltimateBet Support Coming to Poker Copilot
- Rococoa - Bringing Cocoa to Java
- Oh to Have His Problems
- Community Cards
- Table Stats
- Customers Over Competitors Recanted?
- Customers Over Competitors
- Improved Memory Usage in Poker Copilot
- How Long is a Day?
- My Standard Nightmare
-
▼
November
(44)


8 comments:
Ignore it
Somebody at FT watches too much High Stakes Poker. Not so funny for HUD programmers though. Just be glad you they don't offer "Run It Three or Four Times" lol.
Unfortunately you can't calc an accurate win rate without taking this new feature into account. There are a lot of "features" that are optional, but this isn't one of them.
I guess the easy answer is "see how PT3 and HEM handle it." It definitely needs to be supported but I sure don't see an obvious way to do so.
Once "players agree to run it twice" could it go to some kind of side pot type database? Then figure it out from there?
Treat it as two separate hands? Name the first one #1111111-1 and the second #1111111-2.
Can't you just use an if-then-else statement?
Like:
If "2 pots" is true
calculate statistics of "showdown 1" and "pot 1"
then calculate statistics of "showdown 2" and "pot 2" and proceed to next hand
else calculate statistics of "showdown 1" and "pot 1" and proceed to next hand
Maybe it should be called "run 1", which includes "turn 1", "river 1", "showdown 1" and "pot 1".
So make it do everything like normal except if PCP identifies that there are 2 pots in one game number, it calculates the pots as individual results in a sense, but no different to a game number only having one pot.
Because if you are all-in before the turn then what is there left to calculate apart from $ won, bb/100, WtS, WaS. Statistics like aggression could only be calculated up until the all-in on the flop, right?
I might be chatting shit, though if I'm not you've probably already figured it out, but whatever!
I've only messed around with the very basics of programming just for jokes a while back and I was super tired at the time of writing this, so I might be far off. lol
Here's my two cents on the algorithm. The key to reporting the cash properly is the summary sections:
*** SUMMARY 1 ***
Seat 2: YYYYYY (small blind) showed [Qh Th] and won ($1,029) with two pair, Queens and Fours
*** SUMMARY 2 ***
Seat 1: XXXXXX (big blind) showed [3d Ad] and won ($1,029) with a pair of Aces
At the time of the choice to split into two pots the money has already gone in, so the hero amount at risk isn't affected by this change. Thus the dollar accounting is simple and straightforward. If you see "Showdown 1" and "Showdown 2" in the history file you fork to the multi-pot scenario.
For hand analysis purposes what you have here is two halves of a transaction. You have to fork to a truth table to determine how to report what happened for the hand / position analysis. Win both = win, lose both = lose, win one lose one = chop. Then handle win / lose / chop as you would in a single showdown scenario.
It's a bunch of new code, which is an annoyance, but it really shouldn't be that difficult to parse out the details into the structures you're already using.
The simplest way is probably to parse the hand and copy into two hands if you detect 'agree to run it twice'. Then treat as two separate hands.
Theoretically it is two separate hands.
Post a Comment