Working together to push science forward
Happy rOpenSci users can be found at
As part of our continuous effort to improve rOpenSci infrastructure, we are rolling out a new service to automatically build and host documentation for all rOpenSci packages. The webpages are generated using the popular pkgdown system with our rOpenSci template, and get automatically published on https://docs.ropensci.org/. Some examples: https://docs.ropensci.org/drake/ https://docs.ropensci.org/magick/ https://docs.ropensci.org/writexl/ https://docs.ropensci.org/stplanr/ https://docs.ropensci.org/osmdata/ https://docs.ropensci.org/visdat/ https://docs.ropensci.org/tesseract/ We intend this to become the central place to find documentation for rOpenSci packages....
We’ve been following rOpenSci’s work for a long time, and we use several packages on a daily basis for our scientific projects, especially taxize to clean species names, rredlist to extract species IUCN statuses or [treeio](many probs with this post) to work with phylogenetic trees. rOpensci is a perfect incarnation of a vibrant and diverse community where people learn and develop new ideas, especially regarding scientific packages. We’ve also noticed how much the thorough review process improves the quality of the packages that join the rOpenSci ecosystem....
🔗 Introduction ramlegacy is a new R package to download, cache and read in all the different versions of the RAM Legacy Stock Assessment Database, a public database containing stock assessment results of commercially exploited marine populations from around the world. The package accomplishes all this by: Providing a function download_ramlegacy(), to download all the available versions of the RAM Database and cache them on the user’s computer in a location provided by the rappdirs package....
We strive for high quality in our suite of packages, in practice via a system of software peer review, and via packaging guidelines that keep growing. There is therefore a risk of increasing the workload of package authors, who already have a lot on their plate. To avoid that, when explaining how to do things in our dev guide, we recommend existing automated tools to authors. The usethis package implements this important principle: Automate that which can be automated....
As announced in our recent post about updates to our Software Peer Review system, all our package development, review and maintenance is available as an online book. Our goal is to update it approximately quarterly so it’s already time to present its second official version! You can read the changelog or this blog post to find out what’s new in our dev guide 0.2.0! 🔗 A more legit and accessible book Let’s start with very exciting news, the dev guide now has a cover, designed by Oz Locke from Locke Creatives!...
Happy rOpenSci users can be found at