Carnegie Mellon University
15-826 Multimedia Databases and Data Mining
  Spring 2017 - C. Faloutsos

GRADING SCHEME - default projects

updated: 4/19 (see yellow highlights)

1. First Deliverable: Phase 1 - The Literature survey

Your survey should be approximately 6-8 pages long, typed (eg., latex/pdf/msword), 12pt size font, neat, and with pictures if they seem useful (`idraw', `xfig', 'tikz', are good choices). 

Important points - check-list:

  1. Grading scheme: 90% for the survey; 10% for plan of activities - who-does-what
  2. Use the latex template - follow its outline.
  3. Attribution: list which group member did (or will do) what
  4. Your survey should have at least 3 papers or book chapters per group member (outside of the course reading list).
  5. Check grammar and syntax (small penalty for each typo / grammar error).


2. Second Deliverable: Phase 2 - The Progress Report

This should be a 10-15 page long report, and it serves as a check-point. It should consist of the same sections as your final report (introduction, survey, etc), with a few sections `under construction'. Specifically, the introduction and survey sections should be in their final form; the section on the implementation should be  finished; the sections on the experiments and conclusions will have whatever results you may have obtained, as well as `place-holders' for the results you plan/hope to obtain.

Grading scheme for the project report:

Reminders, for all projects:

3. Third deliverable: Phase 3 - The Final Report

The grade of the final phase of the project will have the following components:

  1. writeup: there, you would describe your discoveries/insights/experiments. Your final report is expected to be a 20-30 pages.
  2. software: packaging, documentation, and portability. The goal is to provide enough material, so that other people can use it and continue your work.

3.1. Grading Scheme for Final Report

3.1.1. Two-member teams:

3.1.2.Single-member teams:

 As above, with reduced load for the following tasks:

3.2. Specifications for packaging of software:

Please create a tar-file, like this sample package ( use  gunzip ; tar xvf). Check-list:
  1. after un-tar-ing, the command 'make' should compile your system, install it if necessary and run a small demo on a sample input file (included in your package)
  2. it should have a README file, corresponding to the `user's manual': This file should describe the package in a few paragraphs, as well as how to install it and how to use it.
  3. it should have a directory DOC, with your writeup, and your foils (in your favorite form: latex, pdf, powerpoint, ms-word)
  4. 'make paper.pdf' should create the corresponding version of your writeup (skip this step, if you use ms-word)
  5. `make clean' should eliminate all the derived files (*.o, *.class, *.aux, etc)
  6. `make all.tar' (or 'make') should create a  tar/zip-file,  ready for distribution.
  7. please make sure that your package includes only the absolutely necessary set of files!

3.3. Final project report - what to hand in:

On the announced due date on the schedule,
  1. bring a hard copy of the writeup in class,
  2. a (hard copy) of the graded phase-2 report and graded phase-1 report and
  3. upload on black-board your tar/zip-file before class. 
    1. Only one team-member need to upload the file.
    2. If the file is too large (it shouldn't - omit the datafiles), contact the instructor.

Created: Feb. 12, 2017; last modified: April 19, 2017 (items in yellow highlight),  by Christos Faloutsos.