in reply to Poker Probability Processor

Any chance of something that would tell me what my friends were holding?

Seriously: you may be able to verify statistics from some of the existing poker research.

Where you classify hand, you may be able to optimise this further (this may only make a trivial increase in speed):

  1. A pair can't be a flush or a straight so don't do flush processing (in a 5 or 6 card deck, TK in a 7 card deck)
  2. Conversely (it may be faster to iterate through flush processing (4 suits vs 13 cards) first but flushes are less frequent than pairs...

Very, very cool. Easy to read and I'm going to snaffle the parameter passing/initialisation for my next script. Thanks for posting this.

Be careful when you go to Vegas ;-)

Replies are listed 'Best First'.
Re: Re: Poker Probability Processor
by Lexicon (Chaplain) on May 15, 2001 at 15:28 UTC
    The big slowdown right now is absolutly in the Flush processing. When I modulize it, I'll be checking into optimizations like you suggest. Classify_Hand takes about twice as long as Combinate. I'm sure (well, hope) I can bring it down an order of magnitude.

    The first iteration of a game enhancer version is at least 3 months away. I know what you're looking for, but making it both real-time-fast and accurate enough to be meaningful will be difficult. And then you'll have to convince them to allow your laptop at the table. ;)

    Thanks for the input! Let me know how your tweeking goes.

    -Lexicon

[reply]

In Section Cool Uses for Perl