Building a Distance Metrics

Agenda (80 Minutes)

(80 minutes) Distance Metrics

Distance Metrics

Each team will break-up into their groups and fork the following git repository:

https://github.com/colbrydi/CMSE495_2022_Distance_Measures

In the repository, create a jupyter notebook to analyze the data provided in the csv file. This notebook should be written as a report explaining how the data is analyzed and showing how the data specifically relates to your teams perception of the project relative to the rest of the class (Feel Free to use the provided template). Your group needs to do the following:

Read in the data provided by the csv file (this is the data from our survey taken on 0207-Proposal_Presentation_Slide_Review).
Analyze the data to figure out what it says about your teams project.
Write your report and submit it as a pull request (make sure you use a unique filename to avoid merge collisions).

RECOMMENDED: Generate a a square “average distance matrix” where both the rows and columns are the group names. Each row is the teams average distance to the projects represented in the columns. If done correctly the value across the diagonal will be zero (because each team’s project is zero distance from their own project).

Report Summaries

Make sure you submit a merge request by the end of class today (even if your notebook is not done). Include a list of what you need to finish up during class next week. We will give you about 20 minutes to finish up your report and then we will go around the room for demonstrations. You are allowed to learn from each other but make sure you cite the other teams work.

Written by Dr. Dirk Colbry, Michigan State University
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.