Difference between revisions of "CSCI1106"

From Hallab
Jump to navigation Jump to search
Line 49: Line 49:
 
| Week || Monday || Tuesday || Wednesday || Thursday || Friday  
 
| Week || Monday || Tuesday || Wednesday || Thursday || Friday  
 
|-
 
|-
| 1 || Jan 7<br \>[[Media:L01_Intro.pdf|Course Introduction]] || Jan 8<br \> || Jan 9<br \> [[Media:L02_RoboIntro.pdf|Introduction to Robotics]] || Jan 10<br \> Robotics Tutorial 1|| Jan 11 <br \>
+
| 1 || Jan 6<br \>[[Media:L01_Intro.pdf|Course Introduction]] || Jan 7<br \> || Jan 8<br \> [[Media:L02_RoboIntro.pdf|Introduction to Robotics]] || Jan 9<br \> Robotics Tutorial 1|| Jan 10 <br \>
 
|-
 
|-
| 2 || Jan 14<br \>[[Media:L03_CharacterizingSensors.pdf|Characterizing Sensors]] || Jan 15<br \>Robotics Tutorial 2  || Jan 16<br \> [[Media:L04_UsingSensors.pdf|Using Sensors and Actuators]] || Jan 17<br \> Robotics Tutorial 3|| Jan 18 <br \>Guest Lecture (marine robotics)
+
| 2 || Jan 13<br \>[[Media:L03_CharacterizingSensors.pdf|Characterizing Sensors]] || Jan 14<br \>Robotics Tutorial 2  || Jan 15<br \> [[Media:L04_UsingSensors.pdf|Using Sensors and Actuators]] || Jan 16<br \> Robotics Tutorial 3|| Jan 17 <br \>Guest Lecture (marine robotics)
 
|-
 
|-
| 3 || Jan 21<br \> [[Media:L05_StateDiagrams.pdf|State Transition Diagrams]]|| Jan 22<br \>Robotics Tutorial 4 || Jan 23<br \> [[Media:L06_Failure.pdf|Dealing with Failure]] || Jan 24<br \>Robotics Tutorial 5 || Jan 25 <br \> Quiz 1
+
| 3 || Jan 20<br \> [[Media:L05_StateDiagrams.pdf|State Transition Diagrams]]|| Jan 21<br \>Robotics Tutorial 4 || Jan 22<br \> [[Media:L06_Failure.pdf|Dealing with Failure]] || Jan 23<br \>Robotics Tutorial 5 || Jan 24 <br \> Quiz 1
 
|-
 
|-
| 4 || Jan 28<br \> [[Media:L07.pdf|Variables and Threads]]|| Jan 29<br \> Robotics Tutorial 6 || Jan 30<br \> [[Media:L08.pdf|Project Planning]] || Jan 31<br \> Robotics Project 1|| Feb 1 <br \>4 Munro Day - University closed
+
| 4 || Jan 27<br \> [[Media:L07.pdf|Variables and Threads]]|| Jan 28<br \> Robotics Tutorial 6 || Jan 29<br \> [[Media:L08.pdf|Project Planning]] || Jan 30<br \> Robotics Project 1|| Jan 31 <br \>4 Munro Day - University closed
 
|-
 
|-
| 5 || Feb 4<br \>[[Media:L09.pdf|Using State Transition Diagrams]] || Feb 5<br \> Robotics Project 2|| Feb 6<br \> [[Media:L10.pdf|Debugging]] || Feb 7<br \> Robotics Project 3|| Feb 8<br \> Quiz 2
+
| 5 || Feb 3<br \>[[Media:L09.pdf|Using State Transition Diagrams]] || Feb 4<br \> Robotics Project 2|| Feb 5<br \> [[Media:L10.pdf|Debugging]] || Feb 6<br \> Robotics Project 3|| Feb 7<br \> Munro Day - University closed
 
|-
 
