Recitations
|
|
|
Below are the weekly objectives for each recitation session and also any code that is supplied for recitation use. For objective specifics you have to attend recitation.
Most recitations will consist of some group discussion/lecture time, time to complete a small programming problem designed to reinforce current topics in the course, and some time to work on the current programming assignment in teams.
|
Week 1: August 25-29
Logging in, Running Java, and First Assignment Overview
Errata: if you were in recitation on Monday, the office hours on the slides for Erin Nagoshi were incorrect. Her correct office hours are 1-3 on Sunday.
Slides
Week 2: September 2-5
No recitation on Monday. Students in the Monday recitation are encouraged to attend the make-up recitation on Tuesday from 3-4:40.
Code files (right click to save): Driver.java, NumList.java, input.txt
The program reads in floating point numbers from a file. The filename to read is passed as a command line argument. The program sorts the numbers in the file and prints the numbers in sorted order.
Slides
Week 3: September 8-12
Week 4: September 15-19
Slides
Code files (right click to save):
StackInterface.java,
StackArrayBased.java,
StackException.java,
Node.java,
StackListBased.java,
StackReferenceBased.java
Week 5: September 22-26
- Objectives:
- Practice concepts and problems from complexity sections in textbooks:
- estimate Big-O for some functions,
- determine Big-O witnesses,
- show informal proof of Big-O using witnesses,
- assess algorithm complexity
- Assist teams and work on programming assignment 2
Week 6: September 29 - October 3
Week 7: October 6-10
Diff example files are here. NOTE: the files outA.txt, outB.txt, outC.txt, and outD.txt are provided to give you files to use diff on. They should not be taken to be correct output for program 3. The file prog3Test.txt is the correct output for the provided input files.
Week 8: October 13-17
Partner Matching
Fill out a template autobiography page during the week of October 13 - October 17. Answer all of the questions provided on the template as honestly as possible. You will be assigned a code name for example, my code name might be blue-bird. My page would therefore be named blue-bird.html. The template page to modify is here (right click and "Save Link as..."). When you finish your page, email your page to:
stevens at cs dot colostate dot edu
Include your real name and your code name in this e-mail and attach your page.
Send in your page by 9:00 PM Friday, October 13. This weekend, we will post the webpages you sent in. Examine the list of potential partner autobiographies and choose 3 partners and rank them in order. Send an email to:
stevens at cs dot colostate dot edu
Include your "code name", your real name, and the "code names" of your three partner choices in rank order. Complete this by 12:00 Noon, Friday, October 24. Partner assignments will be announced shortly there after. Update (10-24): Voting is now closed.
If you miss recitation this week, send John an e-mail (stevens at cs dot colostate dot edu) and ask for a code name.
Week 9: October 20-24
- Partner matching pages, vote by Noon on Friday. Update (10-24): Voting is now closed.
- Go over midterm exam
- Discuss written homework assignment
Week 10: October 27-31
Week 11: November 3 - November 7
- Review for Midterm 2 (Monday and Tuesday) Review Outline
- Programming Assignment 4 work time.
- Brief review of testing strategies.
Week 12: November 10-14
- Brief review of testing strategies: test small parts of the assignment functionality first, then work up to larger test cases.
- Go over Midterm 2.
Week 13: November 17-21
- Dot: example dot file with descriptive comments. The command dotty can be used to open a dot file directly. The resulting graph, generared by the dot file. This image file was generated from the dot file using the command dot -Tpng dotExample.dot -o dotExample.png
- Dijkstra's algorithm example, using the previous graph.
Thanksgiving! November 24-28
Week 14: December 1-5
Week 15: December 8-12
Copyright ÃÂé 2007-2009: Colorado State University for CS200. All rights reserved.