User:Flixx/GSoC 2013/AI: AI: Refactor recruitment algorithm - Revision history

Egallager: link cleanup

2023-05-05T19:56:37Z

link cleanup

Egallager: heading cleanup

2023-05-05T19:55:15Z

heading cleanup

Flixx: /* Goals / Milestones */

2013-09-14T17:26:37Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-08-19T19:37:26Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-08-17T20:52:22Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-08-14T18:55:28Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-08-13T13:29:09Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-07-31T22:09:57Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-07-24T04:02:11Z

‎Goals / Milestones

Flixx: /* Goals / Milestones */

2013-07-19T16:27:55Z

‎Goals / Milestones

@@ Line 8: / Line 8: @@
 === Map Analysis===
 Previous attempts have been made to this:
 * analyze_potential_recruit_movements() analyzes nearby targets and how to reach them.
@@ Line 16: / Line 15: @@
 === Combat Analysis ===
 The current RCA AI make much use of a combat analysis. This works actually pretty well.
 Although there are still some improvements possible.
@@ Line 109: / Line 107: @@
 | May 28 - Jun 17 || ''Before the official Coding Phase:'' Do Step 1 to Step 5 (Goals). Start Coding already. Maybe provide some patches with have not necessarily something to do with recruitment to familiarize more with the Code.
 |-
