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, April 29	Command-Line Arguments	King, Section 13.7 K&R 5.10 Working with strings	lab exercise 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, May 1	Files	King, Sections 22.1-22.3 K&R 7.5 - 7.8	lab exercise
Monday, May 4	Files Continued	King, Sections 22.1-22.5 K&R 8.1 - 8.5 state-year.c	lab exercise		extra credit if submitted by Friday, May 8
Tuesday, May 5	Supplemental Problem 5		Supplemental Problem 5 (done individually)	Tuesday, May 5
Tuesday, May 5	Project Day 1		project	Friday, May 8
Wednesday, May 6	Project Day 2		project	Friday, May 8

Project: Robot Logging Suite

Write a "robot logger" program which can log actions to a file, and also read actions from a file and performs 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 flag -w has a flag and the following command-line argument does not start with a hyphen -, then that following argument should be used as the 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 should log the commands in the specified file.

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

    • if the flag -r has a flag and the following command-line argument does not start with a hyphen -, then that following argument should be used as the file for writing. 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.

  • 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). As with the Module 011 project, each action (except, perhaps, quit) must be implemented as a separate procedure.

Examples

The following examples are based on a program proj111 that supports this project. Although this table shows several possibilities, the table is not complete. For example, various combinations of -r and -w are possible, with and without file names, and the -r and -w flags could be in either order.

Command line	Interpretation
proj111	no command-line arguments, so reads from terminal and writes to terminal
proj111 -r infile.dat	reads commands from file infile.dat; writes to terminal
proj111 -r	reads from a file; since filename not given on the command line, program must ask user what file to use; program writes to terminal
proj111 -w logfile.dat	reads from terminal; writes commands with parameters to file logfile.dat
proj111 -w	reads from terminal; writes commands with parameters to a file; since file name not given on command line, program must ask what file to use
proj111 -w logfile.dat -r infile.dat OR proj111 -r infile.dat -w logfile.dat	reads commands from infile.dat, writes commands with parameters to infile.dat
proj111 -r infile -w	reads commands from infile.dat; writes comands with parameters to a file; since log file name not specified, user must be asked for the filename

Notes

• Global variables may not be used in this project. Use parameters to communication data into procedures.

• 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