Messages de Rogue Scholar

language
Auteur Karthik Ram

Continuing our series of blog posts (day 1, day 2) this week about unconf 17.available Summary: Ever have trouble naming your software package? Find a great name and realize it’s already taken on CRAN, or further along in development on GitHub? The available package makes it easy to check for valid, available names, and also checks various sources for any unintended meanings.

Auteur Scott Chamberlain

Following up on Stefanie’s recap of unconf 17, we are following up this entire week with summaries of projects developed at the event. We plan to highlight 4-5 projects each day, with detailed posts from a handful of teams to follow.checkers Summary: checkers is a framework for reviewing analysis projects. It provides automated checks for best practices, using extensions on the goodpractice package.

Auteur Karthik Ram

Following up on Stefanie’s recap of unconf 17, we are following up this entire week with summaries of projects developed at the event. We plan to highlight 4-5 projects each day, with detailed posts from a handful of teams to follow.skimr Summary: skimr, a package inspired by Hadley Wickham’s precis package, aims to provide summary statistics iteratively and interactively as part of a pipeline.

We held our 4th annual unconference in Los Angeles, May 25-26, 2017. Scientists, R-software users and developers, and open data enthusiasts from academia, industry, government, and non-profits came together for two days to hack on projects they dreamed up and to give our online community an opportunity to connect in-person. The result?

Publié in Europe PMC News Blog
Auteur Europe PMC Team

Jo McEntyre, EMBL-EBI; Thomas Lemberger, EMBO; Mark Patterson, eLife; Kristen Rattan, Collaborative Knowledge Foundation; Alfonso Valencia, Barcelona Supercomputer Centre. The use of preprints in the life sciences offers tantalising opportunities to change the way research results are communicated and reused, and the work of ASAPbio has been key in engaging the scientific community to promote their uptake.

You can find members of the rOpenSci team at various meetings and workshops around the world. Come say ‘hi’, learn about how our packages can enable your research, or about our onboarding process for contributing new packages, discuss software sustainability or tell us how we can help you do open and reproducible research.Where’s rOpenSci?

Auteurs Scott Chamberlain, Stefanie Butland

There’s a lot of work that goes in to making software: the code that does the thing itself, unit testing, examples, tutorials, documentation, and support. rOpenSci software is created and maintained both by our staff and by our (awesome) community. In keeping with our aim to build capacity of software users and developers, three interns from our academic home at UC Berkeley are now working with us as well.

Auteur Thomas J. Leeper

There is no problem in science quite as frustrating as other peoples’ data . Whether it’s malformed spreadsheets, disorganized documents, proprietary file formats, data without metadata, or any other data scenario created by someone else, scientists have taken to Twitter to complain about it. As a political scientist who regularly encounters so-called “open data” in PDFs, this problem is particularly irritating.