Two pending features to metricsgraphics

I’ve been slowly prodding the metricsgraphics package towards a 1.0.0 release, but there are some rough edges that still need sorting out. One of them is the ability to handle passing in variables for the x & y accessor values (you can pass in bare and quoted strings). This can now be achieved (in the dev01 branch) via mjs_plot_ and in mjs_plot proper in the github main branch thanks to a PR by Jonathan Owen. If everything stays stable with the PR, I’ll just fold the code into mjs_plot for the 0.9.0 CRAN release.

One other pending feature is the ability to turn basic (single geom_) ggplot objects into metricsgraphics plots. Sometimes it’s just easier/nicer to “think” in ggplot and it may be the case that one might have coded a quick histogram/scatter/line plot in ggplot and want an equally quick interactive version. This can also now be achieved (again, in beta) via as_mjsplot. While the previous addition is fairly self-explanatory, this new one needs a few examples. Please note that the package installation is coming from the dev01 branch:

devtools::install_github("hrbrmstr/metricsgraphics", ref="dev01") 
dat <- data.frame(year=seq(1790, 1970, 10),
movies <- movies[sample(nrow(movies), 1000), ]
gg1 <- ggplot(dat, aes(x=year, y=uspop)) + geom_line()
gg2 <- ggplot(dat, aes(x=year, y=uspop)) + geom_point()
gg3 <- ggplot(movies, aes(rating)) + geom_histogram()
gg4 <- ggplot(movies, aes(rating)) + geom_histogram(binwidth = 0.1)

Which you can see below:

As you can see, as_mjsplot will do it’s best to figure out the bins (if using geom_histogram) and also axis labels. Support for converting geom_vline and geom_hline to markers and baselines (respectively) is a work in progress.

I’ve only done limited testing with some basic single geom_ constructs, but if there are any bugs with it or feature requests (remember, the MetricsGraphics.js library has a very limited repertoire) please post an issue on GitHub tagging the dev01 branch.

Get by with a little (R) help from your friends (at GitHub)

@JennyBryan posted her slides from the 2015 R Summit and they are a must-read for instructors and even general stats/R-folk. She’s one of the foremost experts in R+GitHub and her personal and class workflows provide solid patterns worth emulation.

One thing she has mentioned a few times—and included in her R Summit talk—is the idea that you can lean on GitHub when official examples of a function are “kind of thin”. She uses a search for vapply as an example, showing how to search for uses of vapply in CRAN (there’s a read-only CRAN mirror on GitHub) and in GitHub R code in general.

I remember throwing together a small function to kick up a browser from R for those URLs (in a response to one of her tweets), but realized this morning (after reading her slides last night) that it’s possible to not leave RStudio to get these GitHub search results (or, at least the first page of results). So, I threw together this gist which, when sourced, provides a ghelp function. This is the code:

ghelp <- function(topic, in_cran=TRUE) {
  require(htmltools) # for getting HTML to the viewer
  require(rvest)     # for scraping & munging HTML
  # github search URL base
  base_ext_url <- ""
  ext_url <- sprintf(base_ext_url, topic)
  # if searching with user:cran (the default) add that to the URL  
  if (in_cran) ext_url <- paste(ext_url, "+user%3Acran", sep="", collapse="")
  # at the time of writing, "rvest" and "xml2" are undergoing some changes, so
  # accommodate those of us who are on the bleeding edge of the hadleyverse
  # either way, we are just extracting out the results <div> for viewing in 
  # the viewer pane (it works in plain ol' R, too)
  if (packageVersion("rvest") < "") { 
    pg <- html(ext_url)
    res_div <- paste(capture.output(html_node(pg, "div#code_search_results")), collapse="")
  } else {
    pg <- read_html(ext_url)
    res_div <- as.character(html_nodes(pg, "div#code_search_results"))
  # clean up the HTML a bit   
  res_div <- gsub('How are these search results\\? <a href="/contact">Tell us!</a>', '', res_div)
  # include a link to the results at the top of the viewer
  res_div <- gsub('href="/', 'href="', res_div)
  # build the viewer page, getting CSS from github-proper and hiding some cruft
  for_view <- sprintf('<html><head><link crossorigin="anonymous" href="" media="all" rel="stylesheet" /><style>body{padding:20px}</style></head><body><a href="%s">Show on GitHub</a><hr noshade size=1/>%s</body></html>', ext_url, res_div)
  # this makes it show in the viewer (or browser if you're using plain R)

Now, when you type ghelp("vapply"), you’ll get:


in the viewer pane (and similar with ghelp("vapply", in_cran=FALSE)). Clicking the top link will take you to the search results page on GitHub (in your default web browser), and all the other links will pop out to a browser as well.

If you’re the trusting type, you can devtools::source_gist('32e9c140129d7d51db52') or just add this to your R startup functions (or add it to your personal helper package).

There’s definitely room for some CSS hacking and it would be fairly straightforward to get all the search results into the viewer by following the pagination links and stitching them all together (an exercise left to the reader).