CMSE 495
This is the webpage for CMSE495 Data Science Capstone Course. These materials are provided as an Open Educational Resource (OER). Instructors interested in using these classroom resources should reach out to Dirk Colbry (colbrydi@msu.edu) who can provide all the materials and instructor notes.
Figure Reproducibility initial documentation
Agenda (80 Minutes)
- (50 minutes) Figure Reviews
- (25 minutes) Group meeting
Figure Reviews
This is a team paring exercise. Your team will work with another team to review your figure notebooks. Combine your teams and split up in to two groups (some people from each team). Have one group review your teams installation and figure instructions and the other group review the other teams instructions.
| Team A | Team B | Team C |
|---|---|---|
| CEPI - Anomaly Detection | Kellogg - Deduction Classification | |
| SME - Crack Prediction | QSIDE - Human trafficking | |
| D2L - Instructor API | Olson - Campain finance Data | |
| Henry Ford Hospital - Image Segmentation | QSIDE - Justfare Toolbox | |
| NC3 - Community Capital | Boeing - Defect Prediction | |
| Neogen - Pesticide Analysis | Kinesiology - 40 yard dash | Intramotev - Autonomous Vehicles |
Agenda
- (5 minutes) Break up into two groups
- (5 minutes) Quick Introductions. Identify a timekeeper, notetaker, code reviewer, and facilitator.
- (20 minutes) Review Figure instructions
- (10 minutes) Discussion and brainstorming about improvements
- (10 minutes) Finish typing up email to instructors
In your group, have someone that is not from the code development team to try to install the software and review the figure instructions. Have the group members from the development team hold back and only give advice and support if there is a problem. The idea is to streamline the process so that the figure instructions are sufficient for someone outside of the development team to be able to reproduce the figure (within reason) without needing to have a developer to help. As a group take lots of notes and review the documentation to the development group some constructive feedback. If you are a member of the code’s development team, use this as an opportunity to fix problems as they are discovered.
As a group, prepare a report for the instructor and the development team. This report should provide the following:
- List of the evaluation group members with an indication about which capstone team they are on.
- Was someone outside the development team able to understand and possibly reproduce the figure? If not, what was the problem?
- What are the open loops still on the project?
- Is there anything that needed to be added to the code/instructions to make the project easier to understand?
- Was there anything you could add to the project to help make the project better?
This is a group effort, use the attached google document to submit the report to the instructors.
Group meeting
Conduct a group meeting for the remainder of the hour. Check your project milestones, progress and make plans to practice and finish your presentation by next week.
Written by Dr. Dirk Colbry, Michigan State University
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.