acpc_dealer 0.0.1

data/vendor/project_acpc_server/README

@@ -0,0 +1,113 @@
+This README contains information about the server code for the Annual Computer
+Poker Competition.  Please see the LICENCE file for information regarding the
+code's licence.
+
+===== Software Requirements =====
+
+This code was developed and tested for use on Unix based systems.  Though it
+may work on other platforms, there are no guarantees.
+
+You will need standard Unix developer tools to build the software including
+gcc, and make.
+
+===== Getting Started =====
+
+* Building the code
+
+The Makefile provides instructions for compiling the code.  Running 'make' from
+the command line will compile the required programs.
+
+
+* The programs
+
+dealer - Communicates with agents connected over sockets to play a game
+example_player - A sample player implemented in C
+play_match.pl - A perl script for running matches with the dealer
+
+Usage information for each of the programs is available by running the
+executable without any arguments.
+
+
+* Playing a match
+
+The fastest way to start a match is through the play_match.pl script.  An
+example follows:
+
+$ ./play_match.pl matchName holdem.limit.2p.reverse_blinds.game 1000 0 Alice ./example_player.limit.2p.sh Bob ./example_player.limit.2p.sh
+
+After play_match.pl finishes running, there will be two output files for the
+dealer and two output files for each player in the game:
+
+matchName.err - The stderr from dealer including the messages sent to players
+matchName.log - The log for the hands played during the match
+matchName.playerN.std - stdout from player N
+matchName.playerN.err - stderr from player N
+
+Note, play_match.pl expects player executables that take exactly two arguments:
+the server IP followed by the port number.  The executable must be specified
+such that it is either a path or the executable name if it can be found in your
+$PATH.
+
+If you need to pass specific arguments to you agent, we suggest wrapping it in
+another script.  play_match.pl will pass any extra arguments to dealer.
+Matches can also be started by calling dealer and starting the players
+manually.  More information on this is contained in the dealer section below.
+
+
+* dealer
+
+Running dealer will start a process that waits for other players to connect to
+it.  After starting dealer, it will output something similar to the following:
+
+$ ./dealer matchName holdem.limit.2p.reverse_blinds.game 1000 0 Alice Bob
+16177 48777
+# name/game/hands/seed matchName holdem.limit.2p.reverse_blinds.game 1000 0
+#--t_response 10000
+#--t_hand 600000
+#--t_per_hand 6000
+
+On the first line of output there should be as many numbers as there are
+players in the game (in this case, "16177" and "48777").  These are the ports
+the dealer is listening on for players.  Note that these ports are specific to
+the positions for players in the game.
+
+Once all the players have connected to the game, the dealer will begin playing
+the game and outputting the messages sent to each player.  After the end of the
+match, you should have a log file called matchName.log in the directory where
+dealer was started with the hands that were played.
+
+Matches can also be started by starting the dealer and connecting the
+executables by hand.  This can be useful if you want to start your own program
+in a way that is difficult to script (such as running it in a debugger).
+
+
+==== Game Definitions ====
+
+The dealer takes game definition files to determine which game of poker it
+plays.  Please see the included game definitions for some examples.  The code
+for handling game definitions is found in game.c and game.h.
+
+Game definitions can have the following fields (case is ignored):
+
+gamedef - the starting tag for a game definition 
+end gamedef - ending tag for a game definition
+stack - the stack size for each player at the start of each hand (for no-limit)
+blind - the size of the blinds for each player (relative to the dealer)
+raisesize - the size of raises on each round (for limit games)
+limit - specifies a limit game
+nolimit - specifies a no-limit game
+numplayers - number of players in the game
+numrounds - number of betting rounds per hand of the game
+firstplayer - the player that acts first (relative to the dealer) on each round
+maxraises - the maximum number of raises on each round
+numsuits - the number of different suits in the deck
+numranks - the number of different ranks in the deck
+numholecards - the number of private cards to deal to each player
+numboardcards - the number of cards revealed on each round
+
+Empty lines or lines with '#' as the very first character will be ignored
+
+If you are creating your own game definitions, please note that game.h defines
+some constants for maximums in games (e.g., number of rounds).  These may need
+to be changed for games outside of the what is being run for the Annual
+Computer Poker Competition.

data/vendor/project_acpc_server/README.submission

