# Resources

### From cs331b Special Topics in 3dRR

Line 9: | Line 9: | ||

== Final Project Report Format == | == Final Project Report Format == | ||

- | - Max 10 pages;<br>- Title and authors<br>- Abstract: short summary of the project with main results <br>- 6 sections:<br> - Sec 1. Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it. add a concept figure showing the overall idea behind the method you are presenting. <br> - sec 2.1. Review of previous work (i.e. previous methods that have explored a similar problem)<br> - sec 2.2. Say why your method is better than previous work; and/or summarize the key main contributions of your work; <br> - sec 3.1: Technical part: Summary of the technical solution <br> - sec 3.2: Technical part: Details of the technical solution; you may want to decompose this section into several subsections; add figures to help your explanation. <br> - Sec 4: Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations.<br> - Sec 5: Conclusions: what's the take home message? <br> - Sec 6: References<br>- Final format: pdf, please!<br>You can look at one of my recent publications (such as this or this) as an example. | + | - Max 10 pages;<br>- Title and authors<br>- Abstract: short summary of the project with main results <br>- 6 sections:<br> - Sec 1. Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it. add a concept figure showing the overall idea behind the method you are presenting. <br> - sec 2.1. Review of previous work (i.e. previous methods that have explored a similar problem)<br> - sec 2.2. Say why your method is better than previous work; and/or summarize the key main contributions of your work; <br> - sec 3.1: Technical part: Summary of the technical solution <br> - sec 3.2: Technical part: Details of the technical solution; you may want to decompose this section into several subsections; add figures to help your explanation. <br> - Sec 4: Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations.<br> - Sec 5: Conclusions: what's the take home message? <br> - Sec 6: References<br>- Final format: pdf, please!<br>You can look at one of my recent publications (such as [http://web.eecs.umich.edu/~silvio/papers/savarese_feifei_eccv08.pdf this] or [http://www.vision.caltech.edu/savarese/papers_web/SavareseFei-Fei_ICCV2007.pdf this]) as an example. |

- | <br>Evaluation: <br> | + | <br>'''Evaluation:''' <br>Your project report will be evaluated based on the quality of the writing, the clarity of your technical explanation and, overall, how well you get your message across. If you follow the structure above, you'll have good chances to do a good job. :) |

- | <br>Project Source Code: <br>There is no need to attach a print out of the source codes to the manuscript. Final source codes of your working program need to be collected into a unique (zipped) file; this file is due on the project submission deadline date (i.e. Friday 12th midnight) and it is supposed to be sent to the grader as indicated by email. | + | <br>'''Project Source Code: '''<br>There is no need to attach a print out of the source codes to the manuscript. Final source codes of your working program need to be collected into a unique (zipped) file; this file is due on the project submission deadline date (i.e. Friday 12th midnight) and it is supposed to be sent to the grader as indicated by email. |

<br> | <br> | ||

Line 23: | Line 23: | ||

*The presentation needs to be 20 minutes long+ 5 minutes of Q&A; If your presentation lasts more than 20 minutes, it will be stopped. So please make sure the presentation doesn't go over 20 minutes. | *The presentation needs to be 20 minutes long+ 5 minutes of Q&A; If your presentation lasts more than 20 minutes, it will be stopped. So please make sure the presentation doesn't go over 20 minutes. | ||

- | '''Presentation format:''' | + | '''Presentation format:''' |

*The idea is to turn your project report (as discussed above) into slides; thus, your presentation will need to include slides covering: | *The idea is to turn your project report (as discussed above) into slides; thus, your presentation will need to include slides covering: | ||

**Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it. | **Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it. | ||

- | **Review of previous work (i.e. previous methods that have explored a similar problem) | + | **Review of previous work (i.e. previous methods that have explored a similar problem) |

**Why your method is better than previous work; and/or explain the key main contributions of your work; | **Why your method is better than previous work; and/or explain the key main contributions of your work; | ||

**Technical part: Summary of the technical solution, followed by the details of the technical solution; | **Technical part: Summary of the technical solution, followed by the details of the technical solution; | ||

- | **Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations. | + | **Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations. |

**Conclusions: what's the take home message? | **Conclusions: what's the take home message? | ||

- | '''Evaluation:''' | + | '''Evaluation:''' |

*your team will be evaluated based on the clarity of the presentation, quality of the slides, how well you get your message across, and how well you handle the questions at the end. Note that the presentation can still contain ongoing (non final) results; final results may be included in the final report. | *your team will be evaluated based on the clarity of the presentation, quality of the slides, how well you get your message across, and how well you handle the questions at the end. Note that the presentation can still contain ongoing (non final) results; final results may be included in the final report. | ||

Line 40: | Line 40: | ||

*Read the student code book, understand what ‘collaboration’ is and what ‘academic infraction’ is. | *Read the student code book, understand what ‘collaboration’ is and what ‘academic infraction’ is. | ||

- | *Discussing project assignment with each other is allowed, but coding must be done individually | + | *Discussing project assignment with each other is allowed, but coding must be done individually |

*Using on line presentation material (slides, etc…) is not allowed in general. Exceptions can be made and individual cases will be discussed with the instructor. | *Using on line presentation material (slides, etc…) is not allowed in general. Exceptions can be made and individual cases will be discussed with the instructor. | ||

## Revision as of 20:10, 22 September 2013

## Contents |

## Papers Presentation

- Each lecture has a theme. Two students will be presenting a set of papers covering that theme. While preparing your presentation, you must try to integrate the papers as much as possible into a coherent presentation. The presentation will need to summarize the papers and include:

- Introduction: introduce the problem , explain why it is important to solve it; indicate the method that is proposed to solve it.

- Review of previous work; this is an important session; make sure that an appropriate background is given. Don't hesitate to review previous/preliminary concepts that are critical for the understanding of the presented work. If a good background is given, it is easier to explain the details of the method and technical solution later on.

- Why the presented method is better than previous work; and/or explain the key contributions of this work;

- Technical part: Summary of the technical solution, followed by the details of the technical solution;

- Experiments: present here experimental results with plots, graphs, images and visualizations.

- Conclusions: what's the take home message?

Length: The presentation needs to be about 70 minutes long (35 minutes each);Make sure the presentation doesn't go over 70 minutes, so as to have time to go through the 5-minute discussion panel.

Evaluation:

- the presentation will be evaluated based on the clarity of the presentation, quality of the slides, how well you get your message across, and how well you handle the questions at the end.

Class participation

- Be prepared to ask questions during and after the lecture. At the end of each lecture, two discussion leaders are randomly selected: the discussion leader will ask questions to the presenters and lead a 5-minute discussion panel; the quality of the questions & discussion panel will be used for evaluating class participation.

## Final Project Report Format

- Max 10 pages;

- Title and authors

- Abstract: short summary of the project with main results

- 6 sections:

- Sec 1. Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it. add a concept figure showing the overall idea behind the method you are presenting.

- sec 2.1. Review of previous work (i.e. previous methods that have explored a similar problem)

- sec 2.2. Say why your method is better than previous work; and/or summarize the key main contributions of your work;

- sec 3.1: Technical part: Summary of the technical solution

- sec 3.2: Technical part: Details of the technical solution; you may want to decompose this section into several subsections; add figures to help your explanation.

- Sec 4: Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations.

- Sec 5: Conclusions: what's the take home message?

- Sec 6: References

- Final format: pdf, please!

You can look at one of my recent publications (such as [1] or this) as an example.

**Evaluation:**

Your project report will be evaluated based on the quality of the writing, the clarity of your technical explanation and, overall, how well you get your message across. If you follow the structure above, you'll have good chances to do a good job. :)

**Project Source Code: **

There is no need to attach a print out of the source codes to the manuscript. Final source codes of your working program need to be collected into a unique (zipped) file; this file is due on the project submission deadline date (i.e. Friday 12th midnight) and it is supposed to be sent to the grader as indicated by email.

## Project Presentation in Class

- The presentation needs to be 20 minutes long+ 5 minutes of Q&A; If your presentation lasts more than 20 minutes, it will be stopped. So please make sure the presentation doesn't go over 20 minutes.

**Presentation format:**

- The idea is to turn your project report (as discussed above) into slides; thus, your presentation will need to include slides covering:
- Introduction: introduce the problem you want to solve, explain why it is important to solve it; and indicate the method you used to solve it.
- Review of previous work (i.e. previous methods that have explored a similar problem)
- Why your method is better than previous work; and/or explain the key main contributions of your work;
- Technical part: Summary of the technical solution, followed by the details of the technical solution;
- Experiments: present here experimental results of the method you have implemented with plots, graphs, images and visualizations.
- Conclusions: what's the take home message?

**Evaluation:**

- your team will be evaluated based on the clarity of the presentation, quality of the slides, how well you get your message across, and how well you handle the questions at the end. Note that the presentation can still contain ongoing (non final) results; final results may be included in the final report.

##

Collaboration policy

- Read the student code book, understand what ‘collaboration’ is and what ‘academic infraction’ is.
- Discussing project assignment with each other is allowed, but coding must be done individually
- Using on line presentation material (slides, etc…) is not allowed in general. Exceptions can be made and individual cases will be discussed with the instructor.

## Resources

- Matlab tutorials by: