Question about topTable output formatting (Limma) in Excel
1
0
Entering edit mode
@jdelasherasedacuk-1189
Last seen 8.8 years ago
United Kingdom
When I use the topTable function to create a table with my data, like this: toptableH226<-topTable(ebws, coef=1, n=number, genelist=gal, adjust.method="BH", sort.by="B") and then I write it to a file with write.table, like this: write.table(toptableH226, "180406-toptableH226.txt", sep="\t") this produces a tab-delimited text file with my data, perfect. However, if I open the file in Excel, the first row seems off by one column, and I have to insert an empty cell in A1, displacing the first row to the right, so that the headers match the columns. Why is this? If I retrieve elements from the topTable output they seem okay. The first column of the output contains numbers specifying the row locations of the genes. There is no header for that column. So the first row has one less element than the others. It's not a big deal, but... is there some parameters I should be specifying that I don't? I haven't found anything obvious. Thanks! Jose -- Dr. Jose I. de las Heras Email: J.delasHeras at ed.ac.uk The Wellcome Trust Centre for Cell Biology Phone: +44 (0)131 6513374 Institute for Cell & Molecular Biology Fax: +44 (0)131 6507360 Swann Building, Mayfield Road University of Edinburgh Edinburgh EH9 3JR UK
• 688 views
ADD COMMENT
0
Entering edit mode
@jdelasherasedacuk-1189
Last seen 8.8 years ago
United Kingdom
Sorry, please ignore... I got it now. I should have read more carefully the info about CSV files with "write.table", even if I don't use CSV files... Jose -- Dr. Jose I. de las Heras Email: J.delasHeras at ed.ac.uk The Wellcome Trust Centre for Cell Biology Phone: +44 (0)131 6513374 Institute for Cell & Molecular Biology Fax: +44 (0)131 6507360 Swann Building, Mayfield Road University of Edinburgh Edinburgh EH9 3JR UK
ADD COMMENT

Login before adding your answer.

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