Projects

You can have a look at the scope of some projects from 2019 and 2022

This class requires a presentation and a report for a final project. Final projects are team-based with teams consisting of 3 to 5 members.

For the final project you are asked to create an R package. You are free to choose package functionality, but there should be

• a minimum of five functions with a coherent theme,
• a shiny app show-casing some of the functionality
• a website for the package
• a README page with installation instructions and basic demonstration of functionality
• evidence of testing the functionality
• 8-10 page report detailing your work. This report should be written as a package vignette, included in your package’s documentation.

You are asked to present your work as a team in one of the speaking slots during dead week and finals week. Each team member is supposed to present for about 5 mins.

There are several stages to the project. Only the last two stages are graded. All other stages are not graded. You should use them as an opportunity to get feedback. For stages 1-3 feedback will be given as soon as you submit your contribution, i.e. you don’t have to wait until after Spring break to submit your project idea.

• Stage 1 (by Mar 10, not graded): Identify team and topic
• Stage 2 (by Apr 14, not graded): Functional Package
• Stage 3 (by Apr 28, not graded): Testing and Documentation

Abstract and Presentation slots

• Stage 4: Presentation (Dead week and Finals, graded)
• Stage 5 (May 9th, graded): Package submission to canvas (Finals week)

We will be using the following project rubric for evaluating the final submission. Presentations are peer-evaluated. Feedback will be given in this form.

Presentations are scheduled for May 2 and May 4 during our regular class time, 2:10 - 3:25, and Thursday, May 11 12-2:00 pm during Finals Week.

Tuesday, May 2

Thursday, May 4

Thursday, May 11