SummerOfCodeProposal Sparksteel - Revision history

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

2013-03-21T00:08:57Z

Hide historical references to Subversion from the wiki search function

Ivanovic: added category SoC

2009-04-03T21:58:14Z

added category SoC

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T22:48:23Z

‎PROJECT TIMELINE

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T22:47:09Z

‎PROJECT TIMELINE

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T22:40:52Z

‎PROJECT TIMELINE

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T22:25:31Z

‎PROJECT TIMELINE

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T22:07:04Z

‎PROJECT TIMELINE

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T22:05:56Z

‎PROJECT TIMELINE

Sparksteel: /* ANSWERS TO QUESTIONS */

2009-04-02T21:36:15Z

‎ANSWERS TO QUESTIONS

Sparksteel: /* PROJECT TIMELINE */

2009-04-02T21:32:49Z

‎PROJECT TIMELINE

@@ Line 354: / Line 354: @@
 Year 2, Undergraduate
-'''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.'''
+'''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.'''
 None yet..
@@ Line 469: / Line 469: @@
 '''5.1) Are you familiar with any of the following tools or languages?'''
-     * Subversion (used for all commits),                     yes
+     * Sub&shy;&shy;version (used for all commits),                     yes
      * C++ (language used for all the normal source code)     currently basic knowledge
      * Python (optional, mainly used for tools)               no

← Older revision		Revision as of 21:58, 3 April 2009
Line 498:		Line 498:
	==COMMENTS==		==COMMENTS==
	(please put any questions/comments regarding my proposal under this section..)		(please put any questions/comments regarding my proposal under this section..)
		+
		+
		+	[[Category:Summer of Code]]

@@ Line 324: / Line 324: @@
 '''Note about testing'''
-I have a feeling that activities such as extensive unit testing etc. will be unlikely to be particularly useful in the context of this particular project, as it will be both handled by just 1 main programmer (me) and also will concentrate on a relatively small number of functionalities.  However, the more abstract and difficult 'integration testing' bit (ie. testing the behavior/effectiveness of my AI under actual game conditions) will probably be both far more important/time-consuming.  This is why I have added liberal sprinkles of 'spare' time allowance in... in order to ensure on-schedule delivery at the end of the summer.
+I have a feeling that activities such as extensive unit testing etc. will be unlikely to be particularly useful in the context of this particular project, as it will be both handled by just 1 main programmer (me) and also will concentrate on a relatively small number of functionalities.  However, the more abstract and difficult 'integration testing' bit (ie. testing the behavior/effectiveness of my AI under actual game conditions) will probably be both far more important and time-consuming.  This is why I have added liberal sprinkles of 'spare' time allowance in... in order to ensure on-schedule delivery at the end of the summer.
 ==ANSWERS TO QUESTIONS==

@@ Line 263: / Line 263: @@
 - the final number of actions and parameters implemented for this GSoC is likely to be at least around 7-15 'parameters', of varying complexity, 3 of which have already been outlined above in the 'EXAMPLE OF PROOF OF CONCEPT SECTION'; And at least '6-9' actions, depending on the precise parameters chosen; 'actions' will be spread across the 3 categories ('attack/hold/defend') and cover at least 2 out of the 3 levels of abstraction (probably levels 1 and 2, as level 3 is probably the level which corresponds to many of the current Wesnoth AI actions).
-'''''More detailed breakdown'''''
+'''''More detailed timing breakdown'''''
 days    - for designing suitable questions for both players and developers (though I am less sure about the immediate impact the developer questionnaire will have on the project...  That will depend upon how many people are particularly interested in Wesnoth AI part?),
@@ Line 280: / Line 280: @@
 At the end of this period, the majority of my proof-of-concept AI should be completed - implementing a restricted set of 'actions' and 'parameters' only, and using a restricted scenario, say with only 2-3 different units on each side.
-'''''More detailed breakdown'''''
+'''''More detailed timing breakdown'''''
 Roughly 14 days - to finalize formula for all the 7-15 'parameters'.
@@ Line 294: / Line 294: @@
 weeks or so to both finish off the proof-of-concept implementations and test out the new AI against the current default AI.
-'''''More detailed breakdown'''''
+'''''More detailed timing breakdown'''''
 days  - together with spare days from last section.. finish proof-of-concept implementation.
