Exception thrown in ReadAffy() when reading Hu-133B files in a GEO Dataset
1
0
Entering edit mode
lep ▴ 90
@lep-6139
Last seen 9.8 years ago
United States
When using the straightforward "ReadAffy()" syntax to read Affy arrays, I am experiencing an exception which is being thrown when the reader hits HU133B file in a particular GEO dataset. Is there an optimal way to read Hu-133A arrays separately from HU-133B arrays (.CEL files) from an untarred GEO data set? Thus, far, I am attempting a workaround by generating a filename list during untarring, and then attempting to read CEL files separately, using: dirname="C:/Data/GEOBreastHu133Plus/GSE1456/" setwd(dirname) rawcelfilename<-"C:/Data/GEOBreastHu133Plus/GSE1456/GSE1456_RAW.TAR" untar(rawcelfilename) filelist<-untar(rawcelfilename,list=TRUE) for (file in filelist) { result <- try(ReadAffy(filenames=file)); if(class(result) != "try-error"){ # data<- data + ??? <-- NEED to build up data set here after successfully opening each HU133A (B) CEL file } } If an exception is thrown due to an HU133B array, I want to go to the next filename. The trick is also how to build up a data set based on the successfully read CEL files -- and the above is not working. Later on, once "data" are read, I can use: pset <- fitPLM(data) NUSE(pset,main="GSE1456") eset<- rma(data) write.exprs(eset,file="data.txt") save(eset, file = paste("GSE1456",".RData")) FYI, I have successfully used: data<- ReadAffy() for HU133Plus2.0 CEL files and have had no problem; however, the Hu133B in this particular GEO set (1456) results in a thrown exception since HU133A arrays are not readable in ReadAFfy by default. Houston Methodist. Leading Medicine. Ranked by U.S.News & World Report as one of America's "Best Hospitals" in 13 specialties. Named to FORTUNE? Magazine's "100 Best Companies to Work For?" list eight years in a row. Designated as a Magnet hospital for excellence in nursing. Visit us at houstonmethodist.org. Follow us at twitter.com/MethodistHosp and www.facebook.com/HoustonMethodist ***CONFIDENTIALITY NOTICE*** This e-mail is the property of Houston Methodist Hospital and/or its relevant affiliates and may contain restricted and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender and delete all copies of the message. Thank you.
GO GO • 997 views
ADD COMMENT
0
Entering edit mode
@sean-davis-490
Last seen 7 weeks ago
United States
On Mon, Sep 9, 2013 at 3:52 PM, Peterson, Leif <lepeterson at="" houstonmethodist.org=""> wrote: > When using the straightforward "ReadAffy()" syntax to read Affy arrays, I am experiencing an exception which is being thrown when the reader hits HU133B file in a particular GEO dataset. Is there an optimal way to read Hu-133A arrays separately from HU-133B arrays (.CEL files) from an untarred GEO data set? > Hi, Leif. You'll need to either: 1) Put arrays from each platform in separate directory or 2) Supply a vector of filenames for each array platform to ReadAffy You can use the GEOquery or GEOmetadb packages to associate the arrays to the correct platform. Sean
ADD COMMENT

Login before adding your answer.

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