CMPS 101
Programming Assignments
Programming Projects
pa1:  pdf, word   Due Tuesday July 1,  10:00 pm    
pa2:  pdf, word   Due Thursday July 10,  10:00 pm  Extended to Friday July 11, 10:00 pm
pa3:  pdf, word   Due Wednesday July 23,  10:00 pm  Extended to Thursday July 24, 10:00 pm
pa4:  pdf, word   Due Saturday August 2,  10:00 pm   Extended again to Monday August 4,  10:00 pm 
pa5:  pdf, word   Due Tuesday August 12,  10:00 pm  Extended to again Thursday August 14, 10:00 pm

UCSC Computer Accounts
It is a requirement of this course that all students have an active UCSC computer account.  If your account is not already activated, go to the UCSC portal:  http://my.ucsc.edu, and log in using the User ID and Password that were sent to you by the Registrar's Office, then click on the link labeled Activate UCSC Account.  Logon to the University's Unix Timeshare host unix.ic.ucsc.edu to access your account.  You may develop your programming projects on any platform you like, but you must port them to the IC-Solaris Unix environment to submit them.  Since your projects will be evaluated on the IC-Solaris platform, it is urged that you thoroughly test all programs in that environment before submission.  The host unix.ic.ucsc.edu is administered by Instructional Computing.  Contact their help desk for assistance with your account.

How to Submit a Programming Project
To submit a programming assignment, log on to unix.ic.ucsc.edu.  From within the directory where your program resides, type the following at the Unix prompt (%):
% submit  cmps101-pt.u08  assignment_name  file1  file2   ...
In the above example file1, file2, etc are the files to be submitted, and  "assignment_name" is the name of the assignment, such as pa1, pa2, etc.  All assignments in this class require that you submit multiple files, including a README and Makefile.  If you decide that you don't like what you submitted and want to submit a better version of the assignment (before the due date of course), just submit again using the same file name.  The new submission overwrites the old. 

To verify that an assignment was accepted by the system, and to check what was actually submitted, use the peek command:
% peek  cmps101-pt.u08  assignment_name
You'll get a listing of all files which have been submitted for that assignment with the option of viewing the contents of each file.  If you just want to check and see if you are using the submit and peek commands correctly, submit some dummy file to the assignment name "junk".  For example
% submit  cmps101-pt.u08  junk  dummy_file
then run peek on assignment "junk".  Files submitted in this way will not be graded or even looked at. 

Required Final Test of Your Project
In addition to running  the peek command, the following test is required on all programming projects in this course.  First create an empty directory in your own account space, call it 'test' say.  Then cd to the homework directory for a particular assignment.

% cd afs/cats.ucsc.edu/class/cmps101-pt.u08/assignment_name/your_user_id

This is the directory where the submit command places your files.  (In fact, submit is just a script that encapsulates the cp command, along with some error checking.)  Look around and see if all the files you think you submitted were in fact submited.  Make sure that the most recent version of each file is the one you submitted.  Copy all of the submitted files back to your test directory.

% cp * ~/test

Now cd back to your test directory and do gmake to compile the project one last time.  (Do not do gmake in our homework directory, since that would create unwanted files which you will not be able to delete, and will therefore cause you to lose some points!)  You will see just what the grader will see when he tries to compile your project.  Put yourself in the mind of the grader, and evaluate your project critically.  Does the project compile?  Have all required methods been implemented?  Test the project on your own randomly chosen inputs, not just the inputs mentioned in the project description. 


If you find any errors, please report them to: ptantalo@soe.ucsc.edu

webmaster@soe.ucsc.edu

Back to the SOE Class Home Pages
Back to the SOE Home Page