Студопедия
Случайная страница | ТОМ-1 | ТОМ-2 | ТОМ-3
АвтомобилиАстрономияБиологияГеографияДом и садДругие языкиДругоеИнформатика
ИсторияКультураЛитератураЛогикаМатематикаМедицинаМеталлургияМеханика
ОбразованиеОхрана трудаПедагогикаПолитикаПравоПсихологияРелигияРиторика
СоциологияСпортСтроительствоТехнологияТуризмФизикаФилософияФинансы
ХимияЧерчениеЭкологияЭкономикаЭлектроника

Technical documentation

Читайте также:
  1. Civil Engineering: Technical Specialties
  2. St. Petersburg State Polytechnical University as a scientific center. My department.
  3. Technical Reference
  4. Technical Reference
  5. The Vologda State Technical University
  6. Unified system for design documentation. Basic inscriptions
Помощь в написании учебных работ
1500+ квалифицированных специалистов готовы вам помочь

The Validator basically consists of a set of several hundred rules to be checked. Each rule is written in pseudo-code, that can be translated into C-macros easily (there is a little Perl-script for that purpose, "rules2cpp.pl"). Each rule consists of:

 

- a unique ID for the test case

- a flag to distinguish heuristic and non-heuristic rules

- some verbal reasoning.

- a precondition, that checks, if a rule can be applied to the current game state

- a postcondition, that has to be met, if a rule can be applied

- a list of symbols, that got used and are possibly affected in case of an error

 

In practice it looks like this:

 

BEGIN_TESTCASE

TESTCASE_ID ("0501")

HEURISTIC_RULE (false)

REASONING ("If it's my turn, then there has to be always a check or a call button.")

PRECONDITION ("ismyturn")

POSTCONDITION ((("myturnbits" & BUTTON_CHECK) != 0) || (("myturnbits" & BUTTON_CALL) != 0))

SYMBOLS_POSSIBLY_AFFECTED ("ismyturn, myturnbits")

END_TESTCASE

 

Log Files

OpenHoldem will generate a number of log files as it operates. The verbosity of the standard log and the Poker Tracker log can be set in {Preferences}.

 

Standard Log

This contains key actions that OpenHoldem sees, such as connection to a new table, table reset, and hand resets, player actions, as well as detailed before and after Autoplayer action information. The before-after Autoplayer action information is saved as a single line with the following format:

 

# hand commoncard rank poker win los tie P nit bestaction - play* call bet pot balance - FCRA FCRA swag

 

From left to right, the fields in this line are:

- # - Number of chairs at the table (as defined in the Table Map)

- hand - your hole cards

- commoncard – the board cards

- rank - your hand rank (as specified in {Preferences})

- poker - your poker hand

- win / los / tie - the prwin/prlos/prtie Iterator results

- P - the results from your f$P formula

- nit - your NIT setting from the Table Map

- bestaction - the action that the Autoplayer should take, based on the primary function results

- play - the actual action taken by the Autoplayer (may not be the same as best action, if the best action button is not present, for example)

- call / bet / pot / balance - the value of call, bet, pot and balance symbols

- first FCRA - the status of the fold, call, check, raise and allin buttons as seen by the scraper engine

- second FCRA - the status of the f$call, f$rais and f$alli functions

- swag - the value of the f$swag function


Дата добавления: 2015-07-20; просмотров: 119 | Нарушение авторских прав


 

 

Читайте в этой же книге: Poker Value | User DLL | How OpenHoldem calls DLL functions | Using Hand Lists | Preferences | Iterations and Standard Deviation | How to use it from a DLL | Starting Hand Ranking | PokerPro | Poker Tracker symbols |
<== предыдущая страница | следующая страница ==>
Conclusion| Familiarizing yourself with ManualMode

mybiblioteka.su - 2015-2022 год. (0.019 сек.)