Final Project 1: proposal

Author
Affiliation

Jelmer Poelstra

Published

October 11, 2025



Overview

The first Final Project checkpoint is to submit a summary of what you plan to do for your Final Project. This proposal is due on November 16 and is worth 5 points.

Directions and grading

Submission expectations

  • Deadline: Sunday Nov 16th at 11:59 pm.
  • Submission: Submit your assignment by tagging @menukabh and @jelmerp in an Issue in your GitHub repo

Academic integrity

Use of generative AI Tools (e.g. ChatGPT, Microsoft Copilot, Google Gemini) is permitted
Getting help on the assignment is not permitted
Collaborating, or completing the assignment with others, is not permitted
Copying or reusing previous work is not permitted
Open-book research for the assignment is permitted
APA Citations and/or formatting for this assignment are not required

Rubric

You can earn a total of 5 points across the 6 steps below as follows:

Step Points
1 0.25
2 0.25
3 0.5
4 0.5
5 0.25
6 0.5
7 0.25

Detailed steps

  1. Create a directory for your project at OSC (within /fs/ess/PAS2880/users/$USER) and initialize a Git repository there. This will be a directory and repository that you will continue throughout the Final Project, and won’t just be for this proposal.

  2. Write a Final Project proposal in a Markdown file, which you should include in your repository. As with the graded assignments, push your repository to GitHub and tag Menuka (@menukabh) in an “Issue” on GitHub1 when you’re done.

  3. In the proposal, start with a general description of what your project will be about. Describe what data you will work with and what kind of output your project will produce.

  4. Next, summarize how you envision the more technical aspects: for example, you can mention how you will structure and run your scripts, which external programs / bioinformatics tools you plan to use (or that you are still researching this but are looking for something that can do xyz), and how you will structure your results.

  5. Check the list of graded aspects on the page with general information about the project. You may also already refer to the more detailed grading rubric on the page about you project’s final submission. If you are not sure you will be able to fulfill one of these aspects, or intend to skip something, mention that in your proposal.

  6. Describe which aspects of your project you are still uncertain about, for instance because you intend to include some topics that we have yet to cover in the course, or because you’re not sure how far you will get.

  7. Describe why you chose to pick this project. For example, because it will be useful for your research, or because it gives you practice with coding topics that you want to improve on.

Back to top

Footnotes

  1. Make sure to tag in the text body for the issue, it won’t be parsed as a tag if you do this in the title of the issue.↩︎