Help with very old CEL files
1
0
Entering edit mode
@jeremy-davis-turak-2096
Last seen 3.9 years ago
United States
Hi BioC guys, I'm having trouble opening some CEL files from an old project on the RG_U34A chip. When I try to use ReadAffy, I get this error: Error in read.affybatch(filenames = l$filenames, phenoData = l$phenoData, : Is ***01_N1.CEL really a CEL file? tried reading as text, gzipped text and binary Also, the file does not open as a text file (so it's probably binary). I tried using Affy's Cell File Conversion Tool to convert from 'Version 4' to 'Version 3', but it can't open the files (and they're not read-only, which is a common mistake with that tool). Any help you can offer would be appreciated. Thanks very much, Jeremy
convert convert • 1.1k views
ADD COMMENT
0
Entering edit mode
@james-w-macdonald-5106
Last seen 31 minutes ago
United States
Hi Jeremy, Jeremy Davis-Turak wrote: > Hi BioC guys, > > I'm having trouble opening some CEL files from an old project on the > RG_U34A chip. When I try to use ReadAffy, I get this error: > > Error in read.affybatch(filenames = l$filenames, phenoData = l$phenoData, : > Is ***01_N1.CEL really a CEL file? tried reading as text, > gzipped text and binary You can also get this error if the file has been corrupted. Do you get the same result with all of your files, or just this one? Best, Jim > > Also, the file does not open as a text file (so it's probably binary). > I tried using Affy's Cell File Conversion Tool to convert from > 'Version 4' to 'Version 3', but it can't open the files (and they're > not read-only, which is a common mistake with that tool). > > Any help you can offer would be appreciated. Thanks very much, > > Jeremy > > _______________________________________________ > Bioconductor mailing list > Bioconductor at stat.math.ethz.ch > https://stat.ethz.ch/mailman/listinfo/bioconductor > Search the archives: http://news.gmane.org/gmane.science.biology.informatics.conductor ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues.
ADD COMMENT
0
Entering edit mode
> Hi Jeremy, > > Jeremy Davis-Turak wrote: > > Hi BioC guys, > > > > I'm having trouble opening some CEL files from an old project on the > > RG_U34A chip. When I try to use ReadAffy, I get this error: > > > > Error in read.affybatch(filenames = l$filenames, phenoData = l$phenoData, : > > Is ***01_N1.CEL really a CEL file? tried reading as text, > > gzipped text and binary > > You can also get this error if the file has been corrupted. Do you get > the same result with all of your files, or just this one? All of the files have this error. > > Best, > > Jim
ADD REPLY
0
Entering edit mode
On Jun 22, 2007, at 3:24 PM, Jeremy Davis-Turak wrote: >> Hi Jeremy, >> >> Jeremy Davis-Turak wrote: >>> Hi BioC guys, >>> >>> I'm having trouble opening some CEL files from an old project on the >>> RG_U34A chip. When I try to use ReadAffy, I get this error: >>> >>> Error in read.affybatch(filenames = l$filenames, phenoData = l >>> $phenoData, : >>> Is ***01_N1.CEL really a CEL file? tried reading as text, >>> gzipped text and binary >> >> You can also get this error if the file has been corrupted. Do you >> get >> the same result with all of your files, or just this one? > > All of the files have this error. You could try with affxparser. I do not know how the Fusion SDK deals with older version (provided that the files are intact and not damaged, which was also my first thought), but it is worth a try. For one file, do library(affxparser) readCel(filename) Kasper > >> >> Best, >> >> Jim > > _______________________________________________ > Bioconductor mailing list > Bioconductor at stat.math.ethz.ch > https://stat.ethz.ch/mailman/listinfo/bioconductor > Search the archives: http://news.gmane.org/ > gmane.science.biology.informatics.conductor
ADD REPLY

Login before adding your answer.

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