20.109(F08): Microarray data analysis
Sony Playstation or Microsoft X-box? Boxers or briefs? Coke or Pepsi? We all know that taste can’t be mandated, but then how do standards arise. Standards are a fundamental and required aspect of engineering. Without them, machines can’t talk to each other, hardware is difficult to repair, and profits disappear (try to estimate the recent earnings by Betamax). In many cases, standards are government mandated, e.g. the US public school curriculum, cell phone technology in Europe, internet protocols worldwide. On other occasions, external events or pressures influence standards. Sweet N’ Low was essentially the only artificial sweetener on the market until the saccharine it contained was “shown” to cause cancer in lab rats. On rare occasions, standards arise through extreme behavior. In 1888, Thomas Edison wanted to demonstrate the superior safety of direct current (the technology his company marketed) so he publicly electrocuted dogs with 1000 volts of alternating current, the technology his competitor, Westinghouse, was marketing for use in homes.
How do standards arise when there is no traditional financial market for them? In the case of BioBricks, the Registry of Standard Biological Parts is relying on the goodwill of the community to contribute standard parts that conform to the Registry’s rules. The payoff isn’t market share of the biological parts market, but rather the establishment of a shared resource that is reliable, reusable and useful. Community compliance to standards for microarray experiments and data analysis is similarly driven. Despite disagreement within the scientific community about how to collect meaningful microarray data, a “Minimum Information About a Microarray Experiment” (MIAME) checklist has been generated and is largely adhered to. “Minimum information” means only that the microarray data can be examined and interpreted by others…not a high bar for publication standards but one that is difficult to achieve since the arrays themselves are provided by different commercial vendors who disclose different amounts of information about their arrays. Moreover, the effort required to annotate MIAME data is significant and authors vary in their compliance.
Corroboration of published microarray data is further compounded by a lack of standards surrounding the data analysis itself. Processing the raw data mixes art and science. Algorithms used vary dramatically, and a single data set can appear compelling or noisy, depending on the analysis choices made by the investigator. For example, Cy3 and Cy5 are commonly used fluorescent probes but others dyes can be used and may be processed with different background correction and normalization factors. Not surprisingly, experiment protocols make a difference too. Researchers who indirectly label may find different outcomes than researchers who perform the same experiment but directly incorporate fluorescent dyes into their RNA. Also worth noting is human error, since microarrays experiments require many steps over many days. There are even stories of people scanning their slides backwards and consequently mis-identifying every spot on the array.
This lack of consensus should be both liberating for you today and also burdensome. You will have great freedom in how to analyze and interpret your data. Some initial steps are suggested but then you’re free to try different approaches that you are interested in and that make sense to you. You will need to carefully annotate and justify the choices you make, to allow others to understand and critique your approach. Good luck and have fun!
Here is a rough outline of the steps you can take to examine your microarray data. There are many variations on this that are acceptable and that may be more interesting or appropriate for you. You should explore the data as you see fit.
- open txt file in xls (tab delimited)
- delete top 9 rows
- label a new worksheet for working with your data
- copy columns for: GeneName, SystematicName, Description, gMeanSignal, rMeanSignal gMedianSignal, rMedianSignal, gBGMeanSignal, rBGMeanSignal, gBGMedianSignal, rBGMedianSignal
- format the numerical cells as numbers with no decimal place
- consider mean and median variations and background, to correct as you see fit. Be sure you keep track in your notebook or in the xls file of your analytical decisions.
- start new column with ratio of green signal/red signal.
- start new column called log2green/red and use data in green/red column as =LOG(cell#,base), for example =LOG(D3,2) and drag corner to apply formula to all 11K cells. Again format to whole numbers if this does not happen automatically.
- Select entire sheet by clicking on diamond in corner then sort by log2 (green/red).
- Sort cells in decending order according to log2green/red
- What do you see? Are the duplicates in agreement? Are there particular genes you expect to see up or down regulated in the two samples (e.g. URA3)? What happens to the SAGA-subunits? Are there particular kinds of genes (e.g. mating type genes, gal regulated genes...) that are up or down regulated by the deletion? Ask the questions you want about this data...
- save as XLS worksheet or workbook
For next time
Your first draft of your Mod 3 lab report is due next time. Remind yourself of the class expectations for your report. Some extra information to guide you when you prepare your Mod3 lab report is included here. Before arriving in lab next time, email your report to nkuldell AT mit DOT edu and breindel AT mit DOT edu.