General Information
ofessor: Micah Beck
- Claxton 317
- mbeck@cs.utk.edu
- Office hours by appointment. Send email.
TA: Mitch Horton
- Info on his home page -- office hours by appointment.
Class TR 12:40-1:55 in Claxton 205.
No formal lab, although there is reserved lab time
in Claxton 105, Mondays from 2:30 - 5:50.
Grading is roughly 50% labs, 25% exam 1, 25% exam 2, although that
may change.
Lab grading policy will be set by the TA's.
Lab questions should be directed to the TA's first, and then me.
Lecture Notes
There are lecture notes for many of the lectures in the first third
of the course. These will be put on the
web with a pointer hanging off the class home page. The point of
lecture notes is to tell you what went on in class. If I covered
material from the book, the notes will specify the sections. If the
material is not in the book, the notes will contain instructional
reference material.
All programs that I go over in class should be online in a
directory for that class (~mbeck/classes/cs560/notes/XXX).
The point here is that you don't have to try to copy
them down in class. That is a waste of your time, which is best
occupied otherwise.
I will try to make lecture notes available as soon as possible after
class.
Labs
The labs are where you are going to learn the most in this class.
They are going to require far more than 3 hours per week. Thus, you
will have to use evenings or weekends to get machine time. Work this
out. Some classes will let you use extra machines if they are available
and you are quiet. I believe there are no labs scheduled during evening
and weekend hours. You may also want to explore remote login from UTCC
machines, or from your own terminal and modem if you own one.
Ask the TA's about how to log in remotely.
Handing in Labs
Labs will usually be due at 11:59:59PM on the specified night.
Once you have finished writing your code, you must document it,
create a makefile for it, and a shell script to show that it works.
To submit homeworks, you should go through the following steps:
- Put all your work in one directory.
- cd to that directory.
- Remove all extraneous files from this directory.
This includes all .o files, and all executable
files (e.g. a.out).
- Run the program /home/cs560/bin/scripts/submit,
and follow its instructions. This will create your homework
submission file. Mail that to your TA's.
You may talk with the TA's, other students, or me about your
homeworks, but do the programming on your own. Copying other
students' code is considered plagiarism.
Speaking of Plagiarism
You should protect the directories that your homework is in so that
no one but you can read it. I have seen too many instances
of copying recently, and it can be prevented if you protect your
directory. If we discover copying this time, both the copier
and the copyee (?) will be penalized severely. You have been
warned.
Dlists, rbtrees, etc.
I assume that you have taken CS360, and that you already know about
the libraries for fields, dlists, and red-black -trees.
These are implementations
of data structures that can make your lives much simpler. If you are
not well-versed in these things (the fields library is less important,
but easy to learn), then you should read the associated lecture notes
from CS360, and practice by doing the relevant labs from CS360.
The TA's will be happy to help you with these and give you feedback if
you desire. The main link:
http://www.cs.utk.edu/~plank/plank/classes/cs360/360/notes/Libfdr/.