Search Results for "workforce management software"

renv is an R dependency management toolkit that enables project-level library isolation and reproducibility. It tracks package versions in a lockfile and can restore exact library states across machines or over time, making R projects portable and consistent.

This part of the book teaches you how to leverage the plotly R package to create a variety of interactive graphics. There are two main ways to creating a plotly object: either by transforming a ggplot2 object (via ggplotly()) into a plotly object or by directly initializing a plotly object with plot_ly()/plot_geo()/plot_mapbox(). Both approaches have somewhat complementary strengths and weaknesses, so it can pay off to learn both approaches. Moreover, both approaches are an implementation of...

rpkgs (in GitHub via hadley/r-pkgs) is the source (text + examples) for the book R Packages by Hadley Wickham and Jenny Bryan. The book teaches how to develop, document, test, and share R packages: the practices, tools, infrastructure, workflows, and best practices around package development in R. The repository contains the code, text, site content for building the book, examples, exercises, etc. It is not a software library to be loaded in R (except perhaps the examples), but a...

In this tutorial, we describe a workflow to ensure long-term reproducibility of R-based data analyses. The workflow leverages established tools and practices from software engineering. It combines the benefits of various open-source software tools including R Markdown, Git, Make, and Docker, whose interplay ensures seamless integration of version management, dynamic report generation conforming to various journal styles, and full cross-platform and long-term computational reproducibility. The workflow ensures meeting the primary goals that 1) the reporting of statistical results is consistent with the actual statistical results (dynamic report generation), 2) the analysis exactly reproduces at a later point in time even if the computing platform or software is changed (computational reproducibility), and 3) changes at any time (during development and post-publication) are tracked, tagged, and documented while earlier versions of both data and code remain accessible.