Difference between revisions of "Data Analysis"

From LMU BioDB 2019
Jump to navigation Jump to search
(Milestone 3: Complete Microarray Data Analysis: note about column header)
(Milestone 3: Complete Microarray Data Analysis: add links to weekly journals)
Line 34: Line 34:
 
#* Data columns are to the right, in increasing chronological order, using the column header pattern you created
 
#* Data columns are to the right, in increasing chronological order, using the column header pattern you created
 
#* Replicates are grouped together
 
#* Replicates are grouped together
# Perform an ANOVA analysis of the data.
+
# Perform an ANOVA analysis of the data, as you did on [[Week 8]] for the Dahlquist lab data.
# Cluster the data with stem.
+
#* Note that you will need to adjust your formulas to take into account the different number of timepoints and replicates in your article's dataset.
# Use YEASTRACT to generate a candidate gene regulatory network.
+
# Cluster the data with stem, as you did on [[Week 9]].
# Create an input workbook for GRNmap based on a Microsoft Access database that the Coder/Designer and QA's make.
+
#* Note that we will make some adjustments to the GO term analysis because stem was not providing GO term names.
 +
# Use YEASTRACT to generate a candidate gene regulatory network as you did on [[Week 9]].
 +
# Create an input workbook for GRNmap based on a Microsoft Access database that the Coder/Designer and QA's make, following protocol in [[Week 10]]
 
# Run GRNmap and interpret data.
 
# Run GRNmap and interpret data.
 
# As the end-user of the Access database, the Data Analysts will provide feedback to the QAs and Coder/Designer about the usability of database.
 
# As the end-user of the Access database, the Data Analysts will provide feedback to the QAs and Coder/Designer about the usability of database.

Revision as of 14:34, 18 November 2019

Final Project Links
Overview Deliverables Guilds Project Manager Quality Assurance Data Analysis Coder/Designer
Teams FunGals Sulfiknights Skinny Genes

The role of the Data Analyst will be to apply the data analysis pipeline that you learned by analyzing the Dahlquist Lab microarray dataset to complete the analysis of a different published yeast timecourse microarray dataset. The Data Analysts are the end-users of the project, ultimately determining whether the work of the coder/designer and quality assurance members is useful to them.

Guild Members

  • Ivy, Marcus
  • Emma, Kaitlyn
  • Aby, David

Milestones

The milestones do not necessarily correspond to particular weeks; instead they are sets of tasks grouped together.

Milestone 1: Annotated Bibliography

  • The Data Analysts will work with their teams to develop an annotated bibliography of papers relating to their team's assigned paper.

Milestone 2: Journal Club Presentation

  • The Data Analysts will work with their teams to create and deliver a Journal Club presentation about to their team's assigned paper.

Milestone 3: Complete Microarray Data Analysis

  1. Download and examine the microarray dataset, comparing it to the samples and experiment described in your journal club article.
  2. Make a "sample-data relationship table" that lists all of the samples (microarray chips), noting the treatment, time point, and replicate number.
    • Come up with consistent column headers that summarize this information
      • For example, the Dahlquist Lab microarray data used strain_LogFC_timepoint-replicate number, as in wt_LogFC_t15-1.
  3. Organize the data in a worksheet in an Excel workbook so that:
    • ID is in the first column
    • Data columns are to the right, in increasing chronological order, using the column header pattern you created
    • Replicates are grouped together
  4. Perform an ANOVA analysis of the data, as you did on Week 8 for the Dahlquist lab data.
    • Note that you will need to adjust your formulas to take into account the different number of timepoints and replicates in your article's dataset.
  5. Cluster the data with stem, as you did on Week 9.
    • Note that we will make some adjustments to the GO term analysis because stem was not providing GO term names.
  6. Use YEASTRACT to generate a candidate gene regulatory network as you did on Week 9.
  7. Create an input workbook for GRNmap based on a Microsoft Access database that the Coder/Designer and QA's make, following protocol in Week 10
  8. Run GRNmap and interpret data.
  9. As the end-user of the Access database, the Data Analysts will provide feedback to the QAs and Coder/Designer about the usability of database.
Final Project Links
Overview Deliverables Guilds Project Manager Quality Assurance Data Analysis Coder/Designer
Teams FunGals Sulfiknights Skinny Genes