-| Jun 18 - Jul 01 || Time off. See [http://wiki.wesnoth.org/index.php?title=User:Flixx/GSoC_2013/AI:_AI:_Refactor_recruitment_algorithm#time 1.7) in the Questionnaire]
+| Jun 18 - Jul 01 || Time off. See [[User:Flixx/GSoC_2013/AI:_AI:_Refactor_recruitment_algorithm#time|1.7) in the Questionnaire]]
 |-
 | Jul 02 - Jul 28 || Do everything (mandatory) up to Milestone 1.
@@ Line 134: / Line 132: @@
 ! ID !! PRIORITY !! DESCRIPTION !! <small>COMPLEXITY</small> !! <small>PROGRESS</small>
 |-
-| 1 ||  style="width: 110px;" | <p style="color:red">MANDATORY</p> || Specify configurations and [http://forums.wesnoth.org/viewtopic.php?f=8&t=38885 discuss them in the Forums]. Write the results in  [http://wiki.wesnoth.org/User:Flixx/Configuration_Specifications this wikipage]. || 2 || done without feedback
+| 1 ||  style="width: 110px;" | <p style="color:red">MANDATORY</p> || Specify configurations and [http://forums.wesnoth.org/viewtopic.php?f=8&t=38885 discuss them in the Forums]. Write the results in  [[User:Flixx/Configuration_Specifications|this wikipage]]. || 2 || done without feedback
 |-
-| 2 ||  <p style="color:red">MANDATORY</p> || Completely understand the Map Analyses of "Formula AI dev" and write a explanation in [http://wiki.wesnoth.org/User:Flixx/Recruitment_Algorithm_Collection this wikipage]. || 1 || done
+| 2 ||  <p style="color:red">MANDATORY</p> || Completely understand the Map Analyses of "Formula AI dev" and write a explanation in [[User:Flixx/Recruitment_Algorithm_Collection|this wikipage]]. || 1 || done
 |-
 | 3 ||  <p style="color:red">MANDATORY</p> || Set up a own CA for recruitment, implement a score table. Let units recruit according to some mock values in the score table. || 1 || [https://github.com/flixx/wesnoth-old/commit/fa859891f40203e6aaa61d183eda62e09b83f06e done]

@@ Line 1: / Line 1: @@
 {{SoC2013Student}}
-[[Category:SoC_Ideas_AI_Recruitment_2013]]
+==Description==
 <h4>flix: Refactor recruitment algorithm</h4>
 An AI opponent have to decide in a separate phase which units to recruit. Right now the default recruitment algorithm is very simple and can be improved in many ways. I want to make the AI recruiting better, more fun to play against and more configurable by a scenario editor.
-= Make it better =
+== Make it better ==
 (In terms of harder to play against)
-== Map Analysis==
+=== Map Analysis===
 Previous attempts have been made to this:
@@ Line 18: / Line 15: @@
 In my project I want to refactor the "Formula AI dev"-Recruitment in C++, test it, improve it and make it easy to configure.
-== Combat Analysis ==
+=== Combat Analysis ===
 The current RCA AI make much use of a combat analysis. This works actually pretty well.
@@ Line 28: / Line 25: @@
 I will give the combat analysis a refactoring and try to include all those specialties.
-== Counter Recruitment Strategies ==
+=== Counter Recruitment Strategies ===
 In order to recruit the best units for a set of enemy units and make the best use of a combat analysis, it is sometimes useful to wait for the enemy to recruit. (Not spend all money in the first round). The RCA AI will always recruit when it has enough gold available. This can be improved. The hardest part when implementing this is to decide when such a strategy is appropriate.
 I want first to introduce a state "Counter Recruitment". When the AI is in this state it will first wait (and discover) enemy units before spending all the money. Then I will test (via benchmarking) in which cases it is useful for the AI to enter or leave this state.
-== Counter-Counter Recruitment Strategies ==
+=== Counter-Counter Recruitment Strategies ===
 Note: I need a better name for this ;)
@@ Line 41: / Line 38: @@
 See [[User:Flixx/Game Theory for Recruiting]] for more.
-= Make it more Fun =
+== Make it more Fun ==
 In terms of recruitment ''more fun'' is achieved when the AI is recruiting not only one type but a good mix of all available units. This can easily be achieved by just favor rare units. The hard part here is again, how to weight it against other options.
+== Implementation Details: Score Map ==
 So far I spoke about several analyze algorithms: map-analyze, combat-analyze, counter- and counter-counter strategies, and some possibility to boost diversity.
 Here I want to say something how this algorithms could work together.
@@ Line 78: / Line 71: @@
 # One could also think about giving scouts in the first rounds a higher score.
-= Make it more configurable =
+== Make it more configurable ==
 For a better *development flow* I want first specify the configurations (in the wiki) before implementing them. Before it comes to implementation I will also use the forum to discuss my suggestions.
 See [[User:Flixx/Configuration Specifications]]
-= Purposes Idea =
+== Purposes Idea ==
 For the Idea see this page: [[User:Flixx/GSoC 2013/Idea AI Recruitment: Purposes]]
 In the scope of this project I want to take some time to implement a Proof of Concept of this idea for further evaluation. I think it is a good idea but I don't want to define the implementation of this as a project goal. Probably Purpose-Driven-Recruitment will get too complex, and I don't want to fail the goals. Though I want to plan some time at the end of the summer for this idea to see if it's worth something.
-= Multiple Leader =
+== Multiple Leader ==
 Although the AI could have multiple recruiters available it will currently only recruit with one leader. I want to change this. All necessary configurations for this are already in place (a scenario-editor can specify multiple leaders and leader specific recruitment lists).
@@ Line 101: / Line 92: @@
 When I have time I want to make the Move_Leader_To_Keep CA actually ''intelligent'' so it can be decided if it is really necessary to move all recruiters back to a keep (and if not decide which recruiter). I marked this as 'optional'.
-= Set of Goals - Brief overwiew =
+== Set of Goals - Brief overwiew ==
 * Refactor the "Formula AI dev"-Recruitment in C++, test it, improve it and make it easy to configure.
 * Refactor Combat analysis
@@ Line 113: / Line 103: @@
 * (optional) Implementing a Proof of Concept for the Purpose Idea and test it
-= Timeline =
+== Timeline ==
 {| border="1"
 | style="width: 125px;" | May 27 || ''Accepted student proposals announced by Google''
@@ Line 139: / Line 128: @@
 |}
-= Goals / Milestones =
+== Goals / Milestones ==
 (Note: I added a column "complexity" and filled it with values between 1 (easy) and 3 (complex). This is a rough guess but it helped me to balance the steps between the Milestones.)
@@ Line 228: / Line 217: @@
 |}
-=IRC=
+==IRC==
 flix
 '''1) Basics'''
@@ Line 418: / Line 407: @@
 I will add my number in the google application.

@@ Line 182: / Line 182: @@
 | 14 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters of Combat Analysis which could later be configured by aspects. Batch Test parameter variations || 2 || done
 |-
-| 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 || 90%
+| 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 || done
 |-
 | 16 ||  <p style="color:red">MANDATORY</p> || Extract parameters of Counter-Recruitment-Strategies which could later be configured by aspects. || 1 || done
@@ Line 203: / Line 203: @@
 |-
-| 22 ||  <p style="color:red">MANDATORY</p> || Review Configuration Specifications from Step 1 and adjust them if necessary. || 1 ||
+| 22 ||  <p style="color:red">MANDATORY</p> || Review Configuration Specifications from Step 1 and adjust them if necessary. || 1 || done
 |-
-| 23 ||  <p style="color:red">MANDATORY</p> || Define Aspects for the Configurations and implement missing aspects (like 'recruit-more=') and make them work with the score map. || 3 ||
+| 23 ||  <p style="color:red">MANDATORY</p> || Define Aspects for the Configurations and implement missing aspects (like 'recruit-more=') and make them work with the score map. || 3 || done
 |-
-| 24 ||  <p style="color:red">MANDATORY</p> || Test those new aspects. || 2 ||
+| 24 ||  <p style="color:red">MANDATORY</p> || Test those new aspects. || 2 || done
 |-
-| 25 ||  <p style="color:red">MANDATORY</p> || Write a separate wikipage for scenario-editors about those aspects and provide some examples and describe use-cases. || 2 ||
+| 25 ||  <p style="color:red">MANDATORY</p> || Write a separate wikipage for scenario-editors about those aspects and provide some examples and describe use-cases. || 2 || [[AI_Recruitment|done]]
 |-
-| 26 ||  <p style="color:red">MANDATORY</p> || Test recruitment with multiple leaders (I should implement and test every step with multiple leaders so there is hopefully not much to do here)  || 1 ||
+| 26 ||  <p style="color:red">MANDATORY</p> || Test recruitment with multiple leaders (I should implement and test every step with multiple leaders so there is hopefully not much to do here)  || 1 || done
 |-
 | 27 ||  <p style="color:blue">OPTIONAL</p> || Introduce a purpose memory for the AI-Units || 2 ||

@@ Line 190: / Line 190: @@
 | 18 ||  <p style="color:blue">OPTIONAL</p> || Batch-test and improve Counter- and Counter-Counter Recruitment Strategies. || 2 ||
 |-
-| 19 ||  <p style="color:red">MANDATORY</p> || Implement 'Diversity'. When weighting all other phases with 0 the AI should only recruit units, which are currently rare on the map. || 1 ||
+| 19 ||  <p style="color:red">MANDATORY</p> || Implement 'Diversity'. When weighting all other phases with 0 the AI should only recruit units, which are currently rare on the map. || 1 || done
 |-
-| 20 ||  <p style="color:red">MANDATORY</p> || Set up a parameterizable weight-system. || 1 ||
+| 20 ||  <p style="color:red">MANDATORY</p> || Set up a parameterizable weight-system. || 1 || done
 |-
-| 21 ||  <p style="color:red">MANDATORY</p> || Batch-test with different weights. Document results in this wiki page, define default weights (they will be normalized to 1 for easy configuration then) || 3 ||
+| 21 ||  <p style="color:red">MANDATORY</p> || Batch-test with different weights. Document results in this wiki page, define default weights (they will be normalized to 1 for easy configuration then) || 3 || done / not necessary

@@ Line 182: / Line 182: @@
 | 14 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters of Combat Analysis which could later be configured by aspects. Batch Test parameter variations || 2 || done
 |-
-| 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 || 70%
+| 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 || 90%
 |-
-| 16 ||  <p style="color:red">MANDATORY</p> || Extract parameters of Counter-Recruitment-Strategies which could later be configured by aspects. || 1 ||
+| 16 ||  <p style="color:red">MANDATORY</p> || Extract parameters of Counter-Recruitment-Strategies which could later be configured by aspects. || 1 || done
 |-
 | 17 ||  <p style="color:blue">OPTIONAL</p> || Implement 'Counter-Counter-Recruitment-Strategies' and test it. || 3 || done

@@ Line 178: / Line 178: @@
 |-
-| 13 ||  <p style="color:red">MANDATORY</p> || Refactor current Combat Analysis. || 3 || 90%
+| 13 ||  <p style="color:red">MANDATORY</p> || Refactor current Combat Analysis. || 3 || done
 |-
-| 14 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters of Combat Analysis which could later be configured by aspects. Batch Test parameter variations || 2 || 70%
+| 14 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters of Combat Analysis which could later be configured by aspects. Batch Test parameter variations || 2 || done
 |-
-| 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 ||
+| 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 || 10%
 |-
 | 16 ||  <p style="color:red">MANDATORY</p> || Extract parameters of Counter-Recruitment-Strategies which could later be configured by aspects. || 1 ||

@@ Line 164: / Line 164: @@
 | 7 ||  <p style="color:blue">OPTIONAL</p> || Make this implementation (Multiple Leader in MLTK CA) 'intelligent', so that it can be decided which leader shall go to a keep. || 3 ||
 |-
-| 8 ||  <p style="color:red">MANDATORY</p> || Refactor the Map Analyses of "Formula AI dev" in C++. || 3 || 90%
+| 8 ||  <p style="color:red">MANDATORY</p> || Refactor the Map Analyses of "Formula AI dev" in C++. || 3 || done
 |-
 | 9 ||  <p style="color:red">MANDATORY</p> || Test implementation of Map Analyses. || 1 || done
@@ Line 178: / Line 178: @@
 |-
-| 13 ||  <p style="color:red">MANDATORY</p> || Refactor current Combat Analysis. || 3 || 50 %
+| 13 ||  <p style="color:red">MANDATORY</p> || Refactor current Combat Analysis. || 3 || 90%
 |-
-| 14 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters of Combat Analysis which could later be configured by aspects. Batch Test parameter variations || 2 ||
+| 14 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters of Combat Analysis which could later be configured by aspects. Batch Test parameter variations || 2 || 70%
 |-
 | 15 ||  <p style="color:red">MANDATORY</p> || Implement Counter-Recruitment-Strategies. || 2 ||

@@ Line 168: / Line 168: @@
 | 9 ||  <p style="color:red">MANDATORY</p> || Test implementation of Map Analyses. || 1 || done
 |-
-| 10 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters which could later be configured by aspects. || 1 ||
+| 10 ||  <p style="color:blue">OPTIONAL</p> || Extract parameters which could later be configured by aspects. || 1 || done
 |-
 | 11 ||  <p style="color:blue">OPTIONAL</p> || Batch test Map Analyses (with parameter variations) || 2 ||