|-
| 6 || Feb 11<br \>[[Media:L11.pdf|Threads, Interference, and Other Topics]] || Feb 12<br \> Robotics Project 4|| Feb 13<br \> [[Media:L12.pdf|Project Management]] || Feb 14<br \> Robotics Olympics|| Feb 15<br \>
+
| 6 || Feb 10<br \>[[Media:L11.pdf|Threads, Interference, and Other Topics]] || Feb 11<br \> Robotics Project 4|| Feb 12<br \> [[Media:L12.pdf|Project Management]] || Feb 13<br \> Robotics Olympics|| Feb 14<br \>
 
|-
 
|-
| 7 || Feb 18 <br \> [[Media:L13.pdf|Introduction to Game Architecture]]|| Feb 19<br \> Game Tutorial 1|| Feb 20<br \> [[Media:L14.pdf|Classes, Objects, and Events]] || Feb 21 REPORT DUE<br \> Game Tutorial 2|| Feb 22<br \> Quiz 3
+
| 7 || Feb 17 <br \> [[Media:L13.pdf|Introduction to Game Architecture]]|| Feb 18<br \> Game Tutorial 1|| Feb 19<br \> [[Media:L14.pdf|Classes, Objects, and Events]] || Feb 20 REPORT DUE<br \> Game Tutorial 2|| Feb 21<br \> Quiz 3
 
|-
 
|-
| 8 || Mar 4<br \>[[Media:L15.pdf|Movement and Collision Detection]] || Mar 5<br \> Game Tutorial 3|| Mar 6<br \>  [[Media:L16.pdf|Player Movement]]|| Mar 7<br \> Game Tutorial 4|| Mar 8<br \> Devin Horsman:  Demystifying games / Game Design primer
+
| 8 || Mar 3<br \>[[Media:L15.pdf|Movement and Collision Detection]] || Mar 4<br \> Game Tutorial 3|| Mar 5<br \>  [[Media:L16.pdf|Player Movement]]|| Mar 6<br \> Game Tutorial 4|| Mar 7<br \> Devin Horsman:  Demystifying games / Game Design primer
 
|-
 
|-
| 9 || [[Media:codeExamples.docx|Code interpretation]] || Mar 12<br \> Game Tutorial 5|| Mar 13<br \> Mar 11<br \> [[Media:L17.pdf|Play Testing]] || Mar 14<br \> Game Tutorial 6|| Mar 15<br \> Quiz 4
+
| 9 || Mar 10<br \>[[Media:codeExamples.docx|Code interpretation]] || Mar 11<br \> Game Tutorial 5|| Mar 12<br \> Mar 13<br \> [[Media:L17.pdf|Play Testing]] || Mar 13<br \> Game Tutorial 6|| Mar 14<br \> Quiz 4
 
|-
 
|-
| 10 || Mar 18<br \>[[Media:L18.pdf|High Level Game Design]]  || Mar 19<br \>Game Project 1|| Mar 20<br \> [[Media:L19.pdf|Randomness, Arrays and Buttons]] || Mar 21<br \> Game Project 2|| Mar 22<br \>
+
| 10 || Mar 17<br \>[[Media:L18.pdf|High Level Game Design]]  || Mar 18<br \>Game Project 1|| Mar 19<br \> [[Media:L19.pdf|Randomness, Arrays and Buttons]] || Mar 20<br \> Game Project 2|| Mar 21<br \>
 
|-
 
|-
| 11 || Mar 25<br \>[[Media:L20.pdf|Other Controls and Projectiles]] || Mar 26<br \>Game Project 3 || Mar 27<br \> [[Media:L22.pdf|Polish]]/Quiz 5 || Mar 29<br \> Game Project 4|| Mar 29<br \> Good Friday
+
| 11 || Mar 24<br \>[[Media:L20.pdf|Other Controls and Projectiles]] || Mar 25<br \>Game Project 3 || Mar 26<br \> [[Media:L22.pdf|Polish]]/Quiz 5 || Mar 27<br \> Game Project 4|| Mar 28<br \> Good Friday
 
