Presentation and project Presenter Define and motivate problem

Presentation and project

Presenter • Define and motivate problem (if not discussed in class or not an obvious problem) • Explain solution(s) • This should be core • It is not sufficient to raise an interesting question without a potential solution • Given high level idea and then go into details (details are needed) • This does not need to be your original work • Present results • You do not need to conduct the experiment yourself • Be critical of what you got. Are the results from the authors trustworthy?

Audience • You are asked to rate each presenter • I will put the “task” up on canvas • It will be “graded” and a part of the 70% • Be critical. Treat yourself as a judge for some context. Need to comment on strength and weaknesses of a presentation • Grading metric for review (1 points max) • Below average (0. 5 point) • Average (0. 75 point) • Above average (1 points) • Your rating should be submitted before mid-night of the day after presentation • You have ~36 hours

Project proposal (Due on 4/4) • Define problem • Tentative approach(s) • Names of group members • How tasks will be split (if group project) • Work on the project now if you can. Don’t wait until after submitting your proposal. If you are not sure whether your project idea is good, just drop me an email

Some project ideas • If you need some inspiration, check out the course website for links for project ideas • Project should require reasonable amount of effort • Effort of at least 3 HW assignments seem appropriate • However, you can reuse codes you generated from the assignment. No need to start from scratch • Unlike the presentation by the graduate students • You are suppose to implement and test your solution • So literature survey alone is not a valid project for this course

Grading metric (30%) Presentation: (10 out of 30) • clarity, structure, references • Informative: e. g. , background literature survey • good insights and discussions of methodology, analysis, results, etc. Technical: (10 out of 30) • Correctness, depth (ad hoc/theoretical-based), innovation Evaluation and results: (10 out of 30) • sound evaluation metric • thoroughness in analysis and experimentation • results and performance Labor cost adjustment No of members 1 2 3 4 5 6 7> Deduction (in %) 0 0 5 10 20 40 80

Expectation Quality Grade Undergrad Graduate Just submitting 1/3 Department-level “conference” 2/3 University-level conference 3/3 2. 5/3 National-level conference 3/3 Above is just a rough estimate of expectation. But after all the grade is based more on effort spent than whether the project is “complete”. I definitely would like to encourage you to pursue project that you find most interesting and passionate about. Don’t worry if you can’t “complete” it. You just need to detail what you have done in the report.

Submission (due on 5/7) • Written report: • Problem description and motivation • What did you try to solve • Can be shorter if it is a common problem (e. g. , segmentation) • Your approach(s) • Evaluation • Discussion: why it works or doesn’t work • Video/screencast “presentation”: not mandatory. But maximum 25% extra credit of the project • ~ 30 minutes • Longer video is not always better • Only submit youtube/dropbox link to Canvas. Please do not upload the entire video

Final grade • A: ~ 90% or above • B: 80%-90% • C: 70%-80% • D: 60%-70% • F: Below 60%