Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[REVIEW]: MCMCvis: Tools to Visualize, Manipulate, and Summarize MCMC Output #640
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@jkarreth, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
Conflict of interest
Code of Conduct
referenced this issue
Mar 23, 2018
If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews
To fix this do the following two things:
For a list of things I can do to help you, just type:
@caseyyoungflesh, this is a nifty package to speedily process MCMC output. I could absolutely see myself using it, having hacked together similar functions for my own purposes.
The package does well what it is intended to do and it covers a main step of the Bayesian workflow: process MCMC output.
Two minor comments pertinent to the review criteria:
@jkarreth Many thanks. I'll respond here once these issues are addressed.
Responses to major comments
Responses to minor comments
Package version 0.10.0 is now on github.
MCMCvis version 0.10.0 has passed all CRAN checks. A new version will be submitted to CRAN soon. The most recent version github version can be installed with:
If you would like to include a link to your paper from your README use the following code snippet:
This is how it will look in your documentation:
We need your help!
Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following: