User:PJ - Revision history

Egallager: link/heading cleanup

2023-05-05T20:04:43Z

link/heading cleanup

PJ at 23:52, 2 May 2013

2013-05-02T23:52:12Z

PJ at 23:50, 2 May 2013

2013-05-02T23:50:05Z

PJ at 23:44, 2 May 2013

2013-05-02T23:44:14Z

PJ at 20:25, 21 April 2013

2013-04-21T20:25:41Z

PJ at 21:21, 18 April 2013

2013-04-18T21:21:31Z

PJ at 21:20, 18 April 2013

2013-04-18T21:20:53Z

Show changes

PJ: Created page with '{{SoC2013Student}} Category:SoC_Ideas_Your_Own_Ideas2013 =Description=

PJ - Proposal Draft

TODO: Write a small (1-4 sentences) description of your proposal here. …'

2013-04-17T23:34:48Z

Created page with '{{SoC2013Student}} Category:SoC_Ideas_Your_Own_Ideas2013 =Description= <h4>PJ - Proposal Draft </h4> TODO: Write a small (1-4 sentences) description of your proposal here. …'

New page

{{SoC2013Student}}
[[Category:SoC_Ideas_Your_Own_Ideas2013]]

=Description=
<h4>PJ - Proposal Draft </h4>
TODO: Write a small (1-4 sentences) description of your proposal here.

=Specifics=
TODO: Add more first-level sections to detail your proposal

=IRC=

pjte

=Questionnaire=
TODO: fill out the questionnaire, on your copy of this page. Question are here : [[SoC_Information_for_Google#Does your organization have an application template you would like to see students use?]]

@@ Line 1: / Line 1: @@
 {{SoC2013Student}}
-[[Category:SoC_Ideas_Your_Own_Ideas2013]]
+==Description==
 <h4>PJ - Proposal </h4>
@@ Line 9: / Line 7: @@
 The current recruitment system is too weak for the AI to properly recruit units. AI is prone to not recruiting the best units for terrain and is also weak against counter recruitment. This problems can be fixed through a code overhaul in both the C++ section of recruitment and the Lua sections.
+==Specifics==
 <ol>
 <li><b>Support recruiting with multiple leaders.</b></li>
@@ Line 26: / Line 23: @@
 </ol>
-=IRC=
+==IRC==
 pjte
-=Questionnaire=
+==Questionnaire==
 <h4>1) Basics</h4>
 <b>1.1) Write a small introduction to yourself.</b>
@@ Line 60: / Line 57: @@
 A possible week exists at the beginning of June where I would not have access to my home computer. A portable device could be used for some out of state coding.
 <h4>2) Experience</h4>
@@ Line 114: / Line 110: @@
 I have not contributed any patches to Wesnoth, but I have looked extensively through the Wesnoth source code. I have tried some basic edits, and have tried playing around with the AI.
 <h4>3) Communication skills</h4>
@@ Line 145: / Line 140: @@
 I would like to discuss some about the project and determine what exactly needs to be done. Then, I would prioritize the objectives and plan the code. I would code and look for feedback on code as soon as a major difference was seen in the gameplay.
 <h4>4) Project</h4>
@@ Line 191: / Line 185: @@
 <b>4.5) Include as much technical detail about your implementation as you can</b>
+Please see the [[User:PJ#Specifics|Specifics]] section for basic implementation ideas.
 <b>4.6) What do you expect to gain from this project?</b>
@@ Line 202: / Line 194: @@
 The game will never be fully complete, in the sense that improvements and updates will always be made so long as the community remains active. As long as bugs still exist in the code, and as long as the AI has errors to iron out, the project will remain interesting to me. The project becomes partly mine, since I contributed to the code, and I care about its outcome. Letting the project die due to lack of development is sad, and I would be unhappy to see something that I had worked on end up like this.
 <h4>5) Practical considerations</h4>
@@ Line 234: / Line 225: @@
 	I am certainly open to talking to anyone who has questions.

@@ Line 197: / Line 197: @@
 <b>4.6) What do you expect to gain from this project?</b>
+I expect to gain knowledge of both the open source community and the game development community. I hope to use these skills in the future.
 <b>4.7) What would make you stay in the Wesnoth community after the conclusion of SOC?</b>

← Older revision		Revision as of 23:50, 2 May 2013
Line 191:		Line 191:
	<b>4.5) Include as much technical detail about your implementation as you can</b>		<b>4.5) Include as much technical detail about your implementation as you can</b>

−	~~Please see the <a href="url">Specifics</a> section for basic implementation ideas.~~

		+	Please see the [http://wiki.wesnoth.org/User:PJ#Specifics Specifics] section for basic implementation ideas.

@@ Line 2: / Line 2: @@
 [[Category:SoC_Ideas_Your_Own_Ideas2013]]
-=WIP=
+=Description=
-=Description=
+AI Recruitment Algorithms
 =Specifics=
-TODO: Add more first-level sections to detail your proposal
+<ol>
 =IRC=
@@ Line 96: / Line 109: @@
 <b>2.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.</b>
-<b>ANSWER THIS!!!!!!!</b>
+I have played a few games of Wesnoth, enough to see how the AI works.
 .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 GSoC. If you have gained commit access to our repository (during the evaluation period or earlier) please state so.
-<b>ANSWER THIS TOO!!!!!</b>
+I have not contributed any patches to Wesnoth, but I have looked extensively through the Wesnoth source code. I have tried some basic edits, and have tried playing around with the AI.
@@ Line 138: / Line 151: @@
 <b>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?</b>
+AI: Refactor recruitment algorithm. I specifically would like to concentrate on terrain analysis and counter-recruitment strategy.
 <b>4.2) If you have invented your own project, please describe the project and the scope.</b>
@@ Line 146: / Line 159: @@
 <b>4.3) Why did you choose this project?</b>
-<b>4.4) 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".</b>
+<li><b>June 19th</b></li>
 <b>4.5) Include as much technical detail about your implementation as you can</b>

@@ Line 42: / Line 42: @@
 <b>1.6) What country are you from, at what time are you most likely to be able to join IRC?</b>
-	I am from the United States, and can most likely join the IRC channel around 3:00 GMT.
+	I am from the United States, and can most likely join the IRC channel around 3:00 MST.
 <b>1.7) Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.</b>