@@ Line 309: / Line 309: @@
 More comprehensive testing, tidy up code etc.
-'''''More detailed breakdown'''''
+'''''More detailed timing breakdown'''''
 days  - second batch of runs (maybe on a slightly bigger map, depending on how the first batch of tests went)
@@ Line 320: / Line 320: @@
 '''August 17th (end of actual progress on project)'''
 (THE END... almost anyways..)
 ==ANSWERS TO QUESTIONS==

@@ Line 263: / Line 263: @@
 - the final number of actions and parameters implemented for this GSoC is likely to be at least around 7-15 'parameters', of varying complexity, 3 of which have already been outlined above in the 'EXAMPLE OF PROOF OF CONCEPT SECTION'; And at least '6-9' actions, depending on the precise parameters chosen; 'actions' will be spread across the 3 categories ('attack/hold/defend') and cover at least 2 out of the 3 levels of abstraction (probably levels 1 and 2, as level 3 is probably the level which corresponds to many of the current Wesnoth AI actions).
-'''More detailed breakdown'''
+'''''More detailed breakdown'''''
 days    - for designing suitable questions for both players and developers (though I am less sure about the immediate impact the developer questionnaire will have on the project...  That will depend upon how many people are particularly interested in Wesnoth AI part?),
@@ Line 280: / Line 280: @@
 At the end of this period, the majority of my proof-of-concept AI should be completed - implementing a restricted set of 'actions' and 'parameters' only, and using a restricted scenario, say with only 2-3 different units on each side.
-'''More detailed breakdown'''
+Roughly 14 days - to implement all 6-9 'actions'.
-'''July 6th to July 27th'''
+weeks or so to both finish off the proof-of-concept implementations and test out the new AI against the current default AI.
-weeks or so to both finish off the proof-of-concept implementations and test out the new AI against the current default AI.
+days  - time for any bug fixing, correcting etc.
-'''July 28th to August 17th'''
+'''July 28th to August 17th - estimated 3*6 = 18 working days'''
 More comprehensive testing, tidy up code etc.
 '''August 17th (end of actual progress on project)'''
 ==ANSWERS TO QUESTIONS==

@@ Line 250: / Line 250: @@
-'''April 20th to May 22nd (estimated 5*5 = 25 working days - cautious/lower estimate)'''
+'''April 20th to May 22nd - estimated 5*5 = 25 working days - cautious/lower estimate'''
 (I have still exams, coursework etc. during this time..)
@@ Line 261: / Line 261: @@
 - settling on all the small details about the final abstract design for the new AI engine, such as deciding whether to implement indirect 'actions' using queue-order adjustments or not (see 'OVERALL PROJECT OUTLINE' -> 'Notes for the design outlined in Part 2').
-days    - for designing suitable questions for both players and developers,
+- the final number of actions and parameters implemented for this GSoC is likely to be at least around 7-15 'parameters', of varying complexity, 3 of which have already been outlined above in the 'EXAMPLE OF PROOF OF CONCEPT SECTION'; And at least '6-9' actions, depending on the precise parameters chosen; 'actions' will be spread across the 3 categories ('attack/hold/defend') and cover at least 2 out of the 3 levels of abstraction (probably levels 1 and 2, as level 3 is probably the level which corresponds to many of the current Wesnoth AI actions).
 days    - for compiling results from questionnaires and finalizing general implementation details,
 (both general architecture and 'parameters' to include in GSoC project).

← Older revision		Revision as of 21:36, 2 April 2009
Line 279:		Line 279:

	==ANSWERS TO QUESTIONS==		==ANSWERS TO QUESTIONS==
−
−	~~(done)~~

	===Basics===		===Basics===

← Older revision		Revision as of 21:32, 2 April 2009
Line 263:		Line 263:
	'''May 23rd to July 5th(official start date for coding)'''		'''May 23rd to July 5th(official start date for coding)'''

−	During this period, the ~~implementation for~~ my proof-of-concept AI should have been ~~largely~~ completed - implementing a restricted set of 'actions' and 'parameters' only, and using a restricted scenario, say with only 3-4 different units on each side.	+	During this period, the majority of my proof-of-concept AI should have been completed - implementing a restricted set of 'actions' and 'parameters' only, and using a restricted scenario, say with only 2-3 different units on each side.