|CS 758 Course Wiki: Fall 2016||Main »
On this page... (hide)
The project will have you do original research in parallel computing (hardware, software, theory, or combination). You should work in groups of two. With my permission, project groups of three or one are permissible. You will be graded on how well you define your problem, survey previous work, design and conduct experiments, and present your results. The goal to shoot for a conference paper, like the ones in your reader. Since time is limited, however, the above goal is hard to reach, and I will reward those that aim high even if they do not completely succeed. The key is insuring that some aspects of your work are completely done; it is very hard to get fair credit for a project where nothing really works.
I normally accept no late assignments. For this project, papers turned up to 24 hours hours late will be accepted with a 25% penalty. Don't avail yourself of this option; your hard work deserves full credit.
This project should be more significant than a CS/ECE 752/757 project, as you have more time and experience.
You should prepare 2-3 project ideas that you would like to pursue. It is fine to have a preferred topic, but you must think about at least one alternative.
I strongly recommend that you come by my office hours before finalizing your project proposal. My experience can aid you and not re-discovering many past mistakes. If you send your proposal by email, use subject: [CS 758] Project Proposal.
Proposals should be about two pages long. They should include:
Email me DRAFT slides by 6:00am and final slides by 11:00am on your presentation day. Use subject: [CS 758] Project Preliminary Talk.
Groups will present a 10-minute talk using 8-10 slides, with at least one slide on each of the following:
Please, practice your talk to make it better and see how long it is. Have a plan for what slides to skip if you get behind. Please see Oral Presentation Advice, including David Patterson's How to Give a Bad Talk and |K. Compton and M.L.Chang's Terrible Presentations (...and how to not give one).
Groups will meet with the instructor (Wood's office 6369 CSS) during Lecture time slots to be assigned. By 9:00am of the DAY BEFORE the meeting, groups should email the instructor a progress email--1-2 pages--describing what is done and what needs to be done. Use subject: [CS 758] Project Meeting. Concentrate on describing sub-tasks completed, rather than the tasks started. For example, say ``completed simulator modification to watch and fake FOO rather than saying ``started simulator modifications.
Each project group will present a previously-published research paper that is related to your project. There is no better way to learn something than to teach it! The goal of this presentation is to describe the key methods and findings of the work and how it relates to your project. Presentations will be in class on designated lecture days in November. Each presentation will have EXACTLY a 25 minute slot, so plan for 15-18 minutes without interruptions. Please, practice your talk to make it better and see how long it is. Have a plan for what slides to skip if you get behind.
Noon, Monday Nov 5th: Email instructor with 1st, 2nd, and 3rd choices for paper to present (include pdf or a link unless you know I know the paper). I will assign papers first-come-first-serve. Please, talk to me earlier, especially if you have topic ideas, but no specific paper. T - 2 Days: Send instructor presentation draft (First thing Monday for Tuesday presentations). T - 2 Hours: Email instructor presentation. (Make sure it is compatible with Powerpoint 2011 for Mac or bring your own laptop).
Using subject: [CS 758] Paper Presentation., email me draft slides by 6:00am the day of your presentation and final slides 90 minutes before the presentation.
We will divide up the last few lectures into 25-minute conference-style talks. Depending on class size, some talk may be scheduled at alternative times. All group members should deliver part of the talk. The talk should give highlights of the final report, including the problem, motivation, results, conclusions, and possible future work. Time limits will be enforced to let everyone present. Please, practice your talk to make it better and see how long it is. Have a plan for what slides to skip if you get behind.
Using subject: [CS 758] Project Final Talk., email me draft slides by 6:00am the day of your presentation and final slides 90 minutes before the presentation.
Reports should consist of an abstract, body and optional appendices, much like a conference paper. The abstract should summarize the contributions of the report in one or two paragraphs. The length of the body should be the equivalent of 15-20 pages at double-spaced 10-point. Additional supporting material of any length can be put in appendices. I will read the body and only skim appendices. See your reader for examples.
Put final reports in my mailbox and email PDF with subject: [CS 758] Project Report.
You are encouraged to come up with your own topic. Ideally, the topic will be related to your current research interests.
There can be value in combining your project with other work in one of two ways. First, if you have active research in a related area (e.g, an RA), you can do a deeper project by combining your current (supported) research with your course project. Second, it is also possible to do a single multi-disciplinary project to satisfy multiple courses (e.g., CS736). However, this must be coordinated with the other instructor(s) and you will be expected to do two (or more) projects worth of work. In all such cases, it is imperative that such overlaps be disclosed at the proposal stage so that we can address the scope of research that will be required.
|Page last modified on October 23, 2013, at 03:49 PM, visited times|