<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Purrr on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/purrr/</link>
    <description>Recent content in Purrr on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 27 Feb 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/purrr/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Typo-shaming my Git commits</title>
      <link>https://www.rostrum.blog/2021/02/27/typos/</link>
      <pubDate>Sat, 27 Feb 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2021/02/27/typos/</guid>
      <description>The author at work (CC BY-SA 3.0 KaterBegemot)  tl;dr Nearly 10 per cent of the commits to this blog’s source involve typo fixes, according to a function I wrote to search commit messages via the {gh} package.
 Not my typo I’m sure you’ve seen consecutive Git commits from jaded developers like ‘fix problem’, ‘actually fix problem?’, ‘the fix broke something else’, ‘burn it all down’. Sometimes a few swear words will be thrown in for good measure (look no further than ‘Developers Swearing’ on Twitter).</description>
    </item>
    
    <item>
      <title>Take a {ghdump} to download GitHub repos</title>
      <link>https://www.rostrum.blog/2020/06/14/ghdump/</link>
      <pubDate>Sun, 14 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/06/14/ghdump/</guid>
      <description>My garbage GitHub repos being dumped onto my local machine (via openclipart.org, CC0 1.0)  tl;dr Run ghd_copy() from the {ghdump} package to either clone or download all the GitHub repositories for a given user. Intended for archival purposes or setting up a new computer.
The package comes with no guarantees and will likely be in a perpetual work-in-progress state. Please submit issues or pull requests.
 Clone army Situation:</description>
    </item>
    
    <item>
      <title>Iterate parameterised {xaringan} reports</title>
      <link>https://www.rostrum.blog/2020/03/12/knit-with-params/</link>
      <pubDate>Thu, 12 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/03/12/knit-with-params/</guid>
      <description>Driving a Wedge (via Giphy)  tl;dr You want to use R to generate multiple reports from a single template, each containing different data.
How? Create a parameterised RMarkdown template with a params YAML argument. Iterate over param values with rmarkdown::render() inside purrr::map().
I made a demo of this approach that focuses on parameterised {xaringan} slides. It includes a further {purrr} step with pagedown::chrome_print() to render the HTML outputs to PDF.</description>
    </item>
    
    <item>
      <title>Packages that Sparked Joy in 2019</title>
      <link>https://www.rostrum.blog/2019/12/27/pkgs-2019/</link>
      <pubDate>Fri, 27 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/12/27/pkgs-2019/</guid>
      <description>Marie Kondo (Netflix via Giphy)  Thank you package-makers I’ve used a lot of packages in 2019 and many have brought great joy to my R experience. Thank you to everyone who has created, maintained or contributed to a package this year.
Some particular packages of note for me have been:
 🤖 {usethis} by Hadley Wickham and Jenny Bryan 🦆 {drake} by Will Landau 🐈 {purrr} by Lionel Henry and Hadley Wickham  And some honourable mentions are:</description>
    </item>
    
    <item>
      <title>{altcheckr}: check image alt text from R</title>
      <link>https://www.rostrum.blog/2019/12/08/altcheckr/</link>
      <pubDate>Sun, 08 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/12/08/altcheckr/</guid>
      <description>tl;dr I’ve made a small R package called {altcheckr} that checks the accessibility of images on web pages. It has functions that (1) scrape attributes from HTML  elements on a web page and (2) apply simple rules to indicate the suitability of the alt text provided. To use:
remotes::install_github(&amp;quot;matt-dray/altcheckr&amp;quot;) images &amp;lt;- alt_get(&amp;quot;https://www.bbc.co.uk/news&amp;quot;) alt_check(images) I’m not an expert and the package has not been user tested.
 Accessibility A web site is accessible if everyone can engage with its content.</description>
    </item>
    
    <item>
      <title>Graphing the Relayverse of podcasts</title>
      <link>https://www.rostrum.blog/2019/02/14/relayverse/</link>
      <pubDate>Thu, 14 Feb 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/02/14/relayverse/</guid>
      <description>The Relay FM podcast network, visualised. View it here.  tl;dr I made an interactive graph network of the podcast host relationships on Relay FM using R. You can interact with it in a separate window and find out below how it was made.
I refreshed the data and style of the visualisation on 02 Jan 2020.
 Podcast networks Podcasting is becoming big business. Music-streaming giant Spotify just acquired the podcast network Gimlet for a reported $200 million.</description>
    </item>
    
    <item>
      <title>Tid-ye-text with geniusr</title>
      <link>https://www.rostrum.blog/2018/06/05/tid-ye-text/</link>
      <pubDate>Tue, 05 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/06/05/tid-ye-text/</guid>
      <description>Matt Dray
⚠️ Warning: this post contains offensive words. ⚠️
Genius? Kanye West released his latest album – ye – last week1 after a(nother) pretty turbulent and controversial period of his life2. So what’s been on his mind?
I think the real question is why don’t we scrape Yeezus’s lyrics from the web and analyse them using R? Obviously.
 Genius Genius is a website where you can upload and comment on song lyrics.</description>
    </item>
    
    <item>
      <title>R Trek: exploring stardates</title>
      <link>https://www.rostrum.blog/2018/04/14/r-trek-exploring-stardates/</link>
      <pubDate>Sat, 14 Apr 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/04/14/r-trek-exploring-stardates/</guid>
      <description>Captain’s log  Star date 71750.51. Our mission is to use R statistical software to extract star dates mentioned in the captain’s log from the scripts of Star Trek: The Next Generation and observe their progression over the course of the show’s seven seasons. There appears to be some mismatch in the frequency of digits after the decimal point – could this indicate poor ability to choose random numbers?</description>
    </item>
    
  </channel>
</rss>