Design matrix: dye-swap or channel-swap?
1
0
Entering edit mode
John Welsh ▴ 30
@john-welsh-565
Last seen 10.3 years ago
I am confused about the design matrix for gls.series in limma. I have four two-color microarrays comparing samples A and B. A is always in channel1 and B is always in channel2. Red is in the first channel in two of them, and in the other channel in the other two. Do I want the design matrix c(-1,1,-1,1) or c(1,1,1,1)? John Welsh Associate Professor Sidney Kimmel Cancer Center 10835 Altman Row San Diego, CA 92121 (858) 450-5990 ex.282 jwelsh@skcc.org
Cancer limma Cancer limma • 691 views
ADD COMMENT
0
Entering edit mode
@gordon-smyth
Last seen 5 hours ago
WEHI, Melbourne, Australia
John, At 10:23 AM 12/12/2003, John Welsh wrote: >I am confused about the design matrix for gls.series in limma. >I have four two-color microarrays comparing samples A and B. >A is always in channel1 and B is always in channel2. >Red is in the first channel in two of them, and in the other channel in the >other two. Your question is a bit confusing because, normally, one channel belongs to one dye and the other channel belongs to the other dye. Normally one doesn't swap dyes but not channels. The question is, when your data is read into limma, does 'A' always get read into the G matrix and 'B' always into the 'R' matrix? If so you want design matrix all 1's. If not, you need 1 and -1. I am guessing that the former is true, but you haven't given enough information to tell for sure. Gordon >Do I want the design matrix c(-1,1,-1,1) or c(1,1,1,1)? > >John Welsh >Associate Professor >Sidney Kimmel Cancer Center >10835 Altman Row >San Diego, CA 92121 >(858) 450-5990 ex.282 >jwelsh@skcc.org > >_______________________________________________ >Bioconductor mailing list >Bioconductor@stat.math.ethz.ch >https://www.stat.math.ethz.ch/mailman/listinfo/bioconductor
ADD COMMENT

Login before adding your answer.

Traffic: 729 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