CSC 161 Grinnell College Spring, 2012
 
Imperative Problem Solving and Data Structures
 
 

This course is under development, so some adjustments of this material are possible as the course evolves through the Spring 2012 semester.

 
  Modules:   Outline   Module 000   Module 001   Module 010   Module 011
  Topic Index   Data Representation   Module 100   Module 101   Module 110   Module 111

  Instructor   Supplemental Problems   Credits   Schedule ( .dvi format / pdf format / postscript )   Tutors
  Textbooks   Course Work   Deadlines   Collaboration   Cell Phones   Accommodations   Grading
 

This course explores elements of computing that have reasonably close ties to the architecture of computers, compilers, and operating systems. The course takes an imperative view of problem-solving, supported by programming in the C programming language. Some topics include:

Instructor

Henry M. Walker

Office: Science 3811
Telephone: extension 4208
E-mail: walker@cs.grinnell.edu

Office hours are posted weekly on the bulletin board outside Science 3811, with additional hours possible by appointment. You may reserve a half hour meeting by signing up on the weekly schedule, but please sign up at least a day in advance.

Credits

The hardware, software, readings, labs, and other materials from this course have evolved from many sources:

Textbook

Henry Walker, An Introduction to C Through Annotated Examples, http://www.cs.grinnell.edu/~walker/c/index.html

Brian W. Kernighan and Dennis M. Ritchie, The C Programming Language, Second Edition, Prentice Hall, 1988, ISBN 0-13-110362-8 (paperback), 0-13-110370-9 (hardback).

The GNU make Manual, Free Software Foundation, 2006.

Eric Huss, The C Library Reference Guide, University of Illinois Student Chapter, 1997.

The MyroC header file that identifies all MyroC operations defined for the Scribbler 2 robots in C.

A diagram of Scribbler 2 sensors and function calls.

Schedule

While the schedule for this course is expected to evolve, a Tentative Class Schedule is available in .dvi , pdf, and postscript formats.

Also, if you are logged into the departmental network and want a copy printed, click duerer to have a copy printed on the printer duerer.

Course Work

Course Work will involve a combination of the following activities.

Deadlines

Deadlines are shown on the Tentative Class Schedule , and work is due at the start of each class specified. A penalty of 25% per class meeting will be assessed for any assignment turned in late, even work submitted at the end of a class. However, an extension of at least one class period is automatically granted if the department's Linux network is down for an unscheduled period of three or more hours during the week preceding the assignment. Normally, a program or laboratory write-up is due every third class meeting.

Although dates for labs, programming assignments, tests, and the final exam are firm, I understand that circumstances arise when you are not able to attend class.

Absolute Deadline: All homework must be turned in by Friday, 11 May at 5:00 pm;
laboratory reports or programs received after that time will not be counted in the grading of the course.

Collaboration

Collaboration often will be allowed on laboratory exercises and problems from the textbook, but collaboration normally will NOT be allowed on supplemental problems and tests. To avoid confusion, the rules for collaboration on homework are included in the specification of each assignment.

Cell Phones, Text Messaging, and E-Community Devices

Cell phones, text-messaging devices, and other social-networking connections may not be used in this class. If you bring such equipment to the classroom, it must be turned off before the class starts and stay off throughout the class period. Use of such equipment is distracting to those nearby and will not be tolerated.

Accommodations

If you have specific physical, psychiatric, or learning disabilities and require accommodations, please let me know early in the semester so that your learning needs may be appropriately met. You will need to provide documentation of your disability to the Director of Academic Advising. Feel free to talk to me if you have questions or want more information.

Grading

This instructor's grading philosophy dictates that the final grade should ultimately be based upon each student's demonstration of her or his understanding of the material, not on the performance of the class as a whole nor on a strict percentile basis. The following scheme is proposed as a base for how the various assignments and tests will be counted in the final grade.

Lab Write-ups: 15%     Supplemental Problems: 15%     Projects: 25%     Hour Tests: 25%     Exam: 20%