CS 3020
Fall Semester 2014
WEB 1250 T
Instructor: Thomas C. Henderson
Understand the motivation for computer science research and learn about current research activity at the School of Computing :
The prerequisite is an interest in computer science research and a willingness to explore a variety of research activities.
We will look at the basic nature of research and hear from a number of School of Computing faculty on their specific research activity.
Students will not develop codes in this class.
No required text.
There are 2 major types of assignments:
See: Survey Assignment
The
lectures will cover the text on the following schedule (may vary some
during
semester to accommodate progress):
|
Date |
Topic |
Speaker
|
Abstracts |
|
|
|
|
|
|
August 26
|
Introduction to Research
|
Tom Henderson |
Abstract: A1 |
|
September 2
|
Bugs: Black Ice on the Road to Exoscale |
Ganesh Gopalakrishnan |
Abstract: A2 |
|
September 9
|
What is Program Analysis? |
Matt Might |
Abstract: A3 |
|
September 16
|
Intelligent Autonomous Machines |
Tom Henderson |
Abstract: A4 |
|
September 23
|
Topics in Cloud and Networking Research |
Kobus van der Merwe |
Abstract: A5 |
|
September 30
|
Computer Security and Privacy: Beyond the Desktop |
Tamara Denning |
Abstract: A6 |
|
October 7
|
New Security Paradigms: Device Fingerprints and Wireless Link Signatures! |
Sneha Kasera |
Abstract: A7 |
|
October 14
|
Fall Break |
N/A |
|
|
October 21
|
Computer Architecture Challenges |
Rajeev Balasubramonian |
Abstract: A8 |
|
October 28
|
Streaming Matrix Approximation |
Jeff Phillips |
Abstract: A9 |
|
November 4 |
The Shape of Information |
Suresh Venkatasubramanian |
Abstract: A10 |
|
November 11 |
Open-source and open-platform software developments in imaging research |
Guido Gerig |
Abstract: A11 |
|
November 18 |
Developing Efficient Graphics Technologies |
Cem Yuksel |
Abstract: A12 |
|
November 25 |
Discussion |
Tom Henderson |
|
|
December 2 |
Introduction to Image Processing |
Ross Whitaker |
Abstract: A13 |
|
December 9 |
Visualizing data: Why an
(interactive) picture is worth a 1000 numbers |
Miriah Meyer |
Abstract: A14 |
|
|
|
|
The lectures will focus on research and the assignments will cover some aspect of that. Assignments will usually be available out on Tuesday and due a week later.
Thomas C. Henderson, Professor
E-Mail:
Phone:
801-581-3601
Fax:
801-585-3743
Office Hours (2781 WEB): By appointment.
None
E-Mail:
Phone:
Fax:
Office Hours :
The grading distribution will be as follows:
You are expected to make a good effort on all assignments and in-class discussion based on a careful understanding of the assigned material. I will assign a grade based on how reasonable your answer is given the difficulty of the assignment, the time required, and the style and content of the solution. My goal is to look at all your work, and to assign a grade based on your participation, effort and results. It's better to ask questions before and during an assignment, than to try and understand what went wrong after it's due. The proportions given above delineate how I intend to apportion the weight of the various work in the course.
Unless otherwise stated in an assignment, all assignments will be due by classtime on the assignment due date. You should handin PDF's. The time that we use for an assignment is the submit time. I may occassionally ask for other information.
See the Code of Student Rights and Responsibilities, or the Class Schedule for more details.
Appeals of Grades and other Academic Actions
If a student believes that an academic action is arbitrary or capricious he/she should discuss the action with the involved faculty member and attempt to resolve. If unable to resolve, the student may appeal the action in accordance with the following procedure:
No late work is accepted.
The purpose of the assignments is to improve your skills at solving problems and demonstrating that you understand the class material. Collaboration with other class members is acceptable in understanding problems or software tools. For any individual assignments or work turned in, you must do your own work. Using someone else's work or giving someone else your work is considered plagiarism and will be dealt with using standard College and University procedures (i.e., failure of assignment and class). The SoC policy states: "As defined in the University Code of Student Rights and Responsibilities, academic misconduct includes, but is not limited to, cheating, misrepresenting one's work, inappropriately collaborating, plagiarism, and fabrication or falsification of information. It also includes facilitating academic misconduct by intentionally helping or attempting to help another student to commit an act of academic misconduct. A primary example of academic misconduct would be submitting as one's own, work that is copied from an outside source." (See cheating_policy.pdf and SoC_ack_form.pdf in Link to Class Info and Docs.)
See university web page for the full academic calendar (Calendar web page). See the university web page for a copy of the withdraw guidelines as well, or see the Student Code.
See the college web page for more Guidelines.The University conforms to all standards of the
The
All written information in this course can be made available in
alternative
format with prior notification to the Center for Disability
Services.