SoC2014 Zubin AI - Revision history

Zubinkapadia: /* Questionnaire */

2014-03-21T15:13:27Z

‎Questionnaire

Zubinkapadia: /* Questionnaire */

2014-03-21T15:11:44Z

‎Questionnaire

Zubinkapadia: /* ATTENTION */

2014-03-21T14:16:49Z

‎ATTENTION

Zubinkapadia: /* Description */

2014-03-21T14:14:34Z

‎Description

Zubinkapadia: /* Questionnaire */

2014-03-21T14:11:36Z

‎Questionnaire

Zubinkapadia: /* Questionnaire */

2014-03-21T14:10:23Z

‎Questionnaire

Zubinkapadia: /* Questionnaire */

2014-03-21T14:06:14Z

‎Questionnaire

Zubinkapadia: /* Questionnaire */

2014-03-21T14:05:47Z

‎Questionnaire

Show changes

Zubinkapadia: /* Questionnaire */

2014-03-21T13:59:41Z

‎Questionnaire

Zubinkapadia: /* Questionnaire */

2014-03-21T13:57:55Z

‎Questionnaire

@@ Line 208: / Line 208: @@
 Also positioning your units is very important. Positioning of units is different for aggressive and defensive approaches. To plan out the positioning we will use threat map. A threat map is a 2D array which describes the level of danger on every position. While building a threat map, the positioning of the enemy units, type of units and other factors are taken into account.
-.6) What do you expect to gain from this project?
+'''4.6) What do you expect to gain from this project?'''
 *	Gain experience in game development.

@@ Line 146: / Line 146: @@
 Pre coding phase
-Week 1- 3
+March 22- May 18 (4 weeks)
-*Reading the code base of Wesnoth and understanding the flow of application code thoroughly.
+*Reading the codebase of Wesnoth and understanding the flow of application code thoroughly.
 *Discussion with mentor and the community regarding the project to take valuable feedback.
@@ Line 161: / Line 161: @@
 Coding phase
-Week 4 -5
+May 19 - June 9 (3 weeks)
 *Implementing prototypes
@@ Line 170: / Line 170: @@
-Week 6-10
+June 10 – June 27 (2 weeks)
 *Working on implementation of the main code for the AI
-*Implementing threat maps and decision trees.
+*Implementing threat maps.
-Pencil down PHASE
+*Mid-term evaluation
-Week 11-12
+June 28 - august 5 (6 weeks)
 *Cleaning the code

@@ Line 3: / Line 3: @@
 ==ATTENTION==
-Incomplete
+This page will be continuously modified and updated.
 ==Description==

← Older revision		Revision as of 14:14, 21 March 2014
Line 6:		Line 6:

	==Description==		==Description==
		+	<h4>Zubin Kapaida: Improve AI by implementing global attack/retreat decision</h4>
	I believe that the key to making a good AI bot is to keep your ideas clear and simple. One must evaluate the gravity of the situation using the given parameters and accordingly act offensively or defensively.		I believe that the key to making a good AI bot is to keep your ideas clear and simple. One must evaluate the gravity of the situation using the given parameters and accordingly act offensively or defensively.

@@ Line 53: / Line 53: @@
-'''2) Experience'''
+<h4>'''2) Experience'''</h4>
 '''2.1) What programs/software have you worked on before?'''
@@ Line 98: / Line 98: @@
-'''3) Communication skills'''
+<h4>'''3) Communication skills'''</h4>
 '''3.1) Though most of our developers are not native English speakers, English is the project's working language. Describe your fluency level in written English.'''
@@ Line 129: / Line 129: @@
-'''4) Project'''
+<h4>'''4) Project'''</h4>
 '''4.1) 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?'''
@@ Line 208: / Line 208: @@
-'''5) Practical considerations'''
+<h4>'''5) Practical considerations'''</h4>
 '''5.1) Are you familiar with any of the following tools or languages?'''

@@ Line 22: / Line 22: @@
 ==Questionnaire==
-'''1) Basics'''
+<h4>'''1) Basics'''</h4>
 '''1.1) Write a small introduction to yourself.'''

← Older revision		Revision as of 14:06, 21 March 2014
Line 53:		Line 53:


−	2) Experience	+	'''2) Experience'''

	'''2.1) What programs/software have you worked on before?'''		'''2.1) What programs/software have you worked on before?'''

@@ Line 147: / Line 147: @@
 Week 1- 3
-Reading the code base of Wesnoth and understanding the flow of application code thoroughly.
+*Reading the code base of Wesnoth and understanding the flow of application code thoroughly.
-Discussion with mentor and the community regarding the project to take valuable feedback.
+*Discussion with mentor and the community regarding the project to take valuable feedback.
-Thoroughly plan out the decision tree and threat map structures.
+*Thoroughly plan out the decision tree and threat map structures.
-Design algorithm into detail
+*Design algorithm into detail
-Learn useful interfaces
+*Learn useful interfaces
@@ Line 162: / Line 162: @@
 Week 4 -5
-Implementing prototypes
+*Implementing prototypes
-Testing prototypes
+*Testing prototypes
-Refining prototypes
+*Refining prototypes
 Week 6-10
-Working on implementation of the main code for the AI
+*Working on implementation of the main code for the AI
-Implementing threat maps and decision trees.
+*Implementing threat maps and decision trees.
 Pencil down PHASE
@@ Line 180: / Line 180: @@
 Week 11-12
-Cleaning the code
+*Cleaning the code
-Fixing the bugs
+*Fixing the bugs
-Documentation
+*Documentation
@@ Line 197: / Line 197: @@
 .6) What do you expect to gain from this project?
-•	Gain experience in game development.
+*	Gain experience in game development.
-•	Achieve a better understanding of Artificial Intelligence.
+*	Achieve a better understanding of Artificial Intelligence.
-•	Gain experience of working with an open source community.
+*	Gain experience of working with an open source community.
 .7) What would make you stay in the Wesnoth community after the conclusion of SOC?
@@ Line 212: / Line 212: @@
 .1) Are you familiar with any of the following tools or languages?
-	Git (used for all commits)  -   Yes
+*	Git (used for all commits)  -   Yes
-	C++ (language used for all the normal source code)  -  Yes
+*	C++ (language used for all the normal source code)  -  Yes
-	STL, Boost, Sdl (C++ libraries used by Wesnoth)  -  No
+*	STL, Boost, Sdl (C++ libraries used by Wesnoth)  -  No
-	Python (optional, mainly used for tools)  -  Yes, I have also developed a game in Panda3D
+*	Python (optional, mainly used for tools)  -  Yes, I have also developed a game in Panda3D
 using python.
-	build environments (eg cmake/scons)  - Yes
+*	build environments (eg cmake/scons)  - Yes
-	WML (the wesnoth specific scenario language)  -  No
+*	WML (the wesnoth specific scenario language)  -  No
-	Lua (used in combination with WML to create scenarios)  -  Yes, I have developed an android
+*	Lua (used in combination with WML to create scenarios)  -  Yes, I have developed an android
 game in Corona SDK using lua