Hello,
I'm looking for an algorithm that finds the poker combinations (specifically straight, flush, full house, four of a kind, and straight flush) in a set of 13 cards. The most naive implementations is to check each element in a power set of the cards (hence 1287 possible combinations), but experience tells me there is always a better way.
thanks.
Find poker combination in a set of cards
For such a limited set of rules as poker hands, I would not extract 5-card hands and search for winning hands but search for hands in the entire set of cards.
Sort the cards by face value and start with the most valuable hand and search for it:
Sorting the cards by decreasing face value makes it easy to find sequences of identical (for a 4-of-a-kind) or consecutive (for a straight) values.
Sort the cards by face value and start with the most valuable hand and search for it:
- Is there any sequence of 5 consecutive face values of the same suite?
- Are there four cards of the same face value?
- Are there three cards of one face value and two cards of another face value?
- Are there five cards of the same suite?
- ... and so on.
Sorting the cards by decreasing face value makes it easy to find sequences of identical (for a 4-of-a-kind) or consecutive (for a straight) values.
Brother Bob's approach is the best and traditionally used one, also in the case when joker cards are present. Even though the logic needs to be carefully thought out, it will beat a naive "check all 5-subsets of 13 cards".
Brother Bob's idea is generally right, but there is a representation of the hand that allows for much faster code: Store each suit as a 13-bit integer, indicating which cards are present in the hand.
Since 2^13 = 8192 is a reasonably small number, you can aid the algorithm by using a few precomputed tables, with things like what is the highest bit set in a word, or what is the highest bit of a group of at least 5 consecutive bits (to detect straights).
The code would look something like this:
Since 2^13 = 8192 is a reasonably small number, you can aid the algorithm by using a few precomputed tables, with things like what is the highest bit set in a word, or what is the highest bit of a group of at least 5 consecutive bits (to detect straights).
The code would look something like this:
struct Hand {
unsigned short suit[4];
unsigned evaluate() const;
};
unsigned Hand::evaluate() const {
// Straigth flush
unsigned highest_straight_flush = 0u;
for (int i=0; i<4; ++i) {
unsigned value = highest_card_of_straight_table[suit];
if (value > highest_straight_flush)
highest_straight_flush = value;
}
if (highest_straight_flush != 0u)
return STRAIGHT_FLUSH | heighest_straight_flush;
// 4 of a kind
unsigned short all_suits = ~0u;
for (int i=0; i<4; ++i)
all_suits &= suit;
if (all_suits != 0)
return FOUR_OF_A_KIND | highest_card_table[all_suits];
// ...
}
Author
Is this for open faced Chinese poker?
No, it's for this: http://www.gamedev.n...ding-card-game/
I believe this is logically complete, but is still a bit naive:
straight
look for cards with the same face value, keep only one of them in the temporary deck
sort, look for cards with consecutive face values
5+n consecutive cards = n+1 straights (so far)
substitute cards in the straight with the same face value, add each to list
flush
sort the cards by suite,
5+n cards with the same suite = n+1 flushes
full house
sort cards, look for cards that occur >= 3. if none, quit
look for cards that occur in pairs.
C(n1,3) . C(n2,2) for faces that occur >= 3.
C(n,3) . pairs
4 of a kind
sort cards, look for 4 same face values
5th card any other card
straight flush
use previously found straights and flushes, avoid duplicate combinations
I'm still looking at alvaro's code.
Have you looked at the ideas and algorithms at
http://www.codingthe...aluator-roundup
I have ported the two-plus-two evaluator for Java to do hand matchups,
and it worked very well, although the 128 Mb table was a little ridiculous.
Between the ideas already presented, and all the free code,
I'd say you're on your way!
http://www.codingthe...aluator-roundup
I have ported the two-plus-two evaluator for Java to do hand matchups,
and it worked very well, although the 128 Mb table was a little ridiculous.
Between the ideas already presented, and all the free code,
I'd say you're on your way!
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
