Teamname Week 13 Status Report

From LMU BioDB 2013
Jump to: navigation, search

Contents

Team Name

Miles Malefyt

  1. What were the week’s key accomplishments?

This weeks key accomplishments were compiling the raw data from many individual data sources and then calculating where or not the gene was shown to be repressed or induced. Then the fold change ratios, the STdev, and averages were calculated in a new processed data folder. The process I used was based off of the Vibrio Cholera exercise we did earlier in the semester.

  1. What are next week’s target accomplishments?

The next weeks key accomplishments are finishing up the processed data files and then moving on to working on the gen mapp portion of the project. Mostly the GenMapp part because I am going in tomorrow (friday) to finish up processing the data.

  1. What team strengths were seen this week?

The team strengths that were shown this week was our ability to understand each of our roles in the project and communicate between each other on any questions we had with our roles. The group has shown a good work ethic in getting done what they need to get done.

  1. What team weaknesses were seen this week?

I didnt exactly see many weaknesses this week since we were all working on our respective portions of the project. In the future as all of our roles converge I think we need to work on our communication which will be integral to getting the work done. Mmalefyt (talk) 17:25, 21 November 2013 (PST)

Lauren Magee: Reflection Questions

  1. What were the week’s key accomplishments?
    • I was able to finalize a spreadsheet with the Gene IDs and corresponding log((Cy5 Signal- Cy5 background)/(Cy3 Signal- Cy3 background)) for every replicate (1-3) in the following file: File:Full Raw Data.xls. I was also able to clean up the data, so it was ready for the protocol used to prepare the [Vibrio cholerae] data in Week 8 for GenMapp analysis.
  2. What are next week’s target accomplishments?
    • Next week, I will hopefully be able to finish the protocol mentioned above and have a data file ready for GenMapp.
  3. What team strengths were seen this week?
    • We were more geared toward independent work this week, so all of our tasks were done on our own time. I think my teammates and I worked well in dividing our duties and taking responsibility for its completion. If one person fails to include their part, then the project is halted to a certain degree. Therefore, it is very important we all stay on top of our personal assignments and hold each other accountable.
  4. What team weaknesses were seen this week?
    • I don't think we had any blatant weakness this week, but in the future I think we could all work on our communication with one another. Since we were all doing our own assignments this week, I think we lost track of each other and what was getting done outside of our own role.

Laurmagee (talk) 12:31, 21 November 2013 (PST)

Stephen Louie

  • On the GenMAPP user side, a raw data collection of the microarray data was completed. Specifically, the data concerned the transcriptional responses of S. Meliloti when exposed to either 0.3 M NaCl or 0.7 M Sucrose. A new export of the GenMAPP database for S. Meliloti based on an update made available from GenMAPP Builder. With these two things, I ran a preliminary sanity check using Match and MS Access. Based on the results. There was 0 ID correlation between the gdb. and the microarray data.
  • For next week, it is integral that I identify the discrepancy between the IDs used in the microarray data and gdb. file. From what I can tell, the main difference is that the gdb. uses the old name of S. Meliloti (Rhizobium Meliloti) and uses the gene ID RB####. This is the most apparent of the differences, but does not mean that this is the sole cause for the difference.
  • The team primarily focused on their individual guild assignments as opposed to working together on one task. In light of this, I was particularly impressed as to how my teammates were able to finish their tasks and make their data available for the other members in an expedient and organized manner.
  • This was more of a fault on my part then my team. There was only limited communication being facilitated between team members during this week's work sessions. This was not particularly harmful as we all had an implicit understanding of each others' progress. Next week, this will definitely be critical as we move further into the export stages.

Slouie (talk) 23:31, 21 November 2013 (PST)

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox