SummerOfCodeProposal corn - Revision history

Esr: Hide historical instance of "Subversion" from mediawiki search to avoid false positives.

2013-03-21T00:17:35Z

Hide historical instance of "Subversion" from mediawiki search to avoid false positives.

Cornmander: /* Goals */

2009-08-17T20:23:41Z

‎Goals

Cornmander: /* Goals */

2009-08-17T20:20:33Z

‎Goals

Cornmander: /* Goals */

2009-07-03T16:31:51Z

‎Goals

Cornmander: /* Goals */

2009-07-03T16:30:06Z

‎Goals

Cornmander: /* Technical Details */

2009-04-16T22:56:17Z

‎Technical Details

Cornmander: /* Goals */

2009-04-16T22:50:59Z

‎Goals

Cornmander at 22:47, 16 April 2009

2009-04-16T22:47:03Z

Cornmander: /* Goals */

2009-04-14T15:33:00Z

‎Goals

Cornmander at 15:31, 14 April 2009

2009-04-14T15:31:51Z

@@ Line 43: / Line 43: @@
 * vi(m)
 * linux
-* subversion
+* sub&shy;&shy;version
 * gcc
 * grep, sed, awk, other standard shell hacker tools :)
@@ Line 188: / Line 188: @@
 ==== Familiarity with Tools ====
-* Subversion - I know how to use svn, and I run it on my own server as well.
+* Sub&shy;&shy;version - I know how to use s&shy;&shy;v&shy;&shy;n, and I run it on my own server as well.
 * C++ - I know C and Java very well, but I don't know C++. I think I can learn it over the course of a week or two, however.
 * Python - I know python very well.
@@ Line 194: / Line 194: @@
 ==== Development Tools ====
-I use vi, xterm, svn, and GDB. I dislike working in IDEs because of the overhead and effort of getting your project set up properly in them.
+I use vi, xterm, s&shy;&shy;v&shy;&shy;n, and GDB. I dislike working in IDEs because of the overhead and effort of getting your project set up properly in them.
 ==== Fluent Programming Languages ====

@@ Line 130: / Line 130: @@
 | Add new stat windows to the website
 | Created a recruited units window, a dead units window, and a unit by level breakdown in addition to improving the things currently in the prototype. Add date ranges to all the charts on the site.
-| Added date range selection to all the charts. The table in the database with the unit information still isn't being used. Adding new graphs is quick and easy right now, but only piecharts and linegraphs are supported.
+| Incomplete. Added a killmap statistics page but I haven't added any more pie charts or line graphs. Bar graphs are still unsupported.
 |-
 | <p style="color:red">MUST</p>
@@ Line 176: / Line 176: @@
 |-
 |}
 ==== What I expect to get from this Project ====

@@ Line 125: / Line 125: @@
 | Basic stats.wesnoth.org website
 | Create a better formatted version of my prototype at http://cornmander.com:9090
-| Completely rewrote the code for generating graph pages. Everything is driven by a database and new graphs take less than a minute to create. I still need to create a page for adding new graphs.
+| Completely rewrote the code for generating graph pages. Everything is driven by a database and new graphs take less than a minute to create. I still need to create a page for adding new graphs. <- (edit 8/17/09): still haven't thought of new pie/line/bar graphs, but I have two ideas for hexmaps (aka killmaps) that would be useful: most captured villages, most traveled tiles.
 |-
 | <p style="color:red">MUST</p>
@@ Line 140: / Line 140: @@
 | Remove outlier data
 | Give statistics for the median 80%, leaving out the outlying 10% below and 10% above.
-| Not implemented yet. I need to think about how to do this.
+| Still not done. A discussion that came up on IRC was to allow developers to set a wml variable designating their campaign as beta - not to be tracked. This should get rid of some outrageous values (-9000 gold at start turn, for example). A statistical approach to getting rid of outliers still needs to be created, however.
 |-
 | <p style="color:red">MUST</p>
@@ Line 150: / Line 150: @@
 | Kill maps
 | Create a section of stats that gives a breakdown by tile on a scenario of the units killed on that tile. The presentation will be a jscript-enhanced map where a user can hover over a tile and see a percentage breakdown of the units killed on that tile. In addition to website coding, significant changes must be made to stat collection.
-| Not done yet. I will start on this after I finish linegraphs, the addview page, and login support.
+| Done. Added the code to the wesnoth client to send gzipped maps and kill event data. Also added code for a '--screenshot' parameter that allows a server without X11 to generate map screenshots using the wesnoth client. I implemented an extremely tiny WML parser to parse upload logs on my server, wrote a script to generate google maps tilesets from map screenshots (generated on server), and wrote a frontend that has filterable killmaps.
 |-
 | <p style="color:red">MUST</p>
 | CSS and Design
 | Integrate the look of the stats page with the rest of wesnoth.org . Make the website user-friendly
-| Not done yet. All the site functionality should be laid down before I start skinning it.
+| Done. It was pretty simple - I just named my div tags according to the wesnoth.org site and imported the stylesheet.
 |-
 | <p style="color:red">MUST</p>
 | Email subscription to charts
 | Create a login system so that users can subscribe to particular charts, and receive daily emails for comparison. This will be useful for basic AI regression testing, ex: run 10 different campaigns with an AI during a particular day and compare with the charts of the previous day
