openjournals / joss-reviews

Reviews for the Journal of Open Source Software
Creative Commons Zero v1.0 Universal
721 stars 38 forks source link

[REVIEW]: Generative DAGs as an Interface Into Probabilistic Programming with the R Package causact #4415

Closed editorialbot closed 2 years ago

editorialbot commented 2 years ago

Submitting author: !--author-handle-->@flyaflya<!--end-author-handle-- (Adam Fleischhacker) Repository: https://github.com/flyaflya/causact/ Branch with paper.md (empty if default branch): Version: v0.4.1 Editor: !--editor-->@arfon<!--end-editor-- Reviewers: @joethorley, @ChristopherLucas Archive: 10.5281/zenodo.6949489

Status

status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/1e1eb42116078a46ded3986ab0b0e5b9"><img src="https://joss.theoj.org/papers/1e1eb42116078a46ded3986ab0b0e5b9/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/1e1eb42116078a46ded3986ab0b0e5b9/status.svg)](https://joss.theoj.org/papers/1e1eb42116078a46ded3986ab0b0e5b9)

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) by leaving comments 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

@joethorley & @ChristopherLucas, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @terrytangyuan know.

✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨

Checklists

πŸ“ Checklist for @joethorley

πŸ“ Checklist for @zhiiiyang

πŸ“ Checklist for @ChristopherLucas

editorialbot commented 2 years ago

:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.04415/status.svg)](https://doi.org/10.21105/joss.04415)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04415">
  <img src="https://joss.theoj.org/papers/10.21105/joss.04415/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04415/status.svg
   :target: https://doi.org/10.21105/joss.04415

This is how it will look in your documentation:

DOI

We need your help!

The 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:

flyaflya commented 2 years ago

Thank you @arfon, @joethorley, @ChristopherLucas, @zhiiiyang, and @terrytangyuan. We appreciate the time, effort, and helpful suggestions.