Anytime you are summarizing something for an audience, or supervisor, or whatever in either written or verbal from, it's best to have the following consistent structure:
- An introduction, in which you tell or remind your audience in lay terms what you are working on and why
- A description of what you did at an appropriate level of detail for the current audience
- A "show and tell" session describing what you found. Visuals are very important here. Put the visuals front and center and describe and summarize them in as though you were back in grade school playing show and tell.
- Conclusions or Summary. This is a summation of what you found and what it means. It can be as short as the "elevator ride" version of your project that you might give to a colleague. The take-home message.
Presentations will be given on the penultimate day of class, so we have last day of class if we run short on time. The presentations should be between 10 and 12 minutes long.
- Practice the timing. Nailing the length of a presentation is important in professional contexts.
- Emphasize visuals, especially the plots that convey your main message.
- Use verbose slides. The audience will be trying to read and listen to you at the same time, which is not possible.
- Stress. You are among friends. This will be the most gentle form of public speaking in the entire galaxy.
The report is just a version of your presentation with prose in place of the spoken words used in your presentation. The writing should be clear, concise, and direct. No fancy flowery convoluted sentences!
There is no length requirement. Say what you need to say, and the report will then be as long as it needs to be. As with the presentation, play show and tell with your figures.
Simply submit the url of the GitHub repo your group used for the project.