CAS CS 552 - Fall 1999
Operating Systems
Guidelines on Electronic Submissions of Programming Assignments
What to submit:
The program you submit should work correctly and be documented. You
should submit both a hard copy and an electronic copy (see below) of the
following:
-
a program listing containing in-line documentation (i.e., comments)
-
a separate file (a page or so) describing the overall program design, a
verbal description of "how it works", and design tradeoffs considered and
made. Also describe possible improvements and extensions to your program
(and sketch how they might be made)
-
a separate file describing how to compile and run your program. Specify
the compiler you used and the type of machine(s)/operating system(s) on
which you have successfully run your program
-
a separate file describing the tests you ran on your program to convince
yourself that it is indeed correct. Also describe any cases for which your
program is known not to work correctly
How to submit an electronic copy: (Submit only
plain ASCII files!)
[adapted from D. Metcalf's note]
To submit your programming assignments, use the gsubmit program
from your csa account.
gsubmit is an electronic file submission engine which will
submit files or directories of files to the grader so they can be marked.
Every file submitted by a given student for a given assignment should
have a unique file name. If a file is submitted with a duplicate name it
will either overwrite the file or generate an error message.
To make it easy for the grader to find the files relating to a specific
programming assignment, all files for each assignment should be stored
in a subdirectory called pa1, pa2, pa3, etc.
and the entire directory should be submitted.
To submit an assignment:
Create a subdirectory "pa#", where # is the programming assignment number.
This is done using the mkdir command:
mkdir pa5
Copy all files necessary for that assignment into the new subdirectory,
using the cp command:
cp prog1.java pa5
Be sure to copy only the files you need to submit into this subdirectory.
Use gsubmit to submit the entire subdirectory:
gsubmit cs552 -cp pa5
If submission is successful a status message will be printed.
To submit a file to an already-submitted subdirectory:
If you only submitted part of the assignment and would like to add another
file:
To submit a file README.txt to subdirectory pa5,
type (at the unix prompt):
gsubmit cs552 -cp README.txt pa5
To resubmit a file:
To resubmit a file prog1.java in subdirectory pa5, first unsubmit
the file:
gsubmit cs552 -rm pa5/prog1.java
then resubmit it:
gsubmit cs552 -cp prog1.java pa5
To list all files which you have submitted:
To list all files which you have submitted, type:
gsubmit cs552 -ls
To look at a file which has already been submitted:
To look at a file which has already been submitted, type:
gsubmit cs552 -cat prog1.java
You can store this in a file foo by typing
gsubmit cs552 -cat prog1.java > foo
Where do submitted files go?
Each student who submits an assignment has a subdirectory created to hold
his/her files, in a directory for the specified course. This is called
the student's "submission spool directory".
How can the grader tell when a file has been submitted?
Every gsubmit command is automatically logged in a log file, along with
a time stamp.
For further information:
Note - The information in this document is taken from the gsubmit man page.
For further information type man gsubmit.
Back to
CAS CS 552 home page