|-
 
|-
| 12 || Apr 1 <br \>  No Class || Apr 2<br \> Game Project 5|| Apr 3 <br \> Review || Apr 4<br \> Presentation Day|| Apr 5<br \> Quiz 6
+
| 12 || Mar 31 <br \>  No Class || Apr 1<br \> Game Project 5|| Apr 2 <br \> Review || Apr 3<br \> Presentation Day|| Apr 4<br \> Quiz 6
 
|-
 
|-
| 13 || Apr 8 <br \>  || Apr 9<br \> || Apr 10 <br \>  || Apr 11<br \> Reports due|| Apr 12<br \>  
+
| 13 || Apr 7 <br \>  || Apr 8<br \> || Apr 9 <br \>  || Apr 10<br \> Reports due|| Apr 12<br \>  
 
|-
 
|-
 
|}
 
|}

Revision as of 15:09, 25 December 2013

Animated Computing 2014

Instructors

Professor:

 Dr. Thomas Trappenberg (tt@cs.dal.ca)  
Office: Room 4216 in Mona Campbell Building on Coburg RD
Office hour: write email

Teaching Assistants:

 TBA

Course Description

The Animated Computing course is a hands-on introduction to two areas of computer science, robotics and game design. Students will program robots to solve a variety of tasks and design animated computer games. Students will learn about the challenges that a robot faces when interacting with the world around it and the challenges that we face in designing and programming the robots. Students will also learn about computer game design and how to implement simple but interesting animated computer games. Students will investigate both the hardware and software aspects of robotics and design, implement, and play-test basic computer games. Students will also learn how to apply the empirical method to investigate various aspects in robotics and game design.

Classes will be structured in a lecture/lab format and divided into two modules: Game Design and Robotics. During the lectures students will be introduced to the concepts and underpinnings of robotics and game design. The laboratory portion will be devoted to hands-on work in a group. Groups will work together for the duration of a module.


Learning Outcomes

• Describe how an event driven system works.
• Describe and justify what constitutes a good game.
• Implement a game using integrated media presentation authoring software. 
• Identify the challenges in designing and implementing games.
• Design a simple animated game.
• Use sensors and actuators in a robotics applications.
• Use states and transitions to model the behaviour of a system.
• Apply various techniques to identify and recover from faults.
• Program a robot to accomplish tasks of moderate complexity.
• Identify some of the challenges in robotics and mechanisms for overcoming these challenges.
• Formulate a question that can be answered via a study, experiment, or project.
• Apply various methods, tools, and techniques to conduct a study, experiment, or project. 
• Analyze resulting data and relate it to theoretical and foundational knowledge.
• Describe factors that may adversely affect the study, experiment, or project.
• Identify future directions in various technologies and computer science fields. 
• Work with peers on a shared project.
• Write a technical report describing and justifying the design and implementation of a project.

Prerequisites

None.


Schedule (tentative; can change)

