1. What was planned?
- Finish state machine and all game mechanics for Table Tilt (hole detection, scoring, timer)
- Integrate my code with Evie's
2. What was done?
- Finished most of the state machine - level loading is still waiting on the packet information from the server.
- Finished hole detection, scoring, and timer.
- Reworked the physics system, did some code cleanup and added more comments.
- Added some of Christie's art assets.
- Wrote rough draft of final presentation.
- Wrote rough draft of user study.
3. Problems encountered?
- The networking is still not quite to the point of integrating with the level loading and ball transfer, but it is very close.
- Some of the art assets need to be tweaked.
4. What did you learn this week?
- Learned about some different containers and array structures in Objective C.
5. What's planned for next week?
- Finish networking, polish game.
- Finish user study and conduct a pilot study.
- Finish research poster and write research paper.
6. Hours worked.
45
Monday, July 27, 2009
Monday, July 20, 2009
Antoine Campbell Weekly Report 7-15-09
1. What was planned?
*Run Study with camp students.
*Work on more challenges for heap game.
*Run study with 2215 students or any students willing.
2. What was done?
*Ran Study with Camp Students
*Set up appointment with Souvenir to evaluate Bunny Generals
*Done with heap challenge and almost done with gameplay
3. Problems encountered?
*No students from 2215 have showed or scheduled for the study, I don't think we can offer any incentives, maybe it should sound more fun on our flyer.
4. What did you learn this week?
*More about how the DarkWynter Engine works and how to use it effectively
*Dictionary's are the greatest thing since sliced bread!
5. What's planned for next week?
*Finish Heap Gameplay button drag and drop interface
*Implement terrain mods for swapping of Arrows
*Modify Log Parser for newly implemented in game Pre/Post test(Bunny Generals)
6. Hours worked.
*40+ hours
*Run Study with camp students.
*Work on more challenges for heap game.
*Run study with 2215 students or any students willing.
2. What was done?
*Ran Study with Camp Students
*Set up appointment with Souvenir to evaluate Bunny Generals
*Done with heap challenge and almost done with gameplay
3. Problems encountered?
*No students from 2215 have showed or scheduled for the study, I don't think we can offer any incentives, maybe it should sound more fun on our flyer.
4. What did you learn this week?
*More about how the DarkWynter Engine works and how to use it effectively
*Dictionary's are the greatest thing since sliced bread!
5. What's planned for next week?
*Finish Heap Gameplay button drag and drop interface
*Implement terrain mods for swapping of Arrows
*Modify Log Parser for newly implemented in game Pre/Post test(Bunny Generals)
6. Hours worked.
*40+ hours
Rachel Brinkman - Week 6
1. What was planned?
- Return the Dance Tool to a stable state
- Help Evie run a user study on the Dance Tool
- Work on integrating Evie's and my work on Table Tilt
2. What was done?
- Helped eliminate some critical bugs - the Dance Tool was stable in time for the study.
- Helped Evie run the user study.
- Worked on the state machine for Table Tilt.
3. Problems encountered?
- Did not really have time to do much integration on Evie's and my work on Table Tilt, due to the crunch on Dance Tool.
4. What did you learn this week?
- The iPhone does not have a state machine system that I can build on, so I will have to write one from scratch.
5. What's planned for next week?
- Finish state machine and all game mechanics for Table Tilt (hole detection, scoring, timer)
- Integrate my code with Evie's
6. Hours worked.
40
- Return the Dance Tool to a stable state
- Help Evie run a user study on the Dance Tool
- Work on integrating Evie's and my work on Table Tilt
2. What was done?
- Helped eliminate some critical bugs - the Dance Tool was stable in time for the study.
- Helped Evie run the user study.
- Worked on the state machine for Table Tilt.
3. Problems encountered?
- Did not really have time to do much integration on Evie's and my work on Table Tilt, due to the crunch on Dance Tool.
4. What did you learn this week?
- The iPhone does not have a state machine system that I can build on, so I will have to write one from scratch.
5. What's planned for next week?
- Finish state machine and all game mechanics for Table Tilt (hole detection, scoring, timer)
- Integrate my code with Evie's
6. Hours worked.
40
Rachel Brinkman - Week 5
1. What was planned?
- Go to AIED conference in the UK
2. What was done?
- Went to AIED conference, attended as many workshops and talks as possible.
- Also worked as a student volunteer - loaded conference bags, signed people up for the conference, directed people to the different conference rooms, and ran mics for the keynote QA sessions.
3. Problems encountered?
- None, but there were some near misses at the Chicago O'Hare International Airport. They don't have enough signs.
4. What did you learn this week?
- I learned a lot about the the cutting edge research questions in the area of AI and Education and some of the potential answers to those questions, such as the study of metacognition, empathetic agents, affect detection, and scaffolding.
5. What's planned for next week?
- Return the Dance Tool to a stable state
- Help Evie run a user study on the Dance Tool
- Work on integrating Evie's and my work on Table Tilt
6. Hours worked.
40ish.
- Go to AIED conference in the UK
2. What was done?
- Went to AIED conference, attended as many workshops and talks as possible.
- Also worked as a student volunteer - loaded conference bags, signed people up for the conference, directed people to the different conference rooms, and ran mics for the keynote QA sessions.
3. Problems encountered?
- None, but there were some near misses at the Chicago O'Hare International Airport. They don't have enough signs.
4. What did you learn this week?
- I learned a lot about the the cutting edge research questions in the area of AI and Education and some of the potential answers to those questions, such as the study of metacognition, empathetic agents, affect detection, and scaffolding.
5. What's planned for next week?
- Return the Dance Tool to a stable state
- Help Evie run a user study on the Dance Tool
- Work on integrating Evie's and my work on Table Tilt
6. Hours worked.
40ish.
Thursday, July 16, 2009
Bethany Miller - week 6 - 7/16/09
1. What was planned?
40
- complete more heap challenges
- do bunny generals study with high schoolers
- two challenges done in heap game
- pre/post test completed for heap game
- parser for all pre/post test results
- online bunny generals surveys and tests
- high school study participants provided constructive feedback
- high school students weren't eligible participants for study, even though they did provide feedback
- bunny generals pre/post tests had errors and need to be redone
- how to use forms
- gained experience in a trial research study
- get eligible study recruits for bunny generals and implement changes in pre/post tests
- create more challenges for heap game
- find a way to implement game play within heap game
- correct log errors
40
Wednesday, July 8, 2009
Thomas Phifer - Week 5 - 7/8/09
1. What was planned?
-- Work on SNAG project have more features added
-- Work on Dance Tool project, document bugs and fix features
2. What was done?
-- Added points features to SNAGEM
-- Documented bugs and fixed features of Dance Tool such as the file system
3. Problems encountered?
-- Still cannot work on the iPhone project because my Macbook is in use by the GIG
-- Subversioning the Dance Tool is a little confusing.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
-- Better time management skills
-- Learned more about PHP and MySQL while working on SNAG
-- Learned more about JavaScript and C# while working on the Dance Tool
-- Better Documentation Skills
5. What's planned for next week?
-- Meet deliverables deadline for week 6
6. Hours worked.
--50
-- Work on SNAG project have more features added
-- Work on Dance Tool project, document bugs and fix features
2. What was done?
-- Added points features to SNAGEM
-- Documented bugs and fixed features of Dance Tool such as the file system
3. Problems encountered?
-- Still cannot work on the iPhone project because my Macbook is in use by the GIG
-- Subversioning the Dance Tool is a little confusing.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
-- Better time management skills
-- Learned more about PHP and MySQL while working on SNAG
-- Learned more about JavaScript and C# while working on the Dance Tool
-- Better Documentation Skills
5. What's planned for next week?
-- Meet deliverables deadline for week 6
6. Hours worked.
--50
Tuesday, July 7, 2009
Bethany Miller - week 5 - 7/7/09
1. What was planned?
Work on heap game and do study on bunny generals
2. What was done?
Teachers were contacted and we have permission to speak to Professor Goodrum's class to recruit students. Also, we have a summer camp of high schoolers coming for testing bunny generals. The second level of the heap game was also finished and we have moved on to the third level. Pre and post tests have been made and implemented into the game itself. Instructions for the first two challenges are also done.
3. Problems encountered?
Creating the heap took a lot of work. Creating the pre and post tests was very time consuming because of having to actually draw out the heaps to be visually accurate, and then saving each separated picture which gave many files to be used.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
I got the best possible review of heaps possible by creating the pre and post tests.
5. What's planned for next week?
- finish testing for bunny generals
- find way to analyze bunny general data
- make progress in other activities for heap game
6. Hours worked.
40
Work on heap game and do study on bunny generals
2. What was done?
Teachers were contacted and we have permission to speak to Professor Goodrum's class to recruit students. Also, we have a summer camp of high schoolers coming for testing bunny generals. The second level of the heap game was also finished and we have moved on to the third level. Pre and post tests have been made and implemented into the game itself. Instructions for the first two challenges are also done.
3. Problems encountered?
Creating the heap took a lot of work. Creating the pre and post tests was very time consuming because of having to actually draw out the heaps to be visually accurate, and then saving each separated picture which gave many files to be used.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
I got the best possible review of heaps possible by creating the pre and post tests.
5. What's planned for next week?
- finish testing for bunny generals
- find way to analyze bunny general data
- make progress in other activities for heap game
6. Hours worked.
40
Antoine Campbell Weekly Report 7-7-2009
1. What was planned?
*Complete another challenge for the heap sort game.
*Contact professors for class visits.
2. What was done?
*Contacted Professors.
*completed heap challenge
*working on next challenge
3. Problems encountered?
*Takes a little time to find the correct places in code in the DarkWynter Engine
4. What did you learn this week?
*More stuff about how to use the DarkWynter Engine.
5. What's planned for next week?
*Run Study with camp students.
*Work on more challenges for heap game.
*Run study with 2215 students or any students willing.
6. Hours worked.
*40 hours
*Complete another challenge for the heap sort game.
*Contact professors for class visits.
2. What was done?
*Contacted Professors.
*completed heap challenge
*working on next challenge
3. Problems encountered?
*Takes a little time to find the correct places in code in the DarkWynter Engine
4. What did you learn this week?
*More stuff about how to use the DarkWynter Engine.
5. What's planned for next week?
*Run Study with camp students.
*Work on more challenges for heap game.
*Run study with 2215 students or any students willing.
6. Hours worked.
*40 hours
Christie Week 4 and Week 5
Reflection
1. What was planned?
* oversee documentation efforts for Dance Tool
* work with Tyler on art Needs for Dance Tool
* create art documentation for the Dance Tool
* create art for Rachel's game idea
* work on xml for the Dance Tool
* comment the Dance Tool
2. What was done?
* documentation
- submitted 3 revision requests for the fdd
*Art requirements:
- created a splash screen for DT
- started art design documentation
- created opening "scene" for Table Tilt (rachel's game)
- work with Tyler to create buttons
*xml
-recursion
-located and removed false code
3. Problems encountered?
When I first heard I had to do recursion I was a little nervous but I have worked through it. I've struggled some with working with code that isn't mine. I value the practice however, as I am beginning to see that programmers are frequently building on top of somebody else's code.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
I have learned the importance of comments. Evie also gave a very interesting analogy for recursion which has illuminated the concept. I have learned the importance of a functional design document, and I have learned a lot about project management and working under deadlines.
5. What's planned for next week?
* User Testing for DT
* art revisions (ongoing)
* additional debugging on the DT
6. Hours worked. *80 (40 week 4 and 40 week 5)
Thursday, July 2, 2009
Antoine Campbell Weekly Post 6-22-09, and 6-29-09
1. What was planned?
* -Review the returned IRB Paperwork
* -Put the finishing touches on Selection Sort
* -Implement Quick Sort or Merge Sort
* -Set some goals for functionality for the first study
* -Implement all tutorial screens
* -Start on Heap game with Amanda
* -Finish a Heap Challenge
* -Make a Program to evaluate logs
2. What was done?
*Revised IRB paperwork and received Approval
*Finished Selection Sort
*Decided no to implement Quick Sort in the prototype
*Finished the Prototype version of Bunny Generals for the study
*Finished tutorial screens for Prototype
*Began Working on Heap Game
*Finished first Simple Heap Game challenge
*Put off Logging evaluator until later
*Finished Selection Sort
3. Problems encountered?
*Coding Quick Sort was very complicated compared to the other sorts
*The Dark Wynter Engine is large and took a while to learn what classes we should be in
*Finals week messed with our plans to run the study, we have to delay a week until classes start again.
4. What did you learn this week?
*Heaps
*Dark Wynter Engine stuff
5. What's planned for next week?
*Complete another challenge allowing students code to modify the heap level in real time
*Contact professors to recruit students and get permission to visit the classes
6. Hours worked.
*80 hours(two weeks)
* -Review the returned IRB Paperwork
* -Put the finishing touches on Selection Sort
* -Implement Quick Sort or Merge Sort
* -Set some goals for functionality for the first study
* -Implement all tutorial screens
* -Start on Heap game with Amanda
* -Finish a Heap Challenge
* -Make a Program to evaluate logs
2. What was done?
*Revised IRB paperwork and received Approval
*Finished Selection Sort
*Decided no to implement Quick Sort in the prototype
*Finished the Prototype version of Bunny Generals for the study
*Finished tutorial screens for Prototype
*Began Working on Heap Game
*Finished first Simple Heap Game challenge
*Put off Logging evaluator until later
*Finished Selection Sort
3. Problems encountered?
*Coding Quick Sort was very complicated compared to the other sorts
*The Dark Wynter Engine is large and took a while to learn what classes we should be in
*Finals week messed with our plans to run the study, we have to delay a week until classes start again.
4. What did you learn this week?
*Heaps
*Dark Wynter Engine stuff
5. What's planned for next week?
*Complete another challenge allowing students code to modify the heap level in real time
*Contact professors to recruit students and get permission to visit the classes
6. Hours worked.
*80 hours(two weeks)
Wednesday, July 1, 2009
Thomas Phifer - Week 4 - 6/29/09
1. What was planned?-- Work on SNAG project have more features added
-- Work on iPhone project, get an app to transfer
-- Work on Dance Tool project, organize and delegate tasks
-- Low Ropes Course
2. What was done?
-- Successfully figured out how to transfer an app to the iPhone (which is no small feat)
-- Successfully organized and delegated tasks for all projects and gave leaders and subordinates for each task and set weekly goals and deliverable
-- Cleaned Dance Tool code and improved functionality
-- Went to Venture's Low Ropes Course and improved teamwork skills
3. Problems encountered?
-- Still cannot work on the iPhone project because my Macbook is in use by the GIG
-- Apple's App transfer process is excessively tedious
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
-- Better time management skills
-- Learned more about the iPhone SDK and Objective C while working on the iPhone project
-- Learned more about PHP and MySQL while working on SNAG
-- Learned more about JavaScript and C# while working on the Dance Tool
5. What's planned for next week?
-- Meet deliverables deadline
6. Hours worked.
--60
Thomas Phifer - Week 3 - 6/24/09
1. What was planned?-- Work on SNAG project have a prototype ready for Charleston
-- Work on iPhone project
-- Work on Dance Tool project
-- Go to Charleston to present about research
2. What was done?
-- Made progress with SNAG by adding poster voting system and registration system
-- Made progress with the Dance Tool project by documenting more bugs and keeping up the functional design document
-- Went to Charleston and presented SNAG
3. Problems encountered?
-- Cannot work on the iPhone project because my Macbook is in use by the GIG
-- Server problems with Codendi, got them fixed though
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
-- Learned more about what STARS is especially during the Charleston trip.
-- Learned more about the iPhone SDK and Objective C while working on the iPhone project
-- Learned more about PHP and MySQL while working on SNAG
-- Learned more about JavaScript and C# while working on the Dance Tool
5. What's planned for next week?
-- More organized goals for all the projects
-- Get an iPhone App transferred to my iPod
6. Hours worked.
--60
Bethany Miller - week 4 - 7/1/09
1. What was planned?
Finish up Bunny Generals and begin working on the heap game
2. What was done?
All bugs were fixed on bunny generals. There is now a working version ready for testing. Teachers have been notified, but recruitment will not be able to start until next week because of exams. First activity of heap game has been created and I did the dialog for instructions.
3. Problems encountered?
Publishing bunny generals did not work as planned, as well as recruitment. We didn't realize it was exam time, so this hindered our schedule in finishing testing this week.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
I became more familiar with XML files and learned the importance of searching for bugs before actually showing the completed project to others.
5. What's planned for next week?
- start testing for bunny generals
- find way to analyze bunny general data
- make progress in other activities for heap game
6. Hours worked.
40
Finish up Bunny Generals and begin working on the heap game
2. What was done?
All bugs were fixed on bunny generals. There is now a working version ready for testing. Teachers have been notified, but recruitment will not be able to start until next week because of exams. First activity of heap game has been created and I did the dialog for instructions.
3. Problems encountered?
Publishing bunny generals did not work as planned, as well as recruitment. We didn't realize it was exam time, so this hindered our schedule in finishing testing this week.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
I became more familiar with XML files and learned the importance of searching for bugs before actually showing the completed project to others.
5. What's planned for next week?
- start testing for bunny generals
- find way to analyze bunny general data
- make progress in other activities for heap game
6. Hours worked.
40
Rachel Brinkman - Week 4 - 7/1/09
1. What was planned?
- Learn about the capabilities of the iPhone accelerometer and build a limited prototype of the table tilt game (by this Friday)
2. What was done?
- Worked on table tilt prototype - got the app working in landscape mode, found an alternate way to draw using the CoreGraphics framework, and got simple ball physics working on one iPhone.
3. Problems encountered?
- Making a multiple-view application in landscape mode is actually not possible. There is a key that can be set in the Info.plist for the project that is supposed to force the orientation to whatever you choose, but it does not seem to have an affect unless each view controller also gets instructions. Even then, only the primary view will change, and not the secondary view. After searching around for a while, I discovered that landscape mode for multiple views and view controllers is not actually possible. Applications that appear to be this way are actually just faked - one or more of the screens is just an image that makes the user think that the screen has rotated. This is different than in-app rotation by the way - it is very possible to take a portrait app and rotate to landscape when the user turns the iPhone. However, this was not what I needed. I ended up creating a landscape splashscreen view and a portrait game view, but the user will assume that it is still in landscape, and so they will still hold it that way.
- Another problem that I had was with drawing, although the fact that the device was not drawing was actually indicative of a larger problem. Basically, the flow of control for the program had entirely disappeared, and the timer that I had created within the main thread of execution was never being called. I discovered that when using .nib files (so basically any time you are using multiple views), all of the objects are archived inside the .nib, and so the initWithFrame method is never called. This method contained all of my timer initialization code, and since it never ran, nothing was happening in the program. The fix for this is to use the awakeFromNib or initWithCoder methods instead.
- DEPLOYMENT. Deploying to an actual device was a nightmare - Apple has a lot of different certificates that you need as a developer before you can deploy your app, and even when you have created all of them, there are lots of little things that can go wrong along the way. Thanks to Evie and Thomas for helping me get that working!
- The accelerometer is also a problem right now. I can access the data from the three axis correctly, but am running into trouble with the math that ties the readings to the physical movement of the ball.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
- Learned a lot more about views and .nib files
- Learned an alternative way to draw on the iPhone
- Learned some about the accelerometer on the iPhone
- Learned more about Objective C
5. What's planned for next week?
- Finish the prototype by this Friday
- Go to the AIED conference!
6. Hours worked.
40
- Learn about the capabilities of the iPhone accelerometer and build a limited prototype of the table tilt game (by this Friday)
2. What was done?
- Worked on table tilt prototype - got the app working in landscape mode, found an alternate way to draw using the CoreGraphics framework, and got simple ball physics working on one iPhone.
3. Problems encountered?
- Making a multiple-view application in landscape mode is actually not possible. There is a key that can be set in the Info.plist for the project that is supposed to force the orientation to whatever you choose, but it does not seem to have an affect unless each view controller also gets instructions. Even then, only the primary view will change, and not the secondary view. After searching around for a while, I discovered that landscape mode for multiple views and view controllers is not actually possible. Applications that appear to be this way are actually just faked - one or more of the screens is just an image that makes the user think that the screen has rotated. This is different than in-app rotation by the way - it is very possible to take a portrait app and rotate to landscape when the user turns the iPhone. However, this was not what I needed. I ended up creating a landscape splashscreen view and a portrait game view, but the user will assume that it is still in landscape, and so they will still hold it that way.
- Another problem that I had was with drawing, although the fact that the device was not drawing was actually indicative of a larger problem. Basically, the flow of control for the program had entirely disappeared, and the timer that I had created within the main thread of execution was never being called. I discovered that when using .nib files (so basically any time you are using multiple views), all of the objects are archived inside the .nib, and so the initWithFrame method is never called. This method contained all of my timer initialization code, and since it never ran, nothing was happening in the program. The fix for this is to use the awakeFromNib or initWithCoder methods instead.
- DEPLOYMENT. Deploying to an actual device was a nightmare - Apple has a lot of different certificates that you need as a developer before you can deploy your app, and even when you have created all of them, there are lots of little things that can go wrong along the way. Thanks to Evie and Thomas for helping me get that working!
- The accelerometer is also a problem right now. I can access the data from the three axis correctly, but am running into trouble with the math that ties the readings to the physical movement of the ball.
4. What did you learn this week? (esp. computer science, or anything surprising or interesting)
- Learned a lot more about views and .nib files
- Learned an alternative way to draw on the iPhone
- Learned some about the accelerometer on the iPhone
- Learned more about Objective C
5. What's planned for next week?
- Finish the prototype by this Friday
- Go to the AIED conference!
6. Hours worked.
40
Subscribe to:
Posts (Atom)