CSE6242 / CX4242, Fall 2017
Data and Visual Analytics
Georgia Tech, College of Computing

Project

---

Grading & Schedule

1. Proposal (10%)
2. Proposal presentation (10%)
3. Progress report (15%)
4. Final poster presentation (10%)
5. Final report (55%)

See course homepage's schedule table for all deliverables' due dates.

Teaming Important!

The work will be carried out in teams of 4-6 persons.

A team may consist of both on-campus and distance learning students (Q or Q3 section). All such teams will have 3-day lags for all their deliverables. For proposal presentation and final presentation, those teams can choose to do that in class (physically) or submit videos (see details below).

We will grade grad projects and undergrad projects separately; we generally expect grad projects to include more detailed analysis, comprehensive results, etc.

Polo recommends each group to consist of either all grads or all undergrads. The main reason is that grads and undergrads have different expectations and work schedules. If you want to form a group with both grads and undergrads:

1. We will grade that group as if all members are grad students
2. Every member MUST fully understand the potential challenges in coordinating work schedules (e.g., grads usually take class on TH, undergrads on MWF) and expectations (e.g., course grades are generally very important for undergrads)

It is optional for an auditor to work on a project. When an auditor joins a team, the auditor MUST contribute to the team as an enrolled student, and the whole team will be graded as if everyone is enrolled, otherwise it will be unfair to other teams — every team member must fully understand and accept this requirement.

Choosing a Topic

Pick your own topic:

• You need to justify that the topic is interesting, relevant to the course, of suitable difficulty.
• Required components:
  1. at least one large, real dataset;
  2. some non-trivial analysis/algorithms/computation performed on the dataset (e.g., computing basic statistics, like average, min/max will not be enough); and
  3. an interactive user interface that interact with the algorithms (can be visual, voice-controlled, on tablet, desktop, etc.).

Harder way:

• Joint projects with other courses might be negotiable. You must obtain the instructor's approval, and you need to clarify exactly what will be done for this course that is on top of and different from what you will do for the other course.
• Projects related to your dissertation/master-project are also possible, as long as there is no 'double-dipping', i.e., you clearly specify what the project will do, in addition to what you were planning to do for your thesis anyway.

Once you have selected a topic, you should do some background reading so that you are capable of describing, in some detail, what you expect to accomplish. For example, if you decide that you want to implement some new proposal for a multidimensional file structure, you will have to carefully read the paper that proposes similar structures, pinpoint their weaknesses, and explain how your approach will address these weaknesses. Once you have read up on your topic, you will be ready to write your proposal.

Proposal

Your proposal should answer Heilmeier's questions (all 9 of them; see list below); if you think a question is not very relevant, briefly explain why. In other words, your proposal should describe what you plan to do (the problem to address), why you want to do it, how you will do it (what tools? e.g., SQLite, PostgreSQL, Hadoop, Kinect, iPad, etc.), how your approach is better than the state of the art, why it may succeed, and when it does, what differences will it make, how you will measure success, how long it's gonna take, etc.

9 Heilmeier questions (source)

1. What are you trying to do? Articulate your objectives using absolutely no jargon.
2. How is it done today; what are the limits of current practice?
3. What's new in your approach? Why will it be successful?
4. Who cares?
5. If you're successful, what difference and impact will it make, and how do you measure them (e.g., via user studies, experiments, groundtruth data, etc.)?
6. What are the risks and payoffs?
7. How much will it cost?
8. How long will it take?
9. What are the midterm and final "exams" to check for success? How will progress be measured.

Your proposal should be no more than 1000 words, excluding titles, section names, reference list, etc., but including the literature survey. It should use 12pt font, typed in PDF format (can be created using any software, e.g., LaTeX, Word), and with figures, tables, etc. whenever useful. It should be self-contained. For example, don't just say: "We plan to implement Smith's Foo-Tree data structure [Smith86], and we will study its performance." Instead, you should briefly review the key ideas in the references, and describe clearly the alternatives that you will be examining.

Grading scheme & Submission instructions

• 60% for the survey
• 30% for innovation
• 10% for plan of activities
• For every Heilmeier question that's not mentioned, deduct 5%.
• You may consider organizing your proposal based on the Heilmeier questions (e.g., each section addresses one question)
• Your survey should have at least 3 papers or book chapters per group member (outside of any required reading for the class).
  • Short papers, like PNAS, Nature, Science papers, count as 0.5.
  • Copying the abstract of the papers is obviously prohibited, constituting plagiarism.
  • For each paper, describe
    
  • (a) the main idea,
    
  • (b) why (or why not) it will be useful for your project, and
    
  • (c) its potential shortcomings, that you will try to improve upon.
• You may use any citation style (e.g., APA, Chicago). Google Scholar supports a wide range of citation styles; it also provides BibTeX (needed if your team is using LaTeX).
• Clear problem definition: give a precise formal problem definition, in addition to a jargon-free version (for Heilmeier question #1).
• Provide a plan of activities and time estimates, per group member. List what each group member has done, and will do.
• Team's contact person submits a softcopy, named teamXXproposal.pdf, via T-Square (i.e., that person submits for the whole team), where XX is the team number (e.g., team01proposal.pdf for team 1)
• [-5% if not included] Distribution of team member effort. Can be as simple as "all team members have contributed similar amount of effort". If effort distribution is too uneven, I may assign higher scores to members who have contributed more.

Proposal Presentation

• 2 min per team. See this Google spreadsheet for your team's presentation date and time (link on Piazza). Presentations take place during class time. First presentation starts at 4:30pm SHARP.
• If you overrun, we will boot you off the stage and deduct 5% of your presentation grade.
• Two teams can swap their presentation dates if both teams agree; no need to ask Polo for permission. Both teams MUST update the Google spreadsheet with the new dates.
• Attendance is mandatory. Lateness and absence will be noted; marks may be deducted for no-show. If you cannot attend, let Polo and TAs know through a private post on Piazza.
• If you team has a Q or Q3 students. You can choose to
  1. Present in class (physically, using the assigned time slot)
  2. Submit a video presentation through T-Square which shows your slides with voice narration; it is up to you whether to show your face or not. If you choose this video option,
     1. You will have 3-day lag
     2. Please replace the date that Polo assigned to your group with the word "video"
• Every team's presentation slides will be collected via T-Square a few days before the proposal days, and pre-loaded to the computer at the podium, to reduce switching time between teams.
• Team's contact person submits the slides, as a file called teamXXslides.pdf (e.g., team02slides.pdf). PDF only; no PPT or other formats.

Grading

• [45%] You must answer the Heilmeier questions. 5% for each question. If a question doesn’t apply, say so.
• [15%] Brief literature survey. Can be combined with Heilmeier question(s).
• [10%] Expected innovation. Can be combined with Heilmeier question(s).
• [10%] Plan of activities
• [20%] Presentation delivery
• [-5%] Illegible text, tiny figures, bad color contrast, etc.
• [-5%] Overrun
• Your presentation does NOT need to strictly follow your project proposal document. For example, you can talk about ideas and materials that your team has come up recently.
• Points will NOT be deducted or awarded based on the number of presenters. We saw great presentations delivered by teams having various numbers of presenters.

Tips

• Use few slides. Less is more! Fewer slides mean less likely to overrun. Being succinct is hard.
• Practice timing and delivery! If you have several speakers, make sure you practice how to transition from one person to the next (e.g., passing the mic, passing control of mouse and keyboard, etc). PRACTICE! PRACTICE! PRACTICE!

Progress Report

This should be no more than 1600 words, 12pt font, typed.

It mainly serves as a checkpoint, to detect and prevent dead-ends and other problems early on.

It should consist of the same sections as your final report (introduction, survey, etc), with a few sections "under construction", describing the work performed up to then, and the revised plans for the whole project.

Specifically, the introduction and survey sections should be in their final form. The section on the proposed method should be almost finished. The sections about experiments and conclusions will have whatever results you have obtained, as well as `place-holders' for the results you plan/hope to obtain.

Grading scheme & Submission instructions

• [70%] for proposed method (should be almost finished)
• [25%] for the design of upcoming experiments / evaluation
• [5%] for plan of activities (please show the old one and the revised one, along with the activities of each group member)
• Clear list of innovations: give a list of the best 2-4  ideas that your approach exhibits.
• Team's contact person submits a softcopy via T-Square (progress report only), named teamXXprogress.pdf, where XX is the team number (e.g., team01progress.pdf for team 1)
• [-5% if not included] Distribution of team member effort. Can be as simple as "all team members have contributed similar amount of effort". If effort distribution is too uneven, I may assign higher scores to members who have contributed more

Final Poster Presentation Peer-graded

Logistics

Each team will create a single poster (for the whole team).

Each student will be a presenter once, and be a grader several times:

1. Each student will present his/her team's poster during the poster session. Each student will have 3 minutes to present the poster, and 1 minute for Q&A. All team members must attend the poster session. If you cannot attend part of it, you must write to the instructor at least 5 days before the presentation, or you will receive 0 as your presentation score.
2. Each student will also grade several presentations given by students in other teams during the poster session. A student's presentation score will be the average of the scores that he/she receives. Before the poster session, we will let each student know when he/she will present, and when he/she will grade others.

Thus, every team member should know his/her project very well, and be prepared to answer questions.

Demo: Optional but encouraged. The demo time counts towards the presentation time. If you decide to give a demo, please bring your own laptop. Assume there will little or no internet connection, and no ready access to power outlets.

Who will attend: We plan to open the session up to everybody (College of Computing, etc.).

Everyone is welcome to walk around to see other teams' posters.

Poster Design

Design and print the poster *well before* your presentation day, to avoid last-minute rush.

The poster must be in portrait orientation, 30 inches wide and 40 inches tall. Foam core poster boards, push pins, and easels will be provided to you to mount the poster. We suggest 18pt font size and larger.

A deck of PowerPoint slides is not acceptable as a poster. However, you may print your design on multiple smaller sheets of paper and then carefully stitch them together. See the illustration below for what is allowed and what is not.

Your poster should cover the following parts (point distribution shown on the left).

10%	Motivation/Introduction: 5% What is the problem (no jargon)? 5% Why is it important and why should we care?
20%	Your approaches (algorithm and interactive visualization): 5% What are they? 5% How do they work? 5% Why do you think they can effectively solve your problem (i.e., what is the intuition behind your approaches)? 5% What is new in your approaches?
10%	Data: 5% How did you get it? (Download? Scrape?) 5% What are its characteristics (e.g., size on disk, # of records, temporal or not, etc.)
25%	Experiments and results: 5% How did you evaluate your approaches? 10% What are the results? 10% How do you methods compare to other methods?
10%	Presentation delivery: 5% Finished on time? 5% Spoke clearly and at a good pace?
25%	Poster Design: 5% Layout/organization (Clear headings? Easy to follow?) 5% Use of text (Succinct or verbose?) 5% Use of graphics (Are they relevant? Do they help you better understand the project's approaches and ideas?) 5% Legibility (Is the text and figures too small?) 5% Grammar and spelling

If you team has Q or Q3 students. the team can choose to

1. Present in class, physically
2. Submit individual 3-minute video presentations (one presentation per student) through T-Square via the entry “Poster Video - Q”. The standard 3-day lag applies.
   Name each video recording teamXXposter-YY.mp4 (or .avi or .mov), where XX is the team number (e.g., 01 for team 1), and YY is the student's last name (e.g., smith).
   
   Project slip days CANNOT be used for this video presentation submission, since on-campus students cannot use their project slip days either (they all present on the same day).
   
   Your video should show your poster (e.g., as pdf on your computer screen via screen capture, say using Quicktime, MonoSnap, etc.) with voice narration; it is up to you whether to show your face. You should be able to create this recording quickly with little effort – no need to do any special video or audio editing.

Final Report

It will be a detailed description of what you did, what results you obtained, and what you have learned and/or can conclude from your work.

Components:

1. Writeup: no more than 2800 words, 12pt font, typed. Describe in depth the novelties of your approach and your discoveries/insights/experiments, etc. 
2. Software: packaging, documentation, and portability. The goal is to provide enough material, so that other people can use it and continue your work, if you are to open-source it -- in other words, you should make it easy and attractive for others to use your work.

Grading scheme & Submission instructions

• Writeup
  • [2%] Introduction - Motivation
  • [3%] Problem definition
    
  • [5%] Survey
  • Proposed method
    • [10%] Intuition - why should it be better than the state of the art?
    • [35%] Description of your approaches: algorithms, user interfaces, etc.
  • Experiments/ Evaluation
    • [5%] Description of your testbed; list of questions your experiments are designed to answer
    • [25%] Details of the experiments; observations (as many as you can!)
  • [5%] Conclusions and discussion
  • [-5% if not included] Distribution of team member effort. Can be as simple as "all team members have contributed similar amount of effort". If effort distribution is too uneven, I may assign higher scores to members who have contributed more.
• [10%] Team’s contact person submits one zip file, called teamXXfinal.zip, via T-Square, where XX is the team number (e.g., team01final.zip for team 1). The teamXXfinal.zip will contain the following 3 components:
  • README.txt - a concise, short README.txt file, corresponding to the "user guide". This file should contain:
    1. DESCRIPTION - Describe the package in a few paragraphs.
    2. INSTALLATION - How to install and setup your code.
    3. EXECUTION - How to run a demo on your code.
  • DOC - a folder called DOC (short for “documentation”) containing:
    1. teamXXreport.pdf - Your report writeup in PDF format; can be created using any software, e.g., latex, Word.
    2. teamXXposter.pdf - Your final poster.
  • CODE - All your code should be added here. Make sure that your package includes only the absolutely necessary set of files.