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:

• imperative problem solving: top-down design, common algorithms, assertions, invariants

• C programming: syntax and semantics, control structures, functions, parameters, macro processing, compiling, linking, program organization

• concepts with data: data abstraction, integer and floating-point representation, string representation, arrays, unions, structures, linked list data structures, stacks, and queues

• machine-level issues: data representation, pointers, memory management

• GNU/Linux operating system: commands, bash scripts, software development tools

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:

• The underlying hardware and some software for this course are based on research performed by the Institute for Personal Robots in Education (IPRE), hosted at Georgia Tech and Bryn Mawr College. Their materials, including software interfaces, reference materials, and hardware, were funded by grants from Microsoft Research and the National Science Foundation. (wording modified from suggestions by Douglas Blank of the IPRE project and Bryn Mawr College) The main pages for this work are:

  • http://roboteducation.org
  • http://wiki.roboteducation.org/

• The MyroC++ project grew out of efforts by Professor Bruce MacLennan's group, University of Tennessee; special thanks to John Hoare in that group for his assistance.

• The MryoC project was developed by Henry Walker and his group at Grinnell college and funded from Grinnell's Dean's Office.

Textbook

Henry Walker, An Introduction to C Through Annotated Examples, http://www.walker.cs.grinnell.edu/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.

• Supplemental Problems extend the range of problems considered in the course and help sharpen problem-solving skills. Through the semester, four supplemental problems will be required. Supplemental problems numbered 6 or above may be done for extra credit, although extra credit may not raise a student's average on assignments above 120%.

  Note: Supplemental Problems are to be done individually; students should not talk to others in the class, Mentors, Lab Assistants, Technology Consultants about these problems. See for example The Role of Tutors For Computer Science 161.

• Module Laboratories and Projects: Topics in this course are organized into eight modules and a few supplementary labs. Modules include laboratory sessions and conclude with a integrative project.

  Laboratory sessions introduce specific features of Grinnell's computing environment, highlight concepts and constructs introduced in class, allow instructor assistance in a "hands-on" setting, and supplement normal office hours. Approximately four labs require a formal write-up, explaining what work you have done, showing any programming you have done, indicating tests or experiments run, and giving your conclusions. Labs designated [Req] on the Tentative Class Schedule are required -- labs designated [EC] may be done for extra credit. In order for extra-credit labs to provide reasonable benefit, any such lab being submitted for credit must be turned in within 2 weeks of when it is scheduled for coverage in class. As with written homework, extra credit may not raise a student's average on laboratories above 120%.

  Note: As a special incentive for mastering the laboratory exercises, between a third and a half of the problems on each test and on the exam will be taken from the laboratory exercises (with only slight editing).

  Projects: Each of the eight modules concludes with a project, involving both a computer program and associated commentary; and each project is a required part of the course.

  Collaboration on labs and projects encouraged: Many lab activities and projects should be done in groups of two or three, although you may work individually on labs after Lab 8. Only one write-up is expected per group.

• Hour Tests: Two hour tests are tentatively scheduled for Wednesday, 29 February, and Friday, 13 April.

• Exam: Following the College's published schedule, the final examination for this class is scheduled for Thursday, 17 May 2012 at 9:00 am.

• Extra Credit Opportunities: Computer science is a wide-ranging discipline, and courses can cover only selected pieces. To encourage students to expand their horizons, students may earn 2 points extra credit for each Thursday Extra or other departmental talk, by attending the talk and writing a short (4-8 sentence) summary or response. Logistically, when a reasonable statement is received, the student will receive 1 point extra credit counted toward supplemental problems and 1 point extra credit counted toward labs. Additional extra credit opportunities may be announced through the semester.

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.

• When circumstances are known ahead of time (e.g., academic activities, athletic events), I expect you to make arrangements with me before the activity occurs. Normally, we will identify an alternative date for the due date or test.
• When circumstances cannot be reasonably anticipated (e.g., illness, family emergencies), I expect you to notify me as soon as is reasonably possible. (Email is fine.) In the case of medical problems, I expect a written note from a medical professional or counselor that indicates that your health interfered with the course activity. (I do not need to know any details of the medical problem, but I do need to know that you sought help and that the medical professional believed meeting the deadline would likely interfere with your health.)

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%

     http://www.walker.cs.grinnell.edu/courses/161.sp12/index.shtml