SummerOfCodeProposal AI Improvement Crab - Revision history

Esr: Hide historical instance of "SVN" from mediawiki search to avoid false positives.

2013-03-21T02:53:53Z

Hide historical instance of "SVN" from mediawiki search to avoid false positives.

Esr: Hide historical instance of "Subversion" from mediawiki search to avoid false positives.

2013-03-21T01:07:59Z

Hide historical instance of "Subversion" from mediawiki search to avoid false positives.

Crab: /* Goals */ updated progress

2009-08-17T22:03:56Z

‎Goals: updated progress

Crab: /* Timeline */ update

2009-08-17T21:59:50Z

‎Timeline: update

Crab: /* Timeline */

2009-08-01T19:11:53Z

‎Timeline

Crab: /* Goals */

2009-08-01T19:05:20Z

‎Goals

Show changes

Crab: /* Timeline */

2009-04-20T22:22:10Z

‎Timeline

Crab: /* Patches and commits */

2009-04-11T16:42:02Z

‎Patches and commits

Crab: /* Patches and commits */

2009-04-11T16:41:43Z

‎Patches and commits

Crab: /* Answers to those questions */ timezone changes with DST

2009-04-05T14:05:56Z

‎Answers to those questions: timezone changes with DST

@@ Line 245: / Line 245: @@
 | + ||Mar&nbsp;19&nbsp;-&nbsp;Mar&nbsp;22 || Familiarize myself with important parts of current Wesnoth AI code and Wesnoth way of doing things.
 |-
-| + || Mar&nbsp;23&nbsp;-&nbsp;Mar&nbsp;27 ||  Discuss implementation ideas and details. Fix some more bugs. Gain SVN commit access.
+| + || Mar&nbsp;23&nbsp;-&nbsp;Mar&nbsp;27 ||  Discuss implementation ideas and details. Fix some more bugs. Gain S&shy;&shy;V&shy;&shy;N commit access.
 |-
 | + || Mar&nbsp;28&nbsp;-&nbsp;Mar&nbsp;31 || Improve the AI lifecycle handling to allow AI hot-redeployment. Clean up current mess with AI parameter handling in team.cpp (without breaking anything, that is).  Create a test scenario for interactive testing of the AIs
@@ Line 386: / Line 386: @@
 | 1.2.4
 | Batch testing
