Frequently Asked Questions (FAQ) and their answers
General Course Info is in Section 7
cd ~cs6100/public_html/PySat/tests/ and then type ./testfile.py TestFiles/sat2.cnf (for instance)
. For more details, see the README there. (I had to copy over argparse.py into the
tests directory. I did not
come as a default on the lab3 machine. It seems to work.)
This course 1is meant for graduate and advanced undergraduate students (unless otherwise allowed by the instructor).
The topics selected for the Spring 2012 offering are the following:
These topics are intimately related, and all pertain to one’s ability to understand and design correctly functioning systems, and describe the workings of these systems clearly. The onus is on you (the student) to develop a clear understanding of what the course is about, and how you can best tailor the course (influence what will be lectured, and negotiate degrees of freedom that you are comfortable with) to maximize your learning. Please bear in mind that
This is a project-based class. Attendance to the lectures is required, unless you excuse yourself through an explicit email before the lecture begins. A formal roll-call will not be taken; however, prolonged absences without a reason will be grounds for failure.
Interactions during lectures or through email will earn you participation points (10% of the course grade). There will be one midterm (20% of the course grade). The rest of the course grade is based on assignments (20%) and a project (50% of the course grade). The final grading will be based on a curve, typically with each percentile of 10 binned into a grade category (e.g., 90-100: A, 80-19: B, etc.)
The projects are meant to be done either individually or in groups of size 2 (if there is a very well motivated reason for a group-size of 3, that may be permitted). There will be a required project presentation during the last week of classes. Points toward your project will be assigned based on the quality/novelty of the work itself, your presentation, and your report. Projects are required to be selected during the first two weeks of classes, from the list of topics given in Section 5 (to be refined soon; these are general topics for now).
There will be 1-1 project meetings held during the third week of classes. Changes in project focus/topic can be negotiated during these meetings. Generally, these meetings will be scheduled to occur during office hours; however, lecture-time may also be set apart.
Proper citations are expected whenever external public-source material is referred to. Help from your classmates or friends is allowed to the extent that it teaches you the basic methods/approach – and it must be acknowledged in your presentations, assignments, etc. All the worked turned in must be original. In particular, for specific problems assigned, and unless otherwise specified, you must be solely responsible for the creation of the actual solution, code module, etc.
The course will be based on lecture notes, and the references below:
My known commitments are below. Some of these days, classes may actually be held (so don’t assume an automatic “no class” unless it is a holiday).
A link to the SoC Policy Statement of Academic Misconduct appears at:
http://www.cs.utah.edu/internal/cheating_policy.pdf.
If you have not done so, please read the above policy, print the following acknowledgement form, sign it, and hand it over to the SoC office or me:
http://www.cs.utah.edu/internal/SoC_ack_form.pdf
Reasonable accommodation will gladly be provided to the known disabilities of students in the class. Please let the instructor know the situation as soon as possible. If you wish to qualify for exemptions under the Americans with Disabilities Act (ADA), you should also notify the Center for Disabled Students Services, 160 Union Building.
This document was translated from LATEX by HEVEA.