CSCE 479/879 (Fall 2019) Project Rules and Ideas


From the syllabus:

In this course you and your team will do a substantial project, in which you will characterize a significant problem amenable to a deep learning solution, study the related work to this problem, develop one or more deep learning approaches to this problem, and evaluate your approaches.
You will summarize your project results in a written report and an oral presentation. The written report must use a professional writing style similar to that found in a refereed conference or journal (e.g., ACM, IEEE, ICML, ICLR, NeurIPS), including abstract, introduction, summary of related work, your contribution, references, and an appendix (if necessary). The oral presentation will be to the entire class at the end of the semester: during the fifteenth week (December 9–13), and if necessary, during the fourteenth week (December 2–6). You will submit your written report no later than 11:59 p.m. on Sunday, December 15. In accordance with UNL policies, you have now been informed in writing of the nature and scope of this project prior to the eighth week of classes.
Seven to eight weeks into the semester (early to mid-October), we will set a deadline for submission of proposals on your projects. You must do this in order to get full credit for your project, and you must get our approval on your proposal before starting work on your project. A couple of weeks later, you will submit to us an initial progress report and meet with us for a check-in on your project. For this progress report, you will have your data sets downloaded and preprocessed, and have all necessary libraries and environments installed (or at least have the installation requests pending with HCC). A few weeks after that, you will submit to us your second progress report. This report will include initial experimental results and will serve as an early draft of your progress report, so it will also include your problem definition, related work, and discussion on your approaches.

Projects are officially due by 11:59 pm on Sunday, December 15. See the rules on projects for more information.


Project oral presentations are the weeks of December 2 and December 9. See the presentation schedule for more information.


Second project progress reports are due Sunday, November 17. You will submit it in pdf format via handin Canvas. The report, which is considered an early draft of your final report, should include:

  1. A discussion of the learning problem, i.e., what exactly is to be learned, and motivation for the problem.
  2. A summary of related work.
  3. A discussion of your approaches.
  4. A discussion your experimental results so far, including the setup and results.
  5. What you plan to work on for the rest of the semester.

First project progress reports are due Sunday, November 3. You should submit it to sscott@cse and equint@cse in text format in the body of an email via Canvas before 11:59 pm on that day. The report should include:

  1. A discussion on all data sets, libraries, etc. that need to be set up for your project to be successful. You should also discuss the status of all such installations (pending HCC installation requests, etc.).
  2. A summary of what you've accomplished on your project so far.
  3. A description of what major elements remain for your project, including what is left over from your proposal as well as any new elements that you've added since your proposal.
  4. An overview of any significant hurdles that have arisen.
  5. A list of what questions you need answered to move forward.
On Monday, November 4, we will spend the hack-a-thon period reviewing each group's check-in report.

PROPOSAL DEADLINE: The proposal submission deadline is Sunday, October 20. You should submit it to sscott@cse and equint@cse in text format in the body of an email before 11:59 pm on that day. Your proposal will consist of 4–5 paragraphs and will follow The Heilmeier Catechism, a set of questions used to evaluate proposed research programs:
  1. What are you trying to do? Articulate your objectives using absolutely no jargon.
  2. How is it done today, and what are the limits of current practice?
  3. What is new in your approach and why do you think it will be successful?
  4. Who cares? If you are successful, what difference will it make?
  5. What are the risks?
  6. How much will it cost?
  7. How long will it take?
  8. What are the mid-term and final "exams" to check for success?
Specifically, your proposal should include:
  1. A brief statement of your project topic (HC1).
  2. Motivation for your topic: why it is important and interesting (HC3, HC4). If your work is in an application area, be careful to avoid technical jargon from that area that is outside of computer science. If you must use a term, define it as carefully and simply as possible.
  3. A precise work plan: what you plan to do, what data sets you will test on, how you will evaluate performance, what is your timeline, etc. (HC5, HC7, HC8).
  4. What resources will you need, including data sets and libraries that need to be installed on HCC (HC6).
  5. At least three references (at least two published journal or conference papers) (HC2).

Project Ideas

The following is a list of possible projects, suggested by a variety of individuals. If you want to know more about a particular one, let us know and we can put you in contact with those who can provide more details.

You are welcome to suggest your own project as well, e.g., one related to your own research. It should contain some form of an experimental component, be relevant to the course, and be a non-trivial extension beyond what we covered in class.

Classification