-| Not done yet. The login support needs to be done first. crab has a sql database with his AI results that I am going to integrate into my database when I get a chance - this will give me an opportunity to test out this feature.
+| Not done.
 |-
 | <p style="color:green">GOOD</p>
 | Geographic data
-| The server already gets data on user IPs by accepting logs from them. Create a display page where a map is shown colored in according to how many users play from each country.
+| Not done.
 |-
 | <p style="color:green">GOOD</p>
 | Get MP data
-| Get the same data on scenario completion, platform breakdown, win/loss/quit information from MP matches.
+| Partially complete. MP logging is enabled for AI vs AI matches but the log format doesn't have particularly useful stats. I still need to add more log data so that useful graphs can be made (faction win percentage, average end turn).
 |-
 | <p style="color:green">GOOD</p>

@@ Line 155: / Line 155: @@
 | CSS and Design
 | Integrate the look of the stats page with the rest of wesnoth.org . Make the website user-friendly
 |-
 | <p style="color:red">MUST</p>
 | Email subscription to charts
 | Create a login system so that users can subscribe to particular charts, and receive daily emails for comparison. This will be useful for basic AI regression testing, ex: run 10 different campaigns with an AI during a particular day and compare with the charts of the previous day
-| Not done yet. All the site functionality should be laid down before I start skinning it.
+| Not done yet. The login support needs to be done first. crab has a sql database with his AI results that I am going to integrate into my database when I get a chance - this will give me an opportunity to test out this feature.
 |-
 | <p style="color:green">GOOD</p>

@@ Line 120: / Line 120: @@
 ! SUBPROJECT
 ! RESULT
 |-
 | <p style="color:red">MUST</p>
 | Basic stats.wesnoth.org website
 | Create a better formatted version of my prototype at http://cornmander.com:9090
 |-
 | <p style="color:red">MUST</p>
 | Add new stat windows to the website
 | Created a recruited units window, a dead units window, and a unit by level breakdown in addition to improving the things currently in the prototype. Add date ranges to all the charts on the site.
 |-
 | <p style="color:red">MUST</p>
 | Improve filter behavior
 | Make the filters automatically remove choices with 0 entries based on currently selected filters
 |-
 | <p style="color:red">MUST</p>
 | Remove outlier data
 | Give statistics for the median 80%, leaving out the outlying 10% below and 10% above.
 |-
 | <p style="color:red">MUST</p>
 | Add scalability
 | Make the statistics presentation scalable to the millions of rows currently on stats.wesnoth.org. I plan to do this by creating a 10k random-row table subset of the data in a nightly cronjob and using this by default for all queries. If a query gives under CONSTANT_NUMBER results, the site will use the main database instead.
 |-
 | <p style="color:red">MUST</p>
 | Kill maps
 | Create a section of stats that gives a breakdown by tile on a scenario of the units killed on that tile. The presentation will be a jscript-enhanced map where a user can hover over a tile and see a percentage breakdown of the units killed on that tile. In addition to website coding, significant changes must be made to stat collection.
 |-
 | <p style="color:red">MUST</p>
@@ Line 152: / Line 159: @@
 | Email subscription to charts
 | Create a login system so that users can subscribe to particular charts, and receive daily emails for comparison. This will be useful for basic AI regression testing, ex: run 10 different campaigns with an AI during a particular day and compare with the charts of the previous day
 |-
 | <p style="color:green">GOOD</p>
@@ Line 164: / Line 172: @@
 | GUI or scripting interface for hooking in new stat pages
 | Create an interface for looking at new stats. User will have a choice of several graph types and what data sets to use for x and y axes.
 |-
 |}

← Older revision		Revision as of 22:56, 16 April 2009
Line 108:		Line 108:

	==== Technical Details ====		==== Technical Details ====
		+
		+	Frontend will be written in python with the turbogears application platform (for the nice templating language support). Databases for stats data and any user/configuration settings for the frontend will be in MySQL. Charting will be done using Google Charting API.
		+
		+	Changes will be made to the wesnoth client so that it keeps an array or a map where a list of dead units is kept for each tile. This data will be sent along with stats so that killgraphs can be generated. A program will also be written to take wesnoth maps, generate PNG files of them (if there isn't already such functionality) and color in each tile according to how many units were killed on it. This will be generated nightly and used for the killgraphs.
		+
		+	The stats interface will scale up to millions of rows by operating on a randomly taken subset of the data grabbed nightly. If the subset turns out not to have data for a particular set of filters, the interface will revert back to the bigger database.

	== Goals ==		== Goals ==

@@ Line 139: / Line 139: @@
 * Mailing reports will be handled by a cronjob. I plan on having this project be run on a Linux, Apache, MySQL, Python stack.
 ==== What I expect to get from this Project ====
@@ Line 169: / Line 193: @@
 ==== Hours of Availability ====
-Until the end of June, I am available from 6 PM EST (22:00 UTC) to 3 AM EST (7:00 UTC). During the summer, depending on whether or not I get a job, I will either be available during the entire day of 9 PM EST (1:00 UTC) to 5 PM EST (21:00 UTC) or still only from 6 PM EST (22:00 UTC) to 3 AM EST (7:00 UTC). I expect to put in full work days of 8 hours on this project.
+Until the end of June, I am available from 6 PM EST (22:00 UTC) to 3 AM EST (7:00 UTC). I will either be available during the entire day of 9 PM EST (1:00 UTC) to 10 PM EST (21:00 UTC). I expect to put in full work days of 8 hours on this project.
 ==== Phone / Internet Phone Conversations ====