Final Project Guidelines
EE516 -- Computer Speech Processing -- Spring 2009
Oral Presentation Format
- Presentations will be on June 9, 4:30-6:30PM in rm EEB 003.
- Each group will have about 15 minutes for their presentation, plus an
additional 5 minutes for questions. Presentations should
describe the project, the approach, the reasons behind this choice, and the
official results. Contrastive results or demos are highly encouraged.
- Please provide three hardcopies (one for each instructor) of the slides in
class before the presentation. Preliminary reports and slides may also be
e-mailed if available earlier on Tuesday.
- Students in the class are expected to ask at least one question of
of one group. Constructive feedback is also encouraged.
Written Report Format
- The project reports should be ready by the time of the project
presentation. If there is significant feedback during the project
presentation, the reports can be revised and submitted for grading no later
than 5pm on Wednesday, June 10.
- The report should be no more than 10 pages double spaced, including
references, figures, tables, etc. This is a maximum - do not feel
obligated to make it this long. (Reduce the length by half if you don't
double space; use 11pt or 12pt font.)
- Use standard bibliographic form when citing other work.
- Attach source code to your report. The source code is not included in the
length suggestions.
- The report should be written in the style of a paper you might
submit to a journal and include:
- title and abstract
- introduction (problem statement, motivation, overview)
- background discussion of work you build on or
will compare to
- description of algorithm(s)
- description of experimental paradigm (test and training data
division, etc)
- experimental results
- discuss results and comment on things that you learned,
possibly mention things that would be good to try in the future
- references
- The written report will be graded based on a mixture of
style (i.e. points will be subtracted for typos,
grammatical errors, undefined variables, etc.),
organization and completeness (i.e. addressing all the points listed
above), and clarity in description of the technical approach.
This page is maintained by Alex Marin (amarin@u). Last updated on June 5, 2009.
Back to the EE516 Course Information Page