@@ -0,0 +1,42 @@
+#############################################################
+# Please fill out the following information about your team 
+#############################################################
+
+Team Name:
+Agent Name (can be the same as team name):
+
+For each team member, please list the following:
+Name, Team leader (y/n)?, e-mail, Academic (y/n, position - e.g., PhD student)?, University/Business affiliation, Location (city, province/state, country)
+
+Was this submission part of an academic class project?  What level of class
+(undergraduate/graduate)?
+
+
+###########################################################################
+# Please provide as much information about your agent as possible as the
+# competition organizers are very interested in knowing more about the
+# techniques used by our competitors.
+###########################################################################
+
+1) Is your agent dynamic?  That is, does its strategy change throughout the
+course of a match, or is the strategy played the same throughout the match?
+
+2) Does your agent use a (approximate) Nash equilibrium strategy?
+
+3) Does your agent attempt to model your opponents?  If so, does it do so
+online during the competition or offline from data (e.g., using logs of play or
+the benchmark server)?
+
+4) Does your agent use techniques that would benefit from additional CPU time
+during the competition?
+
+5) Does your agent use techniques that would benefit from additional RAM during
+the competition?
+
+6) Would you agent benefit from additional disk space?
+
+One/Two Paragraph Summary of Technique
+
+
+References to relevant papers, if any
+

data/vendor/project_acpc_server/acpc_play_match.pl

@@ -0,0 +1,101 @@
+#!/usr/bin/perl
+
+# Copyright (C) 2011 by the Computer Poker Research Group, University of Alberta
+
+use Socket;
+use File::Basename;
+
+$hostname = `hostname` or die "could not get hostname";
+chomp $hostname;
+@hostent = gethostbyname( $hostname );
+$#hostent >= 4 or die "could not look up $hostname";
+$hostip = inet_ntoa( $hostent[ 4 ] );
+
+$#ARGV >= 3 or die "usage: play_match.pl matchName gameDefFile #Hands rngSeed player1name player1exe player2name player2exe ... [options]";
+
+$numPlayers = -1;
+open FILE, '<', $ARGV[ 1 ] or die "couldn't open game definition $ARGV[ 1 ]";
+while( $_ = <FILE> ) {
+
+    @_ = split;
+
+    if( uc( $_[ 0 ] ) eq 'NUMPLAYERS' ) {
+	$numPlayers = $_[ $#_ ];
+    }
+}
+close FILE;
+
+$numPlayers > 1 or die "couldn't get number of players from $ARGV[ 1 ]";
+
+
+$#ARGV >= 3 + $numPlayers * 2 or die "too few players on command line";
+
+pipe STDINREADPIPE, STDINWRITEPIPE or die "couldn't create stdin pipe";
+pipe STDOUTREADPIPE, STDOUTWRITEPIPE or die "couldn't create stdout pipe";
+
+$dealerPID = fork();
+if( $dealerPID == 0 ) {
+    # we're the child
+
+    # replace standard in and standard out with pipe
+    close STDINWRITEPIPE;
+    close STDOUTREADPIPE;
+    open STDIN, '<&STDINREADPIPE' or die "can't dup STDIN";
+    open STDOUT, '>&STDOUTWRITEPIPE' or die "can't dup STDOUT";
+    open STDERR, ">>$ARGV[ 0 ].err" or die "can't open log file $ARGV[ 0 ].err";
+
+    @args = ( "dealer", $ARGV[ 0 ], $ARGV[ 1 ],
+	      $ARGV[ 2 ], $ARGV[ 3 ] );
+
+    # add names to the arguments
+    for( $p = 0; $p < $numPlayers; ++$p ) {
+	push @args, $ARGV[ 4 + $p * 2 ];
+    }
+
+    # add any extra arguments (options?) to the arguments
+    for( $i = 4 + $numPlayers * 2; $i <= $#ARGV; ++$i ) {
+	push @args, $ARGV[ $i ];
+    }
+    exec { "./dealer" } @args or die "Couldn't run dealer";
+}
+
+close STDINREADPIPE;
+close STDOUTWRITEPIPE;
+
+$_ = <STDOUTREADPIPE> or die "couldn't read port description from dealer";
+@_ = split;
+$#_ + 1 >= $numPlayers or die "couldn't get enough ports from $_";
+
+for( $p = 0; $p < $numPlayers; ++$p ) {
+
+    $playerPID[ $p ] = fork();
+
+    if( $playerPID[ $p ] == 0 ) {
+	# we're the child
+
+	# log standard out and standard error
+	open STDOUT, ">$ARGV[ 0 ].player$p.std"
+	    or die "can't dup player $p STDOUT";
+	open STDERR, ">$ARGV[ 0 ].player$p.err"
+	    or die "can't dup player $p STDERR";
+
+	($playerExec, $playerDir) = fileparse( $ARGV[ 4 + $p * 2 + 1 ] );
+	chdir $playerDir or die "Can't cd to $playerDir: $!\n";
+	exec { "./$playerExec" } ( "./$playerExec", $hostip, $_[ $p ] )
+	    or die "couldn't run $playerExec from $playerDir for player $p";
+    }
+}
+
+$_ = <STDOUTREADPIPE>;
+
+for( $p = 0; $p < $numPlayers; ++$p ) {
+    waitpid( $playerPID[ $p ], 0 );
+}
+
+waitpid( $dealerPID, 0 );
+
+$_ or die "couldn't get values from dealer";
+
+print $_;
+
+exit( 0 );