NOTE: I’ll do my best to ensure the next post will have nothing to do with Twitter, and this post might not completely meet my R\u2076 criteria.<\/p>\n
A single, altruistic, nigh exuberant R tweet about slurping up a directory of CSVs devolved quickly — at least in my opinion, and partly (sadly) with my aid — into a thread that ultimately strayed from a crucial point: idiomatic is in the eye of the beholder<\/em>.<\/p>\n I’m not linking to the twitter thread, but there are enough folks with sufficient Klout scores on it (is Klout even still a thing?) that you can easily find it if you feel so compelled.<\/p>\n I’ll take a page out of the U.S. High School “write an essay” playbook and start with a definition of idiomatic<\/em>:<\/p>\n \n using, containing, or denoting expressions that are natural to a native speaker<\/em>\n<\/p><\/blockquote>\n That comes from idiom<\/em>:<\/p>\n \n a form of expression natural to a language, person, or group of people<\/em>\n<\/p><\/blockquote>\n I usually joke with my students that a strength (and weakness) of R is that there are ~twelve ways to do any given task. While the statement is deliberately hyperbolic, the core message is accurate: there’s more than one way to do most things in R. A cascading truth is: what makes one way more “correct” over another often comes down to idiom.<\/p>\n My rstudio::conf 2017 presentation included an example of my version of using You get data for all the “years” into a However, what if you want the year as a column? Many of these “datalogger” CSV data sets do not have a temporal “grouping” variable as they let the directory structure & naming conventions embed that bit of metadata. That information would be nice, though:<\/p>\n All three versions do the same thing, and each tribe understands each idiom.<\/p>\n The There are multiple ways to further extend the slurping example, but that’s not the point of the post.<\/p>\n Each set of snippets contains 100% valid R code. They accomplish the task and are idiomatic for each tribe<\/em>. Despite what any “mil gun feos turrach na latsa”<\/em> experts’ exchange would try to tell you, the best idiom is the one that works for you\/you & your collaborators and the one that gets you to the real work — data analysis — in the most straightforward & reproducible way possible (for you).<\/p>\n Idiomatic does not mean there’s only a singular One, True Way\u2122, and I think a whole host of us forget that at times.<\/p>\n Write good, clean, error-free, reproducible code.<\/p>\n Choose idioms that work best for you and your collaborators.<\/p>\n Adapt when necessary.<\/p>\n","protected":false},"excerpt":{"rendered":" NOTE: I’ll do my best to ensure the next post will have nothing to do with Twitter, and this post might not completely meet my R\u2076 criteria. A single, altruistic, nigh exuberant R tweet about slurping up a directory of CSVs devolved quickly — at least in my opinion, and partly (sadly) with my aid […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":3,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[91],"tags":[810],"class_list":["post-5996","post","type-post","status-publish","format-standard","hentry","category-r","tag-post"],"yoast_head":"\npurrr<\/code> for idiomatic CSV\/JSON directory slurping. There are lots of ways to do this in R (the point of the post is not really to show you how to do the directory slurping and it is unlikely that I’ll approve comments with code snippets about that task). Here are three. One from base R tribe, one from the data.table<\/code> tribe and one from the tidyverse<\/code> tribe:<\/p>\n# We need some files and we'll use base R to make some\r\ndir.create("readings")\r\nfor (i in 1970:2010) write.csv(mtcars, file.path("readings", sprintf("%s.csv", i)), row.names=FALSE)\r\n\r\nfils <- list.files("readings", pattern = ".csv$", full.names=TRUE)\r\n\r\ndo.call(rbind, lapply(fils, read.csv, stringsAsFactors=FALSE))\r\n\r\ndata.table::rbindlist(lapply(fils, data.table::fread))\r\n\r\npurrr::map_df(fils, readr::read_csv)<\/code><\/pre>\ndata.frame<\/code>, data.table<\/code> and tibble<\/code> (respectively) with those three “phrases”.<\/p>\ndo.call(rbind, lapply(fils, function(x) {\r\n f <- read.csv(x, stringsAsFactors=FALSE)\r\n f$year <- gsub("^readings\/|\\\\.csv$", "", x)\r\n f\r\n}))\r\n\r\ndt <- data.table::rbindlist(lapply(fils, data.table::fread), idcol="year")\r\ndt[, year := gsub("^readings\/|\\\\.csv$", "", fils[year])]\r\n\r\npurrr::map_df(fils, readr::read_csv, .id = "year") %>% \r\n dplyr::mutate(year = stringr::str_replace_all(fils[as.numeric(year)],\r\n "^readings\/|\\\\.csv$", ""))<\/code><\/pre>\ndata.table<\/code> and tidyverse<\/code> versions get you much faster file reading and the ability to “fill” missing columns — another common slurping task. You can hack something together in base R to do column fills (you’ll find a few StackOverflow answers that accomplish such a task) but you will likely decide to choose one of the other idioms for that and become equally as comfortable in that new idiom.<\/p>\n