<p><div><div><div><div data-show-faces="false" data-height="21" data-width="100" data-layout="button_count" data-send="true" data-href="https://www.r-bloggers.com/reproducible-research-and-a-repository-of-artifacts-a-rfc/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="https://random-remarks.net/2018/08/20/reproducible-research-and-a-repository-of-artifacts-a-rfc/"> R – Random Remarks</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<p>ThisÂ  work is still in progres. I think, however, it can already resonate with some people in the community. The communication I am hopeful for should lead to a better design and maybe getting valuable tools faster.</p>
<p>The main goal is to extend the base R’s history mechanism (see <code>?history</code>) which currently gives access to past commands run in R. What if, however, we could browse not only the commands but also the objects (<em>artifacts</em>)? Hence, theÂ <em>repository of artifacts</em>.</p>
<p>It is implemented by a number of packages. The two most important are: the <a rel="nofollow" href="https://github.com/lbartnik/repository" target="_blank">repository</a>Â which provides the basic logic of storing, processing and retrieving artifacts; and the <a rel="nofollow" href="https://github.com/lbartnik/ui" target="_blank">ui</a>Â which implements a basic, text-only user interface and hooks callbacks into R. The other packages are: <a rel="nofollow" href="https://github.com/lbartnik/storage" target="_blank">storage</a>, <a rel="nofollow" href="https://github.com/lbartnik/defer" target="_blank">defer</a> and <a rel="nofollow" href="https://github.com/lbartnik/utilities" target="_blank">utilities</a>.</p>
<p>Here are the basic rules of how repository of artifacts works: the state of R session after each command is examined and all R objects and plots are recorded, together with the information about their origin (parent objects). Thus, the complete graph of origin of each artifact can be retrieved from the repository: the complete sequence of R commands and their byproduct artifacts. Further explanation can be found in theÂ <a rel="nofollow" href="http://lbartnik.github.io/repository" target="_blank">current motivation and plan for future work</a>Â and examples of working with the repository are presented in thisÂ <a rel="nofollow" href="http://lbartnik.github.io/ui" target="_blank">tutorial</a>.</p>
<p>Questions I hope to explore with those interested are:</p>
<ul>
<li>since we all have different working styles, is this design a good fit for anyone besides me?</li>
<li>how well does it work in actual data analysis? are the tools available already (on CRAN, GitHub, etc.) sufficient? if not, what are the gaps that need to be addressed?</li>
<li>Â would anyone be willing to share the recordings of their historical R sessions? even better, track some in the repository? (assumed that it does not disrupt your work)</li>
<li>what are the gaps of the current design? how can it be improved or extended to make more sense?</li>
</ul>
	<p>
<div>
<div>To <strong>leave a comment</strong> for the author, please follow the link and comment on their blog: <strong><a href="https://random-remarks.net/2018/08/20/reproducible-research-and-a-repository-of-artifacts-a-rfc/"> R – Random Remarks</a></strong>.</div>
<hr>
<a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers.com</a> offers <strong><a rel="nofollow" href="https://feedburner.google.com/fb/a/mailverify?uri=RBloggers">daily e-mail updates</a></strong> about <a rel="nofollow" href="https://www.r-project.org/" title="The R Project for Statistical Computing">R</a> news and <a rel="nofollow" href="https://www.r-bloggers.com/search/tutorial" title="R tutorials">tutorials</a> on topics such as: <a rel="nofollow" href="https://www.r-bloggers.com/search/data%20science" title="Data science">Data science</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Big%20Data" title="Big Data">Big Data, <a rel="nofollow" href="https://www.r-users.com/" title="R jobs">R jobs</a>, visualization (<a rel="nofollow" href="https://www.r-bloggers.com/search/ggplot2" title="ggplot and ggplot2 tutorials">ggplot2</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/boxplot" title="Boxplots using lattice and ggplot2 tutorials">Boxplots</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/map" title="Maps and gis">maps</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/animation" title="Animation in R">animation</a>), programming (<a rel="nofollow" href="https://www.r-bloggers.com/search/RStudio" title="RStudio IDE for R">RStudio</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/sweave" title="Sweave and literate programming">Sweave</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/LaTeX" title="LaTeX in R">LaTeX</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/SQL" title="SQL and databases">SQL</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/eclipse" title="Eclipse IDE for R">Eclipse</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/git" title="git and github, Version Control System">git</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/hadoop" title="Large data in R using Hadoop">hadoop</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Web+Scraping" title="Web Scraping of google, facebook, yahoo, twitter and more using R">Web Scraping</a>) statistics (<a rel="nofollow" href="https://www.r-bloggers.com/search/regression" title="Regressions and ANOVA analysis tutorials">regression</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/PCA" title="principal component analysis tutorial">PCA</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/time+series" title="Time series">time series</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/trading" title="finance trading">trading</a>) and more...
<img width="1" alt="" src="http://feeds.feedburner.com/~r/RBloggers/~4/mJbj2izhq7U" height="1"></a></div>