Week Monday Tuesday Wednesday Thursday Friday
1 Jan 6
Course Introduction
Jan 7
Jan 8
Introduction to Robotics
Jan 9
Robotics Tutorial 1
Jan 10
2 Jan 13
Characterizing Sensors
Jan 14
Robotics Tutorial 2
Jan 15
Using Sensors and Actuators
Jan 16
Robotics Tutorial 3
Jan 17
Guest Lecture (marine robotics)
3 Jan 20
State Transition Diagrams
Jan 21
Robotics Tutorial 4
Jan 22
Dealing with Failure
Jan 23
Robotics Tutorial 5
Jan 24
Quiz 1
4 Jan 27
Variables and Threads
Jan 28
Robotics Tutorial 6
Jan 29
Project Planning
Jan 30
Robotics Project 1
Jan 31
4 Munro Day - University closed
5 Feb 3
Using State Transition Diagrams
Feb 4
Robotics Project 2
Feb 5
Debugging
Feb 6
Robotics Project 3
Feb 7
Munro Day - University closed
6 Feb 10
Threads, Interference, and Other Topics
Feb 11
Robotics Project 4
Feb 12
Project Management
Feb 13
Robotics Olympics
Feb 14
7 Feb 17
Introduction to Game Architecture
Feb 18
Game Tutorial 1
Feb 19
Classes, Objects, and Events
Feb 20 REPORT DUE
Game Tutorial 2
Feb 21
Quiz 3
8 Mar 3
Movement and Collision Detection
Mar 4
Game Tutorial 3
Mar 5
Player Movement
Mar 6
Game Tutorial 4
Mar 7
Devin Horsman: Demystifying games / Game Design primer
9 Mar 10
Code interpretation
Mar 11
Game Tutorial 5
Mar 12
Mar 13
Play Testing
Mar 13
Game Tutorial 6
Mar 14
Quiz 4
10 Mar 17
High Level Game Design
Mar 18
Game Project 1
Mar 19
Randomness, Arrays and Buttons
Mar 20
Game Project 2
Mar 21
11 Mar 24
Other Controls and Projectiles
Mar 25
Game Project 3
Mar 26
Polish/Quiz 5
Mar 27
Game Project 4
Mar 28
Good Friday
12 Mar 31
No Class
Apr 1
Game Project 5
Apr 2
Review
Apr 3
Presentation Day
Apr 4
Quiz 6
13 Apr 7
Apr 8
Apr 9
Apr 10
Reports due
Apr 12

Grading Scheme

Evaluation

20% Game Design Project

  Project Evaluation (50% of project mark) 
     Due the day before the project presentation lab.
     Each group submits the game that they have designed. All members of the group are assigned the 
     same mark for the project. 
  Project Report (50% of project mark) 
     Due Monday, October 21, 8:35am (in class).
     Each group submits a user manual and a technical manual describing their project and all members 
     of the group are assigned the same mark for the papers. 

20% Robotics Project

  Project Evaluation (50% of project mark) 
     Due at start of the project presentation lab.
     Each group submits three programs designed to participate in the “Robot Olympics”. 
     All members of the group are assigned the same mark for the project.
  Project Report (50% of project mark)
     Due Wednesday, December 4, 8:35am (instructor’s office)
     Each group submits a single report describing their project and all members of the group are 
     assigned the same mark for the paper.

10% Lab Reports

  At the end of each tutorial and project work period each group submits a brief lab report detailing 
  what they accomplished, who was present, and answering a number of specified questions. (See course 
  notes for lab report forms.) All members of the group are assigned the same mark.

20% Quizzes

  There are 6 quizzes that evaluate knowledge of the course content learned both in lectures and labs.

30% Final Exam

  There will be a two hour final exam that will be scheduled by the Registrar.

