CS 1666 www.cs.pitt.edu/~nlf4/cs1666/ Introduction Meta-notes - - PowerPoint PPT Presentation
CS 1666 www.cs.pitt.edu/~nlf4/cs1666/ Introduction Meta-notes These notes are intended for use by students in CS1666 at the University of Pittsburgh. They are provided free of charge and may not be sold in any shape or form. These
www.cs.pitt.edu/~nlf4/cs1666/
the University of Pittsburgh. They are provided free of charge and may not be sold in any shape or form.
during course lectures. If you miss a lecture, you should definitely obtain both these notes and notes written by a student who attended the lecture.
2
Office: 6313 Sennott Square
3
○ Day/time
4
○ www.cs.pitt.edu/~nlf4/cs1666/
○ No late assignment submissions ○ If you do not submit an assignment by the deadline, you will receive a 0 for that assignment
5
6
forest trees throughout its range
chestnut tree in the world
between 3 and 4 billion American chestnut trees were destroyed in the first half of the 20th century by the Chestnut Blight
7
US in Philadelphia
inhibits the growth of other plants to suppress competition
in the US
trade, and sale banned in Massachusetts
8
○ Exploration and development of technologies that will enable the deployment of robots in forests for the purpose of forest health
○ Conducting field surveys ○ Detecting and controlling invasive species
9
consuming/expensive
○ Use 1666 to train students in 3D simulation ○ Recruit 1666 students into graduate program ○ Have them work on ForesBott project ○ Save America's forests
10
1. Using videogame design as an example use case of advanced computer science concepts 2. Gaining experience in large group development 3. Producing videogames
11
○ From scratch! ■ Every team will build a custom engine and game on that engine using only C++ and SDL ○ 2D ○ Must implement 3 "advanced features" ■ E.g.:
○ Will be built each week live by the instructor at the end of lecture ■ Hence, must build/run Linux native
12
○ Each team will further be divided into 3 subteams of 3-4 students focused on studying and implementing an advanced topic ○ Everyone on a team will share responsibility for the overall game and is expected to contribute equally to the code not required by a specific advanced topic ○ Everyone on a team is expected to contribute equally to any art and story development required by the game
13
○ Our own Jeff Sellak used to work at Nintendo, and he says that at the time he was active there what we’d call "programmer art" was all they wanted. It was the opinion that if a game was not fun as black squares on a white background, it wasn’t actually fun. I think might be true. I often think about DK: King of Swing in this context, it’s one
also said that you couldn’t pitch them for specific IPs, really - you pitched fun mechanics, and fun mechanics got blessed with a nod from the catalog. I always found that interesting and, frankly, informative.
14
the entire team (all advanced topic subteams)
11:59PM on the starting day of their week
○ Goals should be broad enough to represent significant effort by the entire team for the week ○ Should be small enough to be reasonably accomplished
day of their week
○ Report should be emailed to the instructor only
day of a manager's week
the team's repository builds/runs
15
16
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Wednesday-Tuesday
Game demoed in class on the 18th Report due by 11:59PM
All code pushed to GitHub by 11:59PM on the 17th Goal spec due by 11:59PM on the 11th
○ Hence, the instructor will have to approve them
○ E.g.: ■ "Write the enemy AI" is too broad to be doable in a single week ■ "Change player's max velocity from 300px/sec to 250px/sec" is not significant enough to ensure the game will be completed by the end of the term
17
progress made toward that goal
○ Was it accomplished? ■ If not, what were the stumbling blocks? ■ If so, are there any remaining issues? What are the next steps with this work done?
○ List the pull requests that they made over the week and the goal that that pull request helped achieve ■ This means that you should make a note for each pull request that you, as the manager, approve! ■ A brief summary of that team member's performance for the week
viewed by the instructor, hence why progress reports are emailed to the instructor and not added to the organization repo.
18
the course, e.g.:
○ Establish teams and advanced topic sub-teams ○ Schedule management weeks ○ Report management week goal specifications ○ Schedule advanced topic presentations
requests to the instructor to contribute
linked in lecture
19
○ The master branch of that repository will be pulled/tested each week in lecture
and add all team members to that repository
○ All will need to be able to pull code in during their management week
their own work
○ Issue a pull requests to the canonical repository ○ Managers responsible for integrating pull requests
a link to their fork of the canonical repository
20
presentation about their advanced topic
advanced topic of their choice, but will also learn about all
advance of the talk
○ Specific due dates will appear on the class website
application to your game in particular
21
○ Standard lecture
○ Game proposals
○ Standard lectures
○ Standard lectures
○ Advanced topic presentations
22
23
24
25
26
27
28
29
30
31
32
33
34
35
○ Could be increased by up to 1MB by a cartridge
○ Could only render 25 different colors at a time, though
36
○ Pentium 4 2.8GHz / Athlon XP 2800+ ○ 1GB RAM ○ GeForce 7600 GT 256MB / Radeon 9800 Pro
○ Core 2 Duo E4500 2.2GHz / Athlon 64 X2 Dual Core 5000+ ○ 2GB RAM ○ GeForce 8800 GS / Radeon HD 3850
37
38
a game to build as a team over the course of the term.
39