diff --git a/Final-Project.ipynb b/Final-Project.ipynb index 2b59cc3..b560a9b 100644 --- a/Final-Project.ipynb +++ b/Final-Project.ipynb @@ -8,7 +8,7 @@ "\n", "Your final project is, at least ideally, the conjoining of everything you've learned in the course so far. You'll be using many of the big ideas you've learned, your Python skills, command-line and `git`, and plenty of pandas and data viz. \n", "\n", - "You will be working in teams (assigned below) to make a data driven argument that answers the following question:\n", + "You will be working in teams within your lab to make a **data driven** argument that answers the following question:\n", "\n", "## What is the best neighborhood in Pittsburgh?\n", "\n", @@ -16,13 +16,11 @@ "\n", "With your group members, you will be creating a Jupyter notebook to demonstrate your argument and the data analysis you did to support it. You will present your arguments to the class in the last few weeks of lab.\n", "\n", - "To answer this question you need to do the following:\n", + "As a brief overview, to answer this question you need to do the following:\n", "\n", "* Come up with a team name!\n", "* As a group, come up with some ways of defining and measuring \"bestness\". This doesn't have to be a serious metric, it could be whimsical or secretly \\\"worstness.”\n", - "* Each group member will be responsible for **one metric each.**\n", - "* Use at least 3 datasets in your argument. The easiest way to meet this requirement is for each member to choose their own _unique_ dataset to analyze their metric.\n", - "* Combine your metrics into a single metric as you see fit.\n", + "* Use at least 3 datasets in your argument. \n", "* Create a git repository to store your data and notebooks and code.\n", "\n", "\n", @@ -54,33 +52,23 @@ "cell_type": "markdown", "metadata": {}, "source": [ - "## The Breakdown (AKA What Goes in the GitHub repo)\n", - "\n", - "There are some key things that need to be included in your repository. Think of this project as a combination of all of the things we learned in lab this semester, with a focus on the last few weeks. So, there are some minimum requirements of files and information you will want to put in your group repo.\n", - "* The final report Jupyter notebook (see below)\n", - "* A Readme that contains:\n", - " * Team name\n", - " * Team members and their email addresses\n", - " * Description and links to the datasets used\n", - " * An Abstract\n", - "* Each group member's personal notebook(s) (Show your work)\n", - "\n", - "\n", - "While this is a group project, each group member has their own responsibility. In addition, all group members have responsibilities as a group. Basically, the best success will be found by those who work as a team.\n", + "## Final Report Notebook\n", "\n", + "It is best to think about your final project as a data-driven report. You will need to put everything into a Jupyter notebook with the following structure:\n", "\n", - "Individual responsibilities:\n", - "* Maintain your own notebook where you use a metric to find the \"Best\" Neighborhood in Pittsburgh\n", - "* Make sure the group repo has the personal notebook\n", - "* Write a conclusion\n", - "* Submit a link to the group repo on Canvas\n", + "* **Introduction:** Introduce the project, your approach, talk about the process of how you came up with the metric and some alternatives you may have explored.\n", + "* **The Metric:** Describe your metric. What features are you measuring? What datasets are you using?\n", + "* **The Best Neighborhood:** Apply the metric from the previous section to determine the best neighborhood in Pittsburgh. Beyond just executing code, provide narrative about why you think this is the best neighborhood. Incorporate a data visualization, perhaps to rank all of the neighborhoods or show a neighborhood’s best-ness over time. The key is to make a data driven argument.\n", + "* **Conclusion:** Reflect on how the data driven determination of “best neighborhood” is the same or different from your personal favorite neighborhood (Pittsburgh or not!). Each member of the group should write their own response to this.\n", "\n", + "Then, in our final meetings, each group will present their findings to the whole class. This presentation will cover all of the above categories.\n", "\n", - "Group responsibilities:\n", - "* Have a group repository that contains all work done\n", - "* Combine Individual metrics into a single final metric (surprisingly, this does require teamwork)\n", - "* Have a Best Neighborhood for your group\n", + "### Tips\n", "\n", + "* Make this fun! Don’t make this harder than it needs to be. You define your metric and submetrics, so you are entirely free to pick a metric that is easy to calculate, but reveals something fun about Pittsburgh. You can also be as fancy as you want, and if you want to do something big and impressive, go for it!\n", + "* Show your work, but not all of it. When working on a project, I often have a couple sets of notebooks. One is a set of working notebooks where I do my data exploration, hack on the code, and go down wrong paths. When I finally am able to pull together the code that generates the result I want, I move just that code into my “final draft.” I only want to see the data cleaning, transformation, analysis, and visualization associated with the specific argument you are making in the final notebook and presentation.\n", + "* Act like you're presenting to a non-technical audience and/or you from the beginning of the semester. Don't read your code line by line, that can be just as boring to the presenter as it is to the audience!\n", + "* GIFs, memes, and jokes, when used appropiately, make a presentation more engaging for everyone!\n", "\n", "---" ] @@ -89,25 +77,37 @@ "cell_type": "markdown", "metadata": {}, "source": [ - "## Final Report\n", "\n", - "It is best to think about your final project as a data-driven report. You will need to put everything into a Jupyter notebook with the following structure:\n", + "While this is a group project, each group member has their own responsibility. In addition, all group members have responsibilities as a group. Basically, the best success will be found by those who work as a team.\n", "\n", - "* **Introduction:** Introduce the project, your approach, talk about the process of how you came up with the metric and some alternatives you may have explored.\n", - "* **The Metric:** Describe your metric, what features are you measuring. What datasets are you using?\n", - "* **The Best Neighborhood:** Apply the metric from the previous section to determine the best neighborhood in Pittsburgh. Beyond just executing code, provide narrative about why you think this is the best neighborhood. Incorporate a data visualization, perhaps to rank all of the neighborhoods or show a neighborhood’s best-ness over time. The key is to make a data driven argument.\n", - "* **Conclusion:** Reflect on how the data driven determination of “best neighborhood” is the same or different from your personal favorite neighborhood. Each member of the group should write their own response to this.\n", "\n", - "Then, in our final meetings, each group will present their findings to the whole class. This presentation will cover all of the above categories.\n", + "### Individual responsibilities:\n", + "* Maintain your own notebook where you use your submetric to find the \"best\" neighborhood in Pittsburgh\n", + "* Make sure the group repo has the personal notebook\n", + "* Write a conclusion\n", + "* Submit a link to the group repo on Canvas\n", "\n", - "### Tips\n", "\n", - "* Make this fun! Don’t make this harder than it needs to be. You define your metrics, so you are entirely free to pick a metric that is easy to calculate, but reveals something fun about Pittsburgh. You can also be as fancy as you want, and if you want to do something big and impressive, go for it!\n", - "* Show your work, but not all of it. When working on a project, I often have a couple sets of notebooks. One is a set of working notebooks where I do my data exploration, hack on the code, and go down wrong paths. When I finally am able to pull together the code that generates the result I want, I move just that code into my “final draft.” I only want to see the data cleaning, transformation, analysis, and visualization associated with the specific argument you are making in the final notebook and presentation.\n", - "* Act like you're presenting to a non-technical audience and/or you from the begining of the semester. Don't read your code line by line, that can be just as boring to the presenter as it is to the audience!\n", - "* GIFs, memes, and jokes, when used appropiately, make a presentation more engaging for everyone!\n", + "### Group responsibilities:\n", + "* Have a group repository that contains all work done\n", + "* Combine individual metrics into your final, overarching metric\n", + "* Name a neighborhood as **Best** according to your analysis" + ] + }, + { + "cell_type": "markdown", + "metadata": {}, + "source": [ + "## The GitHub repo\n", "\n", - "---" + "There are some key things that need to be included in your repository. Think of this project as a combination of all of the things we learned in lab this semester, with a focus on the last few weeks. So, there are some minimum requirements of files and information you will want to put in your group repo.\n", + "* The final report Jupyter notebook\n", + " * Make sure this file (and the rest) are clearly named!\n", + "* Each group member's personal notebook(s) (Show your work)\n", + "* A Readme that contains:\n", + " * Your team name\n", + " * A brief overview of what is contained in the repo\n", + " * i.e. what is the project? what is each file for? etc\n" ] }, { @@ -116,11 +116,10 @@ "source": [ "## Presentations\n", "\n", - "The final two weeks of this lab will be presentation weeks; half of the groups will present on each week. Presentations should last a maximum of 10 minutes, with 5 minutes of discussion.\n", + "You will be presenting your final notebook. However, as with any presentation, don't just read the words verbatim—add commentary. Your analysis may be in-progress, but you should at least have some **initial results**. Each group member should be able to talk about their submetric and what data they're using to measure it. Expect to have a discussion about your team’s metric and get feedback to incorporate into the final report.\n", "\n", - "You can prepare slides or you can present from a notebook directly, but it will be easiest to use the notebook. We understand your analysis will be in-progress, but you should have some initial results.\n", + "Presentations will happen during the the final two weeks of this lab. Half of the groups will present on each week. Presentations should last a maximum of 10 minutes, with 5 minutes of discussion.\n", "\n", - "Each group member should be able to talk about their metric and what data they're using to measure it.\n", "\n", "**NOTE**\n", "\n", @@ -148,7 +147,7 @@ "source": [ "## Collaboration\n", "\n", - "You should use a shared GitHub repository to collaborate with your group, so that you can work on the project and be sure that you all have the same version. One person should create a repository for the project, and then they'll need to invite the other members of the group to collaborate. You can see how to do that in this [GitHub article](https://help.github.com/articles/inviting-collaborators-to-a-personal-repository/). \n", + "You need to use a shared GitHub repository to collaborate with your group, so that you can work on the project and be sure that you all have the same version. One person should create a repository for the project, and then they'll need to invite the other members of the group as collaborators. You can see how to do that in this [GitHub article](https://help.github.com/articles/inviting-collaborators-to-a-personal-repository/). \n", "\n", "For programming, I'd point your attention to the software development concept of \"pair programming\". It's defined [here](https://www.agilealliance.org/glossary/pairing/): \n", "\n", @@ -186,7 +185,7 @@ "source": [ "## Completing the Report and Presentation\n", "\n", - "You'll have this week and next to work on your presentation and the project in lab and independently, with your groups. Don't forget that you will have to talk about your project to your TA in the lab section before presentations begin!\n", + "You'll have time over the next few weeks to work on your project with your groups, in lab or on your own. Don't forget that you will have to talk about your project to your TA in the lab section before presentations begin!\n", "\n", "Again, the final two lab sessions will consist of **student presentations**: each group will give a short presentation on their analysis. These presentations will be a lot like your lab lecture; you'll be presenting from your Jupyter notebook. You should prepare these with your group ahead of time, taking the time to write yourself speaker notes and get a sense of who will be presenting what.\n", "\n", @@ -212,7 +211,7 @@ "name": "python", "nbconvert_exporter": "python", "pygments_lexer": "ipython3", - "version": "3.8.8" + "version": "3.8.3" } }, "nbformat": 4,