Notes =

  All project submissions are to be done via the Moodle (http://moodle.cs.dal.ca). Only one member of the 
  group needs to  submit. This group member must be enrolled in the CSCI1106 course on the Moodle site.
  No late submissions accepted except in cases of documented, university approved reasons.
  To pass the course students must pass the individual component of the evaluation comprising the bi-weekly 
  Quiz and Final exam portion of the marks.
  A student’s project evaluation may be lowered if they do not contribute sufficiently to the project.
  Grades will be assigned using the letter grade scale in Section 17.1 of Dalhousie Academic Calendar.
  The instructor reserves the right to adjust a student’s evaluation criteria, with the student’s consent, 
  if the instructor deems than an adjustment is warranted.


Student Accommodation

Students may request accommodation as a result of barriers related to disability, religious obligation, or any character- istic under the Nova Scotia Human Rights Act. Students who require academic accommodation for either classroom participation or the writing of tests and exams should make their request to the Advising and Access Services Center 3 (AASC) prior to or at the outset of the regular academic year. Please visit www.dal.ca/access for more information and to obtain the Request for Accommodation Form A. A note taker may be required as part of a students accommodation. There is an honorarium of $75/course/term (with some exceptions). If you are interested, please contact AASC at 494-2836 for more information. Please note that your classroom may contain specialized accessible furniture and equipment. It is important that these items remain in the classroom, untouched, so that students who require their usage will be able to participate in the class.




Academic Integrity & Plegarism

(Based on the sample statement provided at http://academicintegrity.dal.ca. Written by Dr. Alex Brodsky.)

Please familiarize yourself with the university policy on Intellectual Honesty. Every suspected case will be reported.

At Dalhousie University, we respect the values of academic integrity: honesty, trust, fairness, responsibility and respect. As a student, adherence to the values of academic integrity and related policies is a requirement of being part of the academic community at Dalhousie University.


What does academic integrity mean?

Academic integrity means being honest in the fulfillment of your academic responsibilities thus establishing mutual trust. Fairness is essential to the interactions of the academic community and is achieved through respect for the opinions and ideas of others. Violations of intellectual honesty are offensive to the entire academic community, not just to the individual faculty member and students in whose class an offence occurs. (see Intellectual Honesty section of University Calendar)


How can you achieve academic integrity?

• Make sure you understand Dalhousies policies on academic integrity.

• Give appropriate credit to the sources used in your assignment such as written or oral work, com- puter codes/programs, artistic or architectural works, scientific projects, performances, web page designs, graphical representations, diagrams, videos, and images. Use RefWorks to keep track of your research and edit and format bibliographies in the citation style required by the instructor (http://www.library.dal.ca/How/RefWorks)

• Do not download the work of another from the Internet and submit it as your own.

• Do not submit work that has been completed through collaboration or previously submitted for another assignment without permission from your instructor. • Do not write an examination or test for someone else.

• Do not falsify data or lab results.

These examples should be considered only as a guide and not an exhaustive list.


What will happen if an allegation of an academic offence is made against you?

I am required to report a suspected offence. The full process is outlined in the Discipline flow chart, which can be found at: http://academicintegrity.dal.ca/Files/AcademicDisciplineProcess.pdf and in- cludes the following:

1. Each Faculty has an Academic Integrity Officer (AIO) who receives allegations from instructors.

2. The AIO decides whether to proceed with the allegation and you will be notified of the process.

3. If the case proceeds, you will receive an INC (incomplete) grade until the matter is resolved.

4. If you are found guilty of an academic offence, a penalty will be assigned ranging from a warning to a suspension or expulsion from the University and can include a notation on your transcript, failure of the assignment or failure of the course. All penalties are academic in nature.


Where can you turn for help?

• If you are ever unsure about ANYTHING, contact myself.

• The Academic Integrity website (http://academicintegrity.dal.ca) has links to policies, defini tions, online tutorials, tips on citing and paraphrasing.

• The Writing Center provides assistance with proofreading, writing styles, citations.

• Dalhousie Libraries have workshops, online tutorials, citation guides, Assignment Calculator, Ref- Works, etc.

• The Dalhousie Student Advocacy Service assists students with academic appeals and student discipline procedures.

• The Senate Office provides links to a list of Academic Integrity Officers, discipline flow chart, and Senate Discipline Committee.

Request for special accommodation

Students may request accommodation as a result of barriers related to disability, religious obligation, or any characteristic under the Nova Scotia Human Rights Act. Students who require academic accommodation for either classroom participation or the writing of tests and exams should make their request to the Advising and Access Services Center (AASC) prior to or at the outset of the regular academic year. Please visit www.dal.ca/access for more information and to obtain the Request for Accommodation – Form A.

A note taker may be required as part of a student’s accommodation. There is an honorarium of $75/course/term (with some exceptions). If you are interested, please contact AASC at 494-2836 for more information.

Please note that your classroom may contain specialized accessible furniture and equipment. It is important that these items remain in the classroom, untouched, so that students who require their usage will be able to participate in the class.