makebearoff(6) [debian man page]
MAKEBEAROFF(6) Games Manual MAKEBEAROFF(6) NAME
makebearoff - generate a GNU Backgammon bearoff database SYNOPSIS
makebearoff [-HCcgnvh] -f filename [-t PxC] [-o P] [-s cache-size] [-O filename] DESCRIPTION
makebearoff generates GNU Backgammon bearoff databases, which are used to improve play in the endgame. It can generate either two-sided (exact) databases that tell precisely the chance of winning or one-sided (approximate) databases that provide a variety of probabilities looking at each side independently. Bearoff databases can get quite large and can take a significant amount of time to generate for large numbers of chequers and/or points. OPTIONS
-f filename, --outfile filename Write the bearoff database to filename. This option must be given. -t PxC, --two-sided PxC Generate a two-sided bearoff database for P points and C chequers for each player. Be warned that the size of the database grows rapidly with larger numbers of points and chequers. -o P, --one-sided P Generate a one-sided bearoff database for P points. One-sided bearoff databases are always generated for up to fifteen chequers. -s N, --xhash-size N Use a memory cache of size N while building the database. If the cache is smaller than the database size, database generation will be slower due to disk writes. -O filename, --old-bearoff filename Reuse an already generated bearoff database. Any needed data already in this database will just be copied without regenerating it. -H, --no-header Do not write the normal bearoff database header. -C, --no-cubeful Do not calculate cubeful equities for two-sided databases. -c, --no-compress Do not compress one-sided databases. -g, --no-gammons Do not include gammon distributions in one-sided databases. -n, --normal-dist Rather than storing exact probabilities, approximate probabilities in a one-sided database with a normal distribution. -v, --version Show version information and exit. -h, --help Display usage and exit. EXAMPLES
To generate a two-sided database for up to eight chequers on six points: makebearoff -t 6x8 -f gnubg_ts.bd Note that this database is 72MB in size. To generate a one-sided database for up to fifteen chequers on ten points: makebearoff -o 10 -f gnubg_os.bd Note that this database is 118MB in size. SEE ALSO
gnubg(6), bearoffdump(6) AUTHORS
Joseph Heled, Oystein Johansen, Jorn Thyssen, and Gary Wong, with the assistance of many others <bug-gnubg@gnu.org>. This manual page was written by Russ Allbery <rra@debian.org>, for the Debian GNU/Linux system (but may be used by others). It may be redistributed and/or modified under the terms of version 2 of the GNU General Public License as published by the Free Software Foundation (the same license as GNU Backgammon). 2006-01-15 MAKEBEAROFF(6)
Check Out this Related Man Page
databases(5) GNATS configuration files databases(5) NAME
databases - the known set of GNATS databases DESCRIPTION
The databases configuration file is a site-wide configuration file containing the list of GNATS databases that are available either on the host itself or remotely over the network, together with some parameters associated with each database. It is located in the directory /usr/share/gnats. The file contains one line for each database. For databases located on the host itself, each line consists of three fields separated by colons: database name:short description:/path/to/database The first field is the database name. This is the name used to identify the database when invoking programs such as query-pr or send-pr, either by using the --database option of the program or by setting the GNATSDB environment variable to the name of the database. The sec- ond field is a short human-readable description of the database contents, and the final field is the directory where the database contents are kept. For a database that is located across a network, but which should be accessible from this host, the entry for the database should look like this: database name:short description of database::hostname:port The first two fields are the same as for local databases, the third field is empty (notice the two adjacent `:' symbols, indicating an empty field), the fourth field is the hostname of the remote GNATS server, and the fifth field is the port number that the remote GNATS server is running on. Note that if you add a new local database, you must create its data directory, including appropriate subdirectories and administrative files after adding an entry to databases. This is best done using the mkdb tool. Lines beginning with a # are ignored. The database name default is special; this is the entry used if no database name is specified via a --database option or the GNATSDB envi- ronment variable. SEE ALSO
Keeping Track: Managing Messages With GNATS (also installed as the GNU Info file gnats.info) databases(5), dbconfig(5), delete-pr(8), edit-pr(1) file-pr(8), gen-index(8), gnats(7), gnatsd(8), mkcat(8), mkdb(8), pr-edit(8), query- pr(1), queue-pr(8), send-pr(1). COPYING
Copyright (c) 1993, 2000, 2003, Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. GNATS
August 2003 databases(5)