Testing is a crucial component to any software package. Testing makes surethat your code does what you expect it to do; and importantly, makes it safer to makechanges moving forward because a good test suite will tell you if a change has brokenexisting functionality. Our recent community call on testing is a niceplace to get started with testing. One way to make testing even harder is through including HTTP requests.
As of earlier this year, we are now automatically building binaries and pkgdown documentation for all rOpenSci packages. One issue we encountered is that some packages include vignettes that require some special tools/data/credentials, which are unavailable on generic build servers. This post explains how to include such vignettes and articles in your package.
We’re thrilled to be introducing a new member of our team. Mark Padgham has joined rOpenSci as a Software Research Scientist working full-time from Münster, Germany. Mark will play a key role in research and development of statistical software standards and expanding our efforts in software peer review, enabled by new funding from the Sloan Foundation.
The United States Deparment of Agriculture National AgriculturalStatistics Service (USDA-NASS) provides a wide range of agriculturaldata that includes animal, crop, demographic, economic, andenvironmental measures across a number of geographies and time periods.This data is available by direct download or queriable via theQuick Stats interface.
rOpenSci thrives because of volunteer contributions from community members - submitting and reviewing R packages, serving as editors for software peer review, writing blog posts, sharing information about packages and resources, contributing code and documentation and answering others’ questions. Recently our fiscal sponsor, NumFOCUS, gave us an opportunity to nominate two contributors for recognition at the NumFOCUS annual summit.
Studies of muscle physiology often rely on closed-source, proprietary software for not only recording data but also for data wrangling and analyses. Although specialized software might be necessary to record data from highly-specialized equipment, data wrangling and analyses should be free from this constraint.
To the uninitiated, software testing may seem variously boring, daunting or bogged down in obscure terminology. However, it has the potential to be enormously useful for people developing software at any level of expertise, and can often be put into practice with relatively little effort. Our 1-hour Call will include two speakers and at least 20 minutes for Q &
Today we are pleased to announce that we have received new funding from the Gordon and Betty Moore Foundation. The $894k grant will help us improve infrastructure for R packages and enable us to move towards a science first package ecosystem for the R community. You may have already noticed some developments on this front when we announced our automated documentation server back in June.
In May 2019 version 0.2.0 of tidync was approved by rOpenSci and accepted to CRAN. Here we provide a quick overview of the typical workflow with some pseudo-code for the main functions in tidync. This overview is enough to read if you just want to try out the package on your own data.
Theme song: PSA by Jay-Z We announced the testing version of skimr v2 onJune 19, 2018. After more than ayear of (admittedly intermittent) work, we’re thrilled to be able to say thatthe package is ready to go to CRAN. So, what happened over the last year? Andwhy are we so excited for v2? Wait, what is a “skimr”? skimr is an R package for summarizing your data.
