How To Combine Two Types Of Affymetrix Genechip Results?
0
0
Entering edit mode
11.5 years ago
Gangcai ▴ 230

Dear All, I have two sets of Affymetrix GeneChip data, one from GeneChipĀ® HT MG-430 PM Array Plate and another from GeneChipĀ® Mouse Genome 430 2.0 Array. According to official description, they use the same kind of technology, however they have different probset ids and different probe-sequences. My question is how can I combine those two datasets for comparison?

Thanks in advance.

affymetrix probeset gene • 3.8k views
ADD COMMENT
1
Entering edit mode

Gangcai, you can join your data as shigeta wrote and try metaanalytic approach, i.e. something to transform data from different experiments to the same scale. Take a look at metaArray, GeneMeta, RankProd, metahdep packages. [?]Somewhere in these tutorials is example of joint analysis of several Affymetrix experiments.[?] HTH

ADD REPLY
0
Entering edit mode

This can be done by taking your log2 difference results from the 2 separate arrays and taking the identical probe set names and comparing them. The two have almost the same probe set contents. Any differences, if any, are not likely to be of biological consequences.

As with other microarray data, scaling data from different experimental runs can be done (esp in this case as they are essentially the same array), but often don't get the best results because of variance between samples, prep, hybridization conditions, etc.

ADD REPLY
0
Entering edit mode

Hi shigeta, thanks for your reply. I have checked the probeset names, and only 64 probes have exact same ids between those two GeneChips.

ADD REPLY
0
Entering edit mode

there is a resource on affymetrix.com called a comparison spreadsheet. they should be available for these 2 arrays - they are less exact unfortunately as the probes are not identical.

ADD REPLY

Login before adding your answer.

Traffic: 1098 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6