CS 315: Algorithms & Data Structures (Spring 2009)

TA: Sandeep Chauhan (sandeep@cs.utexas.edu)

TA: Joohyun Kim (scimitar@cs.utexas.edu)

TA: Sangmin Lee (sangmin@cs.utexas.edu)

(New material will be added over time.)

How to Turn in the Assignments

To submit your assignments, login to your CS department Unix account, cd to the directory where your source files are¹, and type the following command:

turnin --submit <TA> <project> <filenames>

turnin --submit <TA> <project> <directory>

where <project> is proj2, proj3, ... (The first programming assignment is actually proj2)

and <TA> depends on which homework you turn in. The three TAs will take turn to grade all of your homeworks. The following is who you should turn in your assignment

¹ If you choose to do the assignments at home, you will need to transfer your files to the departmental machines before using turnin. One way is to email them to yourself as attachments. Another is to use a FTP program such as the SSH client available from Bevowere.

For example, to submit Assignment 2, Assignment 4, or Assignment 6, you would type:

turnin --submit sangmin proj2 <your_codes> README OR

turnin --submit sandeep proj4 <your_codes> README OR

turnin --submit scimitar proj6 <your_codes> README

You are expected to turn in a README file, indicating your name (for us to identify you on the roster), the departmental computer you have tested your code on², any parts of the assignment you were unable to complete, the TA session you currently register, and anything else you would like to mention about your program.

TA sessions and who takes in charge of each session is like following:

² You may develop your programs on any machine of your choice, but make sure they run on the departmental computers before turning them in. This is not expected to be a problem with Java, but test it first just in case.

Direction to My Office

Take the elevator in ENS to the lower basement (LB). When doors open, exit right and keep going down the hallway. It will curve to the right and you'll come to ENS 31NR (on the left). Go through 31NR to a smaller room, which is 31NQ. There are six desks, marked 1 through 6.

A Note on Using Java on the Department Machines

Currently we support two versions of java:

* "J2SE 5.0" (a.k.a. java 1.5.x)
** installed at /lusr/java5
** documentation available at /lusr/java5/docs/
** source available at /lusr/java5/src

* "Java SE 6" (a.k.a. java 1.6.x)
** installed at /lusr/java6
** documentation available at /lusr/java6/docs
** source available at /lusr/java6/src

Java's product naming conventions are confusing.  See this page for an explanation.

We are currently in a transition phase this semester, upgrading from one version 
of Ubuntu Linux to another (dapper drake -> hardy heron).  With this upgrade, 
the default version of java has changed.

On the older systems (dapper drake), typing 'java' will get you /lusr/java5/bin/java.  
On newer systems (hardy heron), typing 'java' will get you /lusr/java6/bin/java.

To determine which java is first in your $PATH, use 'which':

   $ which java
   /lusr/java6/bin/java

Currently, all public lab machines have been upgraded to hardy heron (ie, java 6), 
except for the machines in ENS 31NR which will remain as dapper drake machines 
until the Christmas break.

To determine which version of Ubuntu a given machine is running, use 'lsb_release':

   $ lsb_release -c
   Codename:       hardy

If you are logging in remotely and need a list of dapper drake or hardy heron machines,
running 'cshosts linuxpub' will list public dapper drake machines, and running 
'cshosts hardypub' will list public hardy heron machines.