-| I will organize a test server which will run test scenarios of "ai vs ai" and "ai arena" type and store their results to a small postgresql database with a small web frontend (numbers only). This test server will be able compile latest wesnoth source from svn and do the tests, storing the results in the DB and sending the results (or compilation errors, to a pre-defined list of emails.
+| I will organize a test server which will run test scenarios of "ai vs ai" and "ai arena" type and store their results to a small postgresql database with a small web frontend (numbers only). This test server will be able compile latest wesnoth source from s&shy;&shy;v&shy;&shy;n and do the tests, storing the results in the DB and sending the results (or compilation errors, to a pre-defined list of emails.
 | DONE
 |-
@@ Line 517: / Line 517: @@
 == Patches and commits ==
-I've earned a <b>svn write access</b> to the Wesnoth source repository on Mar 27.<br/>
+I've earned a <b>s&shy;&shy;v&shy;&shy;n write access</b> to the Wesnoth source repository on Mar 27.<br/>
 I've already contributed some patches to make debugging easier and to fix some crashes related with FormulaAI. <br/>
 [[https://gna.org/bugs/?13218 Bug 13218]] - I've spotted and fixed an infinite loop (which hangs the game) in the AI if it persistently tries to move unit to occupied square, with a hint from <i>Sirp</i> and some help from <i>Dragonking</i><br/>
@@ Line 559: / Line 559: @@
 Applied Mathematics, 6th year, Faculty of Cybernetics, Kiev University, Ukraine.
-<b>1.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for Wesnoth. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.</b><br/>
+<b>1.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for Wesnoth. If you have gained commit access to our S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.</b><br/>
-Yes, I've contributed some patches and fixed some bugs. I've earned commit access to Wesnoth svn on March 27. See [[SummerOfCodeProposal_AI_Improvement_Crab#Patches_and_commits|My Patches and commits]]
+Yes, I've contributed some patches and fixed some bugs. I've earned commit access to Wesnoth s&shy;&shy;v&shy;&shy;n on March 27. See [[SummerOfCodeProposal_AI_Improvement_Crab#Patches_and_commits|My Patches and commits]]
 <h3>Experience</h3>
@@ Line 653: / Line 653: @@
 <b>5.2) Which tools do you normally use for development? Why do you use them?</b><br/>
-vi, gdb, find, fgrep, small shell scripts, svn, git, Eclipse under GNU/Linux; Visual Studio and Eclipse under Windows. My work machine is a notebook running Debian GNU/Linux.
+vi, gdb, find, fgrep, small shell scripts, s&shy;&shy;v&shy;&shy;n, git, Eclipse under GNU/Linux; Visual Studio and Eclipse under Windows. My work machine is a notebook running Debian GNU/Linux.
 <b>5.3) What programming languages are you fluent in?</b><br/>

@@ Line 642: / Line 642: @@
 <b>5.1) Are you familiar with any of the following tools or languages?</b><br/>
-<b>* Subversion (used for all commits)</b><br/>
+<b>* Subv&shy;&shy;ersion (used for all commits)</b><br/>
 yes, both with command-line and gui.<br/>
 <b>* C++ (language used for all the normal source code)</b><br/>

@@ Line 324: / Line 324: @@
 | AI Module Redesign
 | I will fork formula_ai components into 'stable' and development.
+| DONE
 |-
 | 7
@@ Line 373: / Line 373: @@
 | Unit testing
 | I will create a unit test for each external public interface function (used by rest of the game) in the AI module. ( This 'external public interface' means, in trunk,  'public interfaces of <i>ai_manager</i> and <i>ai_configuration</i>' )
+| NOT DONE
 |-
 | 14
@@ Line 380: / Line 380: @@
 | Interactive testing
 | I will add (to AI Arena) at least 5 situations for each of the test topics: leadership, healing, poisoning, backstab, zoc awareness.
+| AI ARENA IMPROVEMENT IN PROGRESS (see patch #1169)
 |-
 | 15
@@ Line 394: / Line 394: @@
 | Batch testing
 | Integrate AI batch testing with stats.wesnoth.org (I'm listing this as 'SHOULD' because this depends not only on me, but also on guys who will do stats.wesnoth.org. On my side, I'll be able to write and host a small script in perl/php/python to pull/push ai batch testing stat data, or code this inside the game in c++ - but I do not know at the moment what method they will prefer.)
-| PARTIALLY
+| PARTIALLY, WORK IN PROGRESS
 |-
 | 17
@@ Line 401: / Line 401: @@
 | Formula function library
 | I will refactor all 1.6 formula functions to use the game rule abstraction layer extracted in 1.1, thus they will take 'ai perceptions about game rules' into account.
+| PARTIALLY
 |-
 | 18
@@ Line 408: / Line 408: @@
 | Formula function library
 | I will separate, from formula_ai, all 'formula functions' in formula_ai.cpp which can be made AI-independent.
+| DONE BY DK
 |-
+|
@@ Line 422: / Line 422: @@
 | .fai improvements
 | I will add library support to .fai, based on my run_file implementation
+| NOT DONE
 |-
 | 20
@@ Line 429: / Line 429: @@
 | .fai improvements
 | I will add namespace support to .fai
+| NOT DONE
 |-
 | 21
@@ Line 436: / Line 436: @@
 | .fai improvements
 | I will add numeric type support to .fai .  Marking as SHOULD, because It is not that important, since it can be replicated in current code, it will just be harder to write without explicit language support.
+| DONE BY DK
 |-
 | 22
@@ Line 443: / Line 443: @@
 | .fai improvements
 | I will allow allow exception handling in .fai - throw and catch exceptions
+| WIP
 |-
 | 23
@@ Line 450: / Line 450: @@
 | .fai improvements
 | I will allow to set time limits on .fai execution. Marking this as SHOULD because this requires multithreading (watchdog on a timer) and this may lead to some problems which I cannot foresee at this point.
+| WIP
 |-
 | 24
@@ Line 457: / Line 457: @@
 | FormulaAI debugger
 | I will make a formula AI debugger, with basic stepping capabilities
+| DONE
 |-
 | 25
@@ Line 464: / Line 464: @@
 | FormulaAI debugger
 | I will add breakpoint capabilities to formula AI debugger
+| WIP
 |-
 | 26
@@ Line 471: / Line 471: @@
 | FormulaAI debugger
 | I will add tracing capabilities to formula AI debugger
+| DONE
 |-
 | 27
@@ Line 478: / Line 478: @@
 | FormulaAI debugger
 | I will add time profiling capabilities to formula AI debugger
+| WIP
 |-
+|
@@ Line 492: / Line 492: @@
 | Candidate Move Evaluation
 | I will write a framework for evaluating candidate moves in 'hypothetical' situations (which differ from current game state by a small amount - e.g. differ by expected results of several moves) without doing a full copy of the current game state.
+| NOT DONE, POSTPONED
 |-
 | 29
@@ Line 499: / Line 499: @@
 | Candidate Move Evaluation
 | I will write a a 'build and Evaluate candidate move tree' turn sequence, based on my 'candidate_move_tree'  search improvement proposal, which will run with 'acceptable' performance for at least max_depth=2 (that is better than todays algorithm, in which it effectively equals 1)
+| NOT DONE, POSTPONED
 |-
 | 30
@@ Line 506: / Line 506: @@
 | Candidate Move Evaluation
 | I will write an algorithm to aggressively prune unpromising solutions from the candidate move tree, thus allowing to set bigger max_depth in 'candidate_move_tree' implementation. Marking this as 'SHOULD', because even with max-depth=2 my implementation will be better that current in spotting synergy opportunities.
+| NOT DONE, POSTPONED
 |-
+|

@@ Line 256: / Line 256: @@
 |-
-| now || August&nbsp;1&nbsp;-&nbsp;August&nbsp;14 || Step 2: Refactor fai, increase .fai capabilities.
+| + || August&nbsp;1&nbsp;-&nbsp;August&nbsp;14 || Step 2: Refactor fai, increase .fai capabilities.
 |-
-| || August&nbsp;15 || "'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc."
+| + || August&nbsp;15 || "'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc."
 |-
-| || Afterwards || - continue to improve the AI<br/>
+| now || Afterwards || - continue to improve the AI<br/>
 |}

@@ Line 253: / Line 253: @@
 | +|| April&nbsp;4&nbsp;-&nbsp;April&nbsp;20 || Step 0: Write extended proposed AI redesign description and begin creating the AI testing framework, begin refactoring of the ai code.
 |-
-| <b>now</b>|| April&nbsp;21&nbsp;-&nbsp;June&nbsp;10 || Step 1: Redesign current AI and FormulaAI code, split them into layers with defined responsibility, finish the AI testing framework, make the code cleaner, modular, and simpler, write a library of formula AI functions which will respect basic AI tuning parameters.
+| +|| April&nbsp;21&nbsp;-&nbsp;July 31&nbsp; || Step 1: Redesign current AI and FormulaAI code, split them into layers with defined responsibility, finish the AI testing framework, make the code cleaner, modular, and simpler.
 |-
-| || June&nbsp;11&nbsp;-&nbsp;July&nbsp;10 || Step 2: Increase .fai capabilities: namespaces, exception handling, numeric datatype, libraries. Write a good Formula_AI debugger.
+| now || August&nbsp;1&nbsp;-&nbsp;August&nbsp;14 || Step 2: Refactor fai, increase .fai capabilities.
 |-
-| || July&nbsp;11&nbsp;-&nbsp;August&nbsp;10 || Step 3: Implement my AI idea (candidate_move_tree) in C++.
+| || August&nbsp;15 || "'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc."
 |-
 | || Afterwards || - continue to improve the AI<br/>

@@ Line 251: / Line 251: @@
 | +|| Apr&nbsp;1&nbsp;-&nbsp;Apr&nbsp;3 || Written an description and pseudocode of the AI idea I am trying to implement (Real implementation needs 'evaluate candidate move in hypothetical situation' part to work, which is hard to do in the current code, although I'll think about hacking it in just to show how it will work.)
 |-
-| <b>now</b>|| April&nbsp;4&nbsp;-&nbsp;April&nbsp;20 || Step 0: Write extended proposed AI redesign description and create the AI testing framework, begin refactoring of the ai code.
+| +|| April&nbsp;4&nbsp;-&nbsp;April&nbsp;20 || Step 0: Write extended proposed AI redesign description and begin creating the AI testing framework, begin refactoring of the ai code.
 |-
-| || April&nbsp;21&nbsp;-&nbsp;June&nbsp;10 || Step 1: Redesign current AI and FormulaAI code, split them into layers with defined responsibility, make the code cleaner, modular, and simpler, write a library of formula AI functions which will respect basic AI tuning parameters.
+| <b>now</b>|| April&nbsp;21&nbsp;-&nbsp;June&nbsp;10 || Step 1: Redesign current AI and FormulaAI code, split them into layers with defined responsibility, finish the AI testing framework, make the code cleaner, modular, and simpler, write a library of formula AI functions which will respect basic AI tuning parameters.
 |-

@@ Line 498: / Line 498: @@
 [[https://gna.org/bugs/?13345 Bug 13345]] - I've fixed a crash at start of scenario 19 in "The Legend of Wesmere".<br/>
 [[https://gna.org/bugs/?13348 FR 13348]] - I've added info about current attack bonus (due to timeofday/alignment) of unit in Formula AI.<br/>
-[[https://gna.org/bugs/?13348 Bug 13352]] - I've fixed a bug with allied AI sides behaving stupidly if a leader's initial village capture moves him closer to his ally's keep than his own.<br/>
+[[https://gna.org/bugs/?13352 Bug 13352]] - I've fixed a bug with allied AI sides behaving stupidly if a leader's initial village capture moves him closer to his ally's keep than his own.<br/>
 <b>My immediate work plans:</b><br/>

@@ Line 495: / Line 495: @@
 [[http://svn.gna.org/viewcvs/wesnoth?rev=34329&view=rev r34329]] - I've used those new capabilities to create an [[AI_Arena| AI Arena - a framework to easily test the AIs in specified situations]]<br/>
 [[http://svn.gna.org/viewcvs/wesnoth?rev=34378&view=rev r34378]] - I've fixed enemy_units formula to not include incapacitated units, such as stoned units on Caves of the Basilisk<br/>
 <b>My immediate work plans:</b><br/>
 Make the game get multiplayer AI list from the list of AI configuration files in data/ai/ais/ directory to allow 'AI is an addon' paradigm to work <br/>
-Begin my refactoring of ai-game interface<br/>
+Continue my refactoring of ai-game interface<br/>
 ==Answers to those questions==

@@ Line 626: / Line 626: @@
 <b>5.5) At what hours are you awake and when will you be able to be in IRC (please specify in UTC)</b><br/>
-I'm in UTC+2 timezone. I am normally awake from +10 UTC to +02 UTC, and most of that time I'm at home, so I'm able to be in IRC.
+I'm in UTC+3 timezone in summer. I am normally awake from +9 UTC to +01 UTC, and most of that time I'm at home, so I'm able to be in IRC.
 <b>5.6) Would you mind talking with your mentor on telephone / internet phone? We would like to have a backup way for communications for the case that somehow emails and IRC do fail.</b><br/>