Brinkman 1-20-12 Report

1. What did you plan to do this week?
- Write Android sections of GG final report
- Write Table Tilt paper

2. What did you do?
- Wrote Android sections of GG final report
- Wrote short Table Tilt paper for FDG Experimental Game entry
- Helped Veronica prepare SPARCs materials and create pre/post tests

3. Problems encountered?
- Finding a LaTeX editor that worked well in Windows

4. What do you plan to do next week?
- Extend Android functionality to include "extras" that were cut out of last semester's schedule
- More Android testing

5. How many hours did you work?
~18

Katie Doran Weekly Report 1/13 - 1/19

1. What did you plan to do this week?

- Submit ITiCSE paper (deadline early on 1/14)

- Submit abstract to grad research fair (deadline 1/18)

- Identify target conferences for this semester

- Assist in Global Game Jam preparations

2. What did you do?

- Finished and submitted paper to ITiCSE on Citizen Schools work

- Submitted an abstract for a poster to the Grad Research Fair (also on outreach)

- Identified several target publications (see #6)

- Have finalized nearly all details for GGJ, secured funding for advertising (unfortunately not for food, but may already have another source for that), contacted Journalism professors about students to assist in interviews for a paper on GGJ & Creativity

3. Problems encountered?

- Format of data from Citizen Schools made it impossible for me to calculate the statistical significance of my results, weakening the impact of the ITiCSE paper

4. What do you plan to do next week

- Finalize all Citizen Schools lesson plans for this semester of outreach and put them online

- Make plans for a short-paper submission to GAS on our work creating a game-based digital layer for the museum (deadline 2/17)

- Investigate feasibility of a study on learning benefits of Citizen Schools outreach for the instructors

- Global Game Jam event & study

- Citizen Schools WOW! training

- Set up new devices for outreach use

- Contact Mike Kubiak from Citizen Schools data collection office to determine what data I need and, out of that, what I can get (what I received most recently was good, but did not have all the information I would like to capture)

5. How many hours did you work?

~12 hours

6. What publication venues are you targeting and for what papers?

- GAS 2012, short paper (4 pages) - Creation of a Game-Based Digital Layer for a Science Museum (deadline 2/17)

- ICER 2012, discussion paper (6 pages) - Better Understanding through Outreach: learning gains among instructors of computer science outreach (deadline 4/20)

- Meaningful Play 2012, extended abstract (500+ words) - I'd like to submit a paper on OLPC serious games for Haiti, but this depends on me creating such a game before our spring break trip...which I plan to do, but may or may not be successful (deadline 7/16)

- A D.C. somewhere? Maybe ICER?

Antoine Campbell Weekly Report 11-8 / 11-14

1. What was planned?
*Finish Undo System
*Practice for 8 hour startup Web Application Competition

2. What was done?
*Lots of practice for the 8 hour startup competition
*Won the 8 hour startup competition!!!

3. Problems encountered?
*Splitting time up, had to just work on Ninjitsu Sea Pirates this week, only seem to be working with a two man team, which is giving us even more work. Teammates are not following through on assignments.

4. What did you learn this week?
*A little bit of practice goes a long way, presentation and polish also go a long way.

5. What's planned for next week?
*Get back on to Bunny Generals, not that the competition is over, and my birthday is out of the way, can get back to work on it.
*Writing a two essays for the DOE grant. (I should have payed attention in English class, I like numbers)

6. Hours worked.
*Not sure exactly a lot but not on Bunny Generals so not sure what to put, at least 15.

Antoine Campbell Weekly Report 11-1 / 11-7

1. What was planned?
*Mainly Finish the Undo System
*Test for bugs
*Playtesting

2. What was done?
*Developed a system to Undo the actions made by the player after a mistake is made, however it does not function as I want it to so playtesting will tell whether it is helpful or not.
*Found a couple of bugs, fixed the bugs I found, got a couple of unexpected functionality if someone just banged a bunch of keys on the keyboard.
*Only had one person playtest and use the undo system, and depending on the situation it moved the algorithm ahead instead of back, I think I just need to change some values here and there.

3. Problems encountered?
*Undo System no as easy as originally thought
*Need more time competition approaching, working on 3 projects and preparing for a competition

4. What did you learn this week?
*Some interesting debugging techniques, Visual Studio is great

5. What's planned for next week?
*Just to get the Undo System working so I can playtest, the Undo System should be the last bit of feedback that was received about Bunny Generals

6. Hours worked.
*About 14

Amanda's report 11/02-11/06

1. What was planned for this week. Code cleanup. Prepare lecture on DarkWynter’s HUD and Event System for the serious games class.

2. What was done. Both.

3. Problems encountered. None...other than prepping lectures takes bloody forever.

4. Plan for next week. Deliver said lecture on Monday.

5. How many hours worked. 15

Amanda's report 10/26-10/30

1. What was planned for this week. Halloween Game night. Code cleanup on the engine.

2. What was done. Both though there was more work done for the Game night than anything else.

3. Problems encountered. Game nights.

4. Plan for next week. Finish code cleanup.

5. How many hours worked. 20

Amanda's report 10/19-10/23

1. What was planned for this week. One click install, work on the parsing some more, final engine prep work for the turn in to Reality Works, deliver lecture prepared last week. Proctored the discrete math test.

2. What was done. All of that.

3. Problems encountered. One click install - not entirely certain that it works the way it should. Just have to wait and see what Reality Works says.

4. Plan for next week. Clean up the disaster of a mess that I had to make of my code base in order to hack in some quick fixes.

5. How many hours worked. 30