CSC 161 Module on Integrated Robotics

Summary and Main Topics

The purpose of this module is to smoothly integrate and review material that has been presented through the semester, with a particular emphasis on C programming concepts and full usage of the Scribbler robot.

1. Command-Line Arguments
2. Files
3. Logging Commands

Day-by-day Details

Day	Topic	Preparation	In-class	Due Date	Availability for Extra Credit
Wednesday, December 4	Introduction		command-line.c Examples: Walker, An Introduction to C Through Annotated Examples Program 19 (genfile.c), pages 31-32. Program 20 (readfiles.c), pages 33-34. Program 21 (fileletters-1.c), pages 35-38. Program 22 (fileletters-2.c), pages 39-40. Program 23 (fileletters-3.c), pages 41-43.
Friday, December 6	Command-Line Arguments	King, Section 13.7 K&R 5.10 Working with strings Processing Letter/Number Combinations	lab exercise
Monday, December 9	Files	King, Sections 22.1-22.5 K&R 7.5 - 7.8, 8.1 - 8.5 state-year.c	lab exercise		Extra Credit Lab, if submitted by Friday, December 13 at 5:00 pm
Tuesday, December 10	Project Day 1		project	Friday, December 13
Wednesday, December 11	Supplemental Problem 5		Supplemental Problem 5 (done individually)	Wednesday, December 11
Wednesday, December 11	Project Day 2		project	Friday, December 13

Project: Robot Logging Suite

Write a "robot logger" program which can log actions to a file, and also read actions from a file and perform them.

• You should use command-line input flags to specify whether the robot is in "read" mode (reading actions from a file), "write" mode (logging actions onto a file), or both "read" and "write" mode. In particular:

  • if the use specifies a command-line directive -w, then

    • if the command line also has a file name, subsequent processing should use this file for writing. However, if no file name is given, the program should ask the user for a file name.
    • the program should perform the commands, and
    • the program log the commands in the specified file.

  • if the use specifies a command-line directive -r, then

    • if the command line also has a file name, subsequent processing should use this file for reading. However, if no file name is given, the program should ask the user for a file name.
    • the program should read commands from the specified file, and
    • the program should perform the commands.

  • if no command-line arguments are given, the program should remind the user that the program requires -w or -r.

  • it should be possible for a user to utilize both -w and -r mode.

• This program should support at least 10 different actions (following the module 011 project command requirements).

Hints

• You are encouraged to use either your module 011 project or your command-robot.c program as the basis for the command input.

• One approach would involve two variables readMode and writeMode.

  • Both readMode and writeMode are set at the beginning of the program by processing the command line.
  • If readMode is set, all input should come from a file; if it is not set, all input should come from the keyboard. (This impacts where data will be read from, but the basic approach to reading could be the same in both cases.)
  • If writeMode is set, commands should be written to a file; if not, commands might or might not be echoed to the terminal (your choice).

Grading

• General Grading Form
• Project-specific Grading Form