Question: Is there any tutorial to perform Mouse/Human Transcriptome microarrays 1.0 ?
0
gravatar for jacorvar
4.0 years ago by
jacorvar40
European Union
jacorvar40 wrote:

Dear bioC community,

I have spent more than a whole day searching for tutorials/manuals to analyse mouse transcriptome arrays 1.0. I want to perform a DE analysis gene-wise but considering only exons, and there's apparently no information in the web. And what's the difference between mta10stprobeset and mta10sttranscriptioncluster? Does one consider the probes and the other the probesets? In that case, how can I distinguish probes mapping to exons, junctions and others? Is there any function for that? When I use mta10sttrancriptioncluster and limma to analyse DE genes, about 50% are DE, which makes no sense. Could any kind soul help me please?

Thanks in advance

affy mta10 tutorial • 996 views
ADD COMMENTlink modified 4.0 years ago by James W. MacDonald51k • written 4.0 years ago by jacorvar40
Answer: Is there any tutorial to perform Mouse/Human Transcriptome microarrays 1.0 ?
3
gravatar for James W. MacDonald
4.0 years ago by
United States
James W. MacDonald51k wrote:

If you summarize your array data doing something like

dat <- read.celfiles(filenames = list.celfiles())
eset <- rma(dat)

Then you will be summarizing the data at the 'core' or transcript level. In other words, you will be taking all probes that align to any exonic region (not junction probes) for each gene, and then summarizing them using RMA. If you do this, then you are treating your HTA array as if it were a Gene ST array, in which case any tutorial you find for analyzing microarray data will be directly applicable. If you are using limma, then the limma User's Guide is your friend.

The mta10stprobeset.db and mta10sttranscriptcluster.db packages are for when you summarize at the 'probeset' and 'core' levels, respectively. So you want the latter.

As for your analysis with 50% DE, without knowing more about your study and how you modeled the data, that may or may not make sense to me.

ADD COMMENTlink written 4.0 years ago by James W. MacDonald51k

So "core" means I am considering only probes at exon or coding transcript level, i.e., ignoring probes falling at introns? In that case, are the expression values for the probes aggregated per exon?

ADD REPLYlink written 4.0 years ago by jacorvar40
1

No, they are aggregated at the gene level. And yes, ignoring introns. That's what I meant when I said taking all probes that align to any exonic region (not junction probes) for each gene, and then summarizing them.

The only intronic probes on an Affy array are in control probesets, and those AFAIK are never combined into anything but the control probesets.

You cannot really summarize at the exon level, with any Affy array. What people usually consider to be the exon level is what Affy calls the 'probeset' level, which is defined as being within a 'probe set region' or PSR. The PSR may in fact cover the entirety of an exon, but it may not, especially if the exon is large, in which case there may be multiple probesets that interrogate different portions of the exon. You could hypothetically combine all the probesets for each exon into a table similar to the core_mps table in the pd.mta.1.0.st package, and then summarize at the exon level if you really cared about such things.

ADD REPLYlink written 4.0 years ago by James W. MacDonald51k
1

@jacorvar
This image gives you a visual example of why a Probe Selection Region (PSR) may not correspond to an exon.
PSR0100000619.mm and PSR0100000620.mm do have a one to one relationship of PSR -> Exon. However, PSR0100000624.mm and PSR0100000625.mm do not have a simple one to one relationship to a single full exon. PSR0100000624.mm overlaps one full exon [EX010000598.mm] and part of another exon [EX010000599.mm]. PSR0100000625.mm targets the remaining portion of [EX0100000599.mm]

http://i.imgur.com/dCqusbt.png

ADD REPLYlink modified 4.0 years ago • written 4.0 years ago by Jason Hubbard20
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 172 users visited in the last hour