SoC 2012 HappyKsuh AI Recruitment - Revision history

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T03:20:05Z

Hide historical references to Subversion from the wiki search function

HappyKsuh at 20:00, 5 April 2012

2012-04-05T20:00:35Z

HappyKsuh at 19:59, 5 April 2012

2012-04-05T19:59:37Z

HappyKsuh: /* Questionnaire */

2012-04-05T19:58:32Z

‎Questionnaire

HappyKsuh: /* Timeline */

2012-04-05T19:55:05Z

‎Timeline

HappyKsuh: /* Description */

2012-04-05T19:54:19Z

‎Description

HappyKsuh: /* Timeline */

2012-04-05T19:41:35Z

‎Timeline

HappyKsuh: /* Timeline */

2012-04-05T19:37:37Z

‎Timeline

HappyKsuh: /* Details */

2012-04-05T19:27:55Z

‎Details

HappyKsuh: /* Details */

2012-04-05T19:17:45Z

‎Details

@@ Line 184: / Line 184: @@
 I'm familiar with Java and C++ and ususally use MS VS (Windows) or Eclipse (Linux) as working IDE, or sometimes gedit if the project is simple and small.
-;Subversion
+;Sub&shy;&shy;version
 :yes

@@ Line 184: / Line 184: @@
 I'm familiar with Java and C++ and ususally use MS VS (Windows) or Eclipse (Linux) as working IDE, or sometimes gedit if the project is simple and small.
-;Subversion (used for all commits)
+;Subversion
 :yes
-;C++ (language used for all the normal source code)
+;C++
 :yes
-;STL, Boost, Sdl (C++ libraries used by Wesnoth)
+;STL, Boost, Sdl
 :familiar with STL and have a little experience in Boost
-;Python (optional, mainly used for tools)
+;Python
 :no
-;build environments (eg cmake/scons)
+;build environments
 :yes
-;WML (the wesnoth specific scenario language)
+;WML
 :no
-;Lua (used in combination with WML to create scenarios)
+;Lua
 :no

@@ Line 182: / Line 182: @@
 <b><i>5) Practical considerations</i></b>
-I'm familiar with Java and C++ and ususally use MS VS or Eclipse as working IDE, or sometimes gedit if the project is simple and small.
+I'm familiar with Java and C++ and ususally use MS VS (Windows) or Eclipse (Linux) as working IDE, or sometimes gedit if the project is simple and small.
 ;Subversion (used for all commits)

@@ Line 184: / Line 184: @@
 I'm familiar with Java and C++ and ususally use MS VS or Eclipse as working IDE, or sometimes gedit if the project is simple and small.
-* Subversion (used for all commits)
+;Subversion (used for all commits)
-   yes
+:yes
-* C++ (language used for all the normal source code)
+;C++ (language used for all the normal source code)
-   yes
+:yes
-* STL, Boost, Sdl (C++ libraries used by Wesnoth)
+;STL, Boost, Sdl (C++ libraries used by Wesnoth)
-   familiar with STL and have a little experience in Boost
+:familiar with STL and have a little experience in Boost
-* Python (optional, mainly used for tools)
+;Python (optional, mainly used for tools)
-   no
+:no
-* build environments (eg cmake/scons)
+;build environments (eg cmake/scons)
-   yes
+:yes
-* WML (the wesnoth specific scenario language)
+;WML (the wesnoth specific scenario language)
-   no
+:no
-* Lua (used in combination with WML to create scenarios)
+;Lua (used in combination with WML to create scenarios)
-   no
+:no

@@ Line 96: / Line 96: @@
+|
 |-
-| 21.05 - 03.06<br>(hard studies period)
+| 21.05 - 03.06<br>(hard-studying period)
 | Develop task 3.
+|

@@ Line 10: / Line 10: @@
 <h4>Kseniya Buraya - Refactoring AI Recruitment</h4>
-Though it is already mentioned in the ideas list, I'll repeat:
+The project is to improve current AI recruiting system. I will develop and implement these options:
+* To recruit with a lot of leaders instead of one
-I will have to change AI Recruitment Algorithm as it will be able to:
+* To consider the terrain type where the possible battle will be
- - support recruiting with multiple leaders
+* To consider enemy and allied units together as to create great counter-unit mix
- - support per-leader recruit/recall lists
+* To provide the scenario editor an option to choose recruiting strategy ("defensive", "agressive", etc.) and to set limits on particular units
 =Details=

@@ Line 106: / Line 106: @@
+|
 |-
-| 21.05 - 03.06 (last two weeks of studies)
+| 21.05 - 03.06<br>(hard studies period)
 | Develop task 3.
+|
@@ Line 114: / Line 114: @@
+|
 |-
-| 11.06 - 01.07 (exams period)
+| 11.06 - 01.07<br>(exams period)
 | Develop and implement upper limitation on recruiting every unit.
+|
@@ Line 122: / Line 122: @@
+|
 |-
-| 09.07 - 15.07 (mid-term deadline)
+| 09.07 - 15.07<br>(mid-term deadline)
 | Based on prototype implement working realisation of counter-recruiting strategy. Have tasks 0-4 cleared.
+|

← Older revision		Revision as of 19:37, 5 April 2012
Line 85:		Line 85:

	=Timeline=		=Timeline=
		+	{\| border=1
		+	! Time
		+	! Task
		+	! Status
		+	\|-
		+	\| 01.04 - 20.04
		+	\| Get familiar with the code in /AI/default/. Develop and implement tasks 0 and 1 as preliminary example of my coding abilities.
		+	\|
		+	\|-
		+	\| 24.04 - 06.05
		+	\| Fix bugs and make improvements to tasks 0 and 1 if necessary. Develop analyze_potential_recruit_terrain() function and get familiar with necessary code.
		+	\|
		+	\|-
		+	\| 07.05 - 13.05
		+	\| Implement and test analyze_potential_recruit_terrain() function.
		+	\|
		+	\|-
		+	\| 14.05 - 20.05
		+	\| Get familiar with code in /AI/ and / like game., unit. etc. Get tasks 0-2 totally completed.
		+	\|
		+	\|-
		+	\| 21.05 - 03.06 (last two weeks of studies)
		+	\| Develop task 3.
		+	\|
		+	\|-
		+	\| 04.06 - 10.06
		+	\| Make recruits to know their future goals. Testing and bugfixing.
		+	\|
		+	\|-
		+	\| 11.06 - 01.07 (exams period)
		+	\| Develop and implement upper limitation on recruiting every unit.
		+	\|
		+	\|-
		+	\| 02.07 - 08.07
		+	\| Think about counter-recruiting strategy, implement and test the prototype.
		+	\|
		+	\|-
		+	\| 09.07 - 15.07 (mid-term deadline)
		+	\| Based on prototype implement working realisation of counter-recruiting strategy. Have tasks 0-4 cleared.
		+	\|
		+	\|-
		+	\| 16.07 - 22.07
		+	\| Think of and document necessary styles of recruiting. Get a clear view how to integrate those styles into the recruiting process.
		+	\|
		+	\|-
		+	\| 23.07 - 29.07
		+	\| Implement the system of styles.
		+	\|
		+	\|-
		+	\| 30.07 - 05.08
		+	\| Develop and implement the "wait for" strategy. Looks simple in case of tasks 5-6 done.
		+	\|
		+	\|-
		+	\| 06.08 - 12.08
		+	\| Make necessary bugfixing and work on documentation.
		+	\|
		+	\|}

	=IRC=		=IRC=

@@ Line 73: / Line 73: @@
 | 6
 | Different recruiting styles
-| Implement different recruiting styles (i.e. "defensive", "aggressive", "conserve resourses") and integrate it into the current recruiting system.
+| Develop and implement different recruiting styles (i.e. "defensive", "aggressive", "conserve resourses") and integrate it into the current recruiting system.
 | none
+|

@@ Line 54: / Line 54: @@
 |-
 | 3
-| Add goals to recruits
+| Goals of potential recruits
 | Find a way to store information about the goals of every recruit. Probably to store it in unit::role_ later.
 | none
@@ Line 60: / Line 60: @@
 |-
 | 4
-| Add limitation to every type of unit
+| Limitation of recruitment
 | Find a way to store information about the uppper limit of each type of units.
 | none
@@ Line 66: / Line 66: @@
 |-
 | 5
-| Make sensible counter-recruiting strategy
+| Sensible counter-recruiting strategy
 | Add function similar to <i>get_combat_score</i>, that will calculate scores based not only on enemy units but on own units too. Probably it'll take a lot of time to develop and test.
 | <b>3</b>
@@ Line 73: / Line 73: @@
 | 6
 | Different recruiting styles
-| Find a way to store information about current recruiting style (i.e. "defensive", "aggressive", "conserve resourses") and integrate it into current recruiting system.
+| Implement different recruiting styles (i.e. "defensive", "aggressive", "conserve resourses") and integrate it into the current recruiting system.
 | none
+|
 |}