User:Dragos/GsoC 2013/AI: Refactor recruitment algorithm - Revision history

Dragos at 15:27, 16 May 2013

2013-05-16T15:27:54Z

Dragos at 15:25, 16 May 2013

2013-05-16T15:25:12Z

Dragos at 14:14, 3 May 2013

2013-05-03T14:14:06Z

Dragos at 22:47, 30 April 2013

2013-04-30T22:47:21Z

Dragos at 22:36, 30 April 2013

2013-04-30T22:36:58Z

Dragos at 22:31, 30 April 2013

2013-04-30T22:31:00Z

Dragos at 20:01, 30 April 2013

2013-04-30T20:01:53Z

Dragos at 21:59, 29 April 2013

2013-04-29T21:59:57Z

Dragos at 21:59, 29 April 2013

2013-04-29T21:59:51Z

Dragos at 21:36, 29 April 2013

2013-04-29T21:36:02Z

@@ Line 18: / Line 18: @@
 The recruitment algorithm will choose the best unit to recruit by taking into account many factors and combining them. It’s very important that the AI will recruit optimally (or at least as optimal as possible). This includes recruiting with more than one leader and selecting the best units for each leader. The algorithm should take into account the enemy units, their position and the map in general to make the best recruiting decisions. (This is already taken into account, but we should still integrate it with multiple leader recruit, as sometimes, for instance, it is better to only recruit with the second leader than only with the first.)
-For example, we should make units that are good against the closest enemy units, since the closer a unit is, the more important it will be when choosing what to counter-recruit. This is to try to get through the first line of defense. It does not matter if our new units are good against the units far away if they are bad with the closer units that they would have to get through to reach the other units.
+One important idea is making the AI recruit units that are good against the closest enemy units, since the closer a unit is, the more important it will be when choosing what to counter-recruit. This is to try to get through the first line of defense. It does not matter if our new units are good against the units far away if they are bad with the closer units that they would have to get through to reach the other units.
 At the same time, we need to consider the next wave of units. In many cases the AI/ player in the next recruitment wave recruits units that will complement the current units. There are many small factors that will influence our decisions, like mostly ignoring the units with low HP, except the case when they are about to level up (since if it has low HP but levels up, it will have full HP and be a bigger threat to our side).

@@ Line 16: / Line 16: @@
 ==Optimal recruiting==
-This idea is somewhat broad and contains many small ideas that will accomplish the needed optimality of recruiting.
+The recruitment algorithm will choose the best unit to recruit by taking into account many factors and combining them. It’s very important that the AI will recruit optimally (or at least as optimal as possible). This includes recruiting with more than one leader and selecting the best units for each leader. The algorithm should take into account the enemy units, their position and the map in general to make the best recruiting decisions. (This is already taken into account, but we should still integrate it with multiple leader recruit, as sometimes, for instance, it is better to only recruit with the second leader than only with the first.)
-It’s very important that the AI will recruit optimally (or at least as optimal as possible). This includes recruiting with more than one leader and select the best units for each leader.
+For example, we should make units that are good against the closest enemy units, since the closer a unit is, the more important it will be when choosing what to counter-recruit. This is to try to get through the first line of defense. It does not matter if our new units are good against the units far away if they are bad with the closer units that they would have to get through to reach the other units.
-The algorithm should take into account the enemy units, their position and the map in general to make the best recruiting decisions. (This is already taken into account but we should still integrate it with multiple leader recruit. Sometimes, for example, is better to only recruit with the second leader then only with the first).
+At the same time, we need to consider the next wave of units. In many cases the AI/ player in the next recruitment wave recruits units that will complement the current units. There are many small factors that will influence our decisions, like mostly ignoring the units with low HP, except the case when they are about to level up (since if it has low HP but levels up, it will have full HP and be a bigger threat to our side).
-We should also take into account the that are already on the field. So, if our group of units already counters archers, we should not try as hard to recruit archers.
+Another idea that I consider important to the decision is to simulate the next state to some extent, as this will help us make the decision on what to recruit. A small note on this idea: we can compress the number of states and ignore irrelevant information about the game-state (in short, simulating the next turn recruitment-wise will be way easier than for other purposes - like attacking for instance). Because of this, the most important thing we need to focus is having the best function to express the advantage of a certain state.
-This should also take into account what happens when the AI recruits first, as it should be as hard as possible for the enemy to counter-recruit. Also, it should stop recruiting when it has a noticeable advantage in the field and wait to counter the next wave of enemy units.
+We should also take into account the units that are already on the field. So, if our group of units already counters archers, we should not try as hard to recruit archers.
 ==Unit purpose and goals==

@@ Line 1: / Line 1: @@
 {{SoC2013Student}}
 [[Category:SoC Ideas AI Recruitment 2013]]
 =Description=
@@ Line 182: / Line 179: @@
-===Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".===
+===Include an estimated timeline for your work on the project. Include as much technical detail about your implementation as you can===
 {| class="wikitable"
@@ Line 214: / Line 211: @@
 | After SOC (PLAN) || Continue working for Wesnoth
 |}
 ===What do you expect to gain from this project?===

@@ Line 196: / Line 196: @@
 | 5 July - 16 July (12 days) || Adding the feature to Counter-recruiting when necessary/good
 |-
-| 17 July - 21 July (5 days) ||  Testing the changes so far, adding small Customization features from idea 3
+| 17 July - 21 July (5 days) ||  Testing the changes so far, adding small Customization features from [[#Customizability|idea 3]]
 |-
 | 22 July- 29 July (8 days) || Adding simple goals when recruiting, making units respect those simple goals.

@@ Line 192: / Line 192: @@
 | 24 June - 28 June (5 days) ||  Making the AI recruit more optimally considering the multiple leaders
 |-
-| 28 June - 4 July (7 days) || Reworking the recruiting algorithm to make it hard for enemies to counter recruit
+| 29 June - 4 July (6 days) || Reworking the recruiting algorithm to make it hard for enemies to counter recruit
 |-
-| 5 July - 17 July (13 days) || Adding the feature to Counter-recruiting when necessary/good
+| 5 July - 16 July (12 days) || Adding the feature to Counter-recruiting when necessary/good
 |-
 | 17 July - 21 July (5 days) ||  Testing the changes so far, adding small Customization features from idea 3
@@ Line 202: / Line 202: @@
 | 30 July- 2 August (4 days) || Preparing for mid term Evaluation and start working on more complex goals
 |-
-| 2  August - 7 August (8 days) || Adding the complex goals
+| 3  August - 8 August (6 days) || Adding the complex goals
 |-
-| 8  August - 21 August (14 days) || Optional: Making the AI detect useful goals that will help win the game and testing all changes
+| 9  August - 21 August (13 days) || Optional: Making the AI detect useful goals that will help win the game and testing all changes
 |-
 | 22  August - 4 September (14 day) || Customization: Limiting number of units

← Older revision		Revision as of 22:31, 30 April 2013
Line 184:		Line 184:
	===Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".===		===Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".===

		+	{\| class="wikitable"
		+	\|-
		+	! width="300pt"\| Time Frame !! Milestone
		+	\|-
		+	\| 14 June - 23 June (10 days) \|\| Adding support to recruit with more leaders
		+	\|-
		+	\| 24 June - 28 June (5 days) \|\| Making the AI recruit more optimally considering the multiple leaders
		+	\|-
		+	\| 28 June - 4 July (7 days) \|\| Reworking the recruiting algorithm to make it hard for enemies to counter recruit
		+	\|-
		+	\| 5 July - 17 July (13 days) \|\| Adding the feature to Counter-recruiting when necessary/good
		+	\|-
		+	\| 17 July - 21 July (5 days) \|\| Testing the changes so far, adding small Customization features from idea 3
		+	\|-
		+	\| 22 July- 29 July (8 days) \|\| Adding simple goals when recruiting, making units respect those simple goals.
		+	\|-
		+	\| 30 July- 2 August (4 days) \|\| Preparing for mid term Evaluation and start working on more complex goals
		+	\|-
		+	\| 2 August - 7 August (8 days) \|\| Adding the complex goals
		+	\|-
		+	\| 8 August - 21 August (14 days) \|\| Optional: Making the AI detect useful goals that will help win the game and testing all changes
		+	\|-
		+	\| 22 August - 4 September (14 day) \|\| Customization: Limiting number of units
		+	\|-
		+	\| 5 September - 14 September (10 days) \|\| Customization: Adding general customization features
		+	\|-
		+	\| 15 September - 23 September (9 days) \|\| Testing all the features and preparing for final evaluation
		+	\|-
		+	\| After SOC (PLAN) \|\| Continue working for Wesnoth
		+	\|}

	===Include as much technical detail about your implementation as you can===		===Include as much technical detail about your implementation as you can===

@@ Line 172: / Line 172: @@
 ===Did you select a project from our list? If that is the case, what project did you select? What do you want to especially concentrate on?===
 ===If you have invented your own project, please describe the project and the scope.===
@@ Line 177: / Line 179: @@
 ===Why did you choose this project?===
@@ Line 186: / Line 189: @@
 ===What do you expect to gain from this project?===
-Working at a project like Wesnoth will provide invaluable experience. Working at this will also expand my practical knowledge of AI and algorithms. Also, I’m sure that this Summer of Code will prepare me for working in the future for open-source organisations and programs. (I always felt that I wanted to work for an open-source project, but lacked the guidance and a clear goal)
+Working at a project like Wesnoth will provide invaluable experience. It will also expand my practical knowledge of AI and algorithms and will help me better understand the LUA programming language. Moreover, I’m sure that this Summer of Code will prepare me for working in the future for open-source organisations and programs. (I always felt that I wanted to work for an open-source project, but lacked guidance or a clear goal).
 ===What would make you stay in the Wesnoth community after the conclusion of SOC?===

@@ Line 8: / Line 8: @@
 <h4>Dragos Ristache: Refactor the recruitment algorithm </h4>
+I propose to work on the "Refactor the recruiting algorithm" project. The new implemented algorithm should be very customizable from LUA (this will be extremely useful to help campaign creation). The new recruiting algorithm should also be capable of doing the listed features in the project description.
 =IRC=
@@ Line 14: / Line 14: @@
 =Project=