Yeast Beasts

• This page will be the main place from which the Yeast Beasts team project will be managed. Include all of the information/links that you think will be useful for your team to organize your work and communicate with each other and with the instructors. Hint: the kinds of things that are on your own User pages and on the course Main page can be used as a guide.

Week Reflections

Week 13

Andrew's Reflection [Coder/Designer]

To find my electronic notebook for this week please click on Andrew Sandler's Week 13 Lab Notebook Executive Summary

What worked? Everything "worked" but some surprises came up.

What didn't work? Not that this didn't work but it provided a challenge, the issues with the #REF boxes, the blank boxes, the random text in some boxes, and the NaN coming up in some spots. I don't know how to deal with this and will need help from Dr. Dahlquist so I am not just guessing at a solution. I also need to figure out how to get a complete Gene ID list and then compare the whole ID list to the missing ID's. I also need that list for the ID's for the Access Database.

What will I do next to fix what didn't work? I plan on speaking with Dean and Dr. Dahlquist in class tomorrow to fix these issues and then move onto working on the Access section of this assignment.

Katie's Reflection

1. This week, Charlotte, Hailey, and I worked on completing Milestones 2 and 3. These milestones consisted of preparing the dataset from SGD for analysis, and then performing an ANOVA analysis like we had done in Week 9. A more detailed summary of the steps we followed is outlined on mine and Charlotte's individual page, linked below.
   • Data Analysts Week 13
2. The data analysts, me and Charlotte, worked together with Hailey on progressing through Milestones 2 and 3 on the Data Analysis page. We contacted each other throughout the week to check in on what each person was doing. We then met in person to work together on performing the ANOVA analysis. This worked well, because when we couldn't meet we were still able to get some work done, and then once we got together we were able to ask any questions that we had. It was slightly difficult to progress through the steps in person because when attempting to work on the dataset at the same time, only one person could be actively making changes. I don't believe it is possible for this issue to be fixed, as we cannot have multiple people working at exactly the same time, because steps need to be followed in a specific order. In the future, we will continue to make sure that we split up the steps so that each person is doing an equal amount of work, and to be communicative about any questions that we have or can answer.

Charlotte's Reflection:

Katherine Miller and I, being the data analysts, worked with Quality Assurance Hailey Ivanson to complete Milestone 2 and Milestone 3 in person on April 17th, 2024. We messaged the Coder/Designers and got an update from them. I wrote out the steps taken on our Data Analysts Week 13 page. It was helpful that we were able to meet in person to collaborate. However, it was hard to make changes to the data since we were working on one computer. We ended up splitting up the work well, but at first everyone trying to make edits at once was hard. Now we know a system that works for us as a group.

Week 15

1. Each person needs to write a short executive summary of that person's progress on the project for the week, with links to the relevant individual journal pages (which will have more detailed information).
2. Each team member should reflect on the team's progress:
   1. What worked?
   2. What didn't work?
   3. What will I do next to fix what didn't work?
3. Note that you will be directed to add specific information to your team's pages in the individual portion of the assignment for this and future weeks.

Team Pages

• Yeast Beasts Main Page
• Deliverables
• Overview

Role Pages

• Project Manager
• Quality Assurance
• Data Analysis
• Coder/Designer

Template:Yeast_Beasts