search for: d41586

...(read.csv is no different) is a classic issue in bioinformatics. It seems like every practitioner ends up encountering this issue in due time. E.g. https://pubmed.ncbi.nlm.nih.gov/15214961/ https://genomebiology.biomedcentral.com/articles/10.1186/s13059-016-1044-7 https://www.nature.com/articles/d41586-021-02211-4 https://www.theverge.com/2020/8/6/21355674/human-genes-rename-microsoft-excel-misreading-dates On Tue, Apr 16, 2024 at 3:46?AM jing hua zhao <jinghuazhao at hotmail.com> wrote: > > Dear R-developers, > > I came to a somewhat unexpected behaviour of read.csv() which...

All: **OFF TOPIC** -- feel free to respond to me personally, but I will not respond to on-list comments. https://www.nature.com/articles/d41586-023-03635-w Many of you will no doubt know of this already. I hope it will be of interest to all concerned with research replicability, integrity, and the public's view of the value of scientific research. Best to all (and happy Thanksgiving to US readers), Bert

Dear R-developers, I came to a somewhat unexpected behaviour of read.csv() which is trivial but worthwhile to note -- my data involves a protein named "1433E" but to save space I drop the quote so it becomes, Gene,SNP,prot,log10p YWHAE,13:62129097_C_T,1433E,7.35 YWHAE,4:72617557_T_TA,1433E,7.73 Both read.cv() and readr::read_csv() consider prot(ein) name as (possibly confused by