Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REVIEW]: pymdp: A Python library for active inference in discrete state spaces #4098

Closed
40 tasks done
whedon opened this issue Jan 25, 2022 · 107 comments
Closed
40 tasks done
Assignees
Labels
accepted Matlab published Papers published in JOSS Python recommend-accept Papers recommended for acceptance in JOSS. review

Comments

@whedon
Copy link

whedon commented Jan 25, 2022

Submitting author: @conorheins (Conor Heins)
Repository: https://github.com/infer-actively/pymdp
Branch with paper.md (empty if default branch): master
Version: v0.0.5
Editor: @emdupre
Reviewers: @seankmartin, @patrickmineault
Archive: 10.5281/zenodo.6484849

⚠️ JOSS reduced service mode ⚠️

Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.

Status

status

Status badge code:

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

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

@seankmartin & @patrickmineault, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:

  1. Make sure you're logged in to your GitHub account
  2. Be sure to accept the invite at this URL: https://github.com/openjournals/joss-reviews/invitations

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @emdupre 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

Review checklist for @seankmartin

✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨

Conflict of interest

  • I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

General checks

  • Repository: Is the source code for this software available at the repository url?
  • License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@conorheins) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
  • Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines

Functionality

  • Installation: Does installation proceed as outlined in the documentation?
  • Functionality: Have the functional claims of the software been confirmed?
  • Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

  • A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
  • Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
  • A statement of need: Does the paper have a section titled 'Statement of Need' that clearly states what problems the software is designed to solve and who the target audience is?
  • State of the field: Do the authors describe how this software compares to other commonly-used packages?
  • Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
  • References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

Review checklist for @patrickmineault

✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨

Conflict of interest

  • I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

General checks

  • Repository: Is the source code for this software available at the repository url?
  • License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@conorheins) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
  • Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines

Functionality

  • Installation: Does installation proceed as outlined in the documentation?
  • Functionality: Have the functional claims of the software been confirmed?
  • Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

  • A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
  • Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
  • A statement of need: Does the paper have a section titled 'Statement of Need' that clearly states what problems the software is designed to solve and who the target audience is?
  • State of the field: Do the authors describe how this software compares to other commonly-used packages?
  • Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
  • References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?
@whedon
Copy link
Author

whedon commented Jan 25, 2022

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @seankmartin, @patrickmineault it looks like you're currently assigned to review this paper 🎉.

⚠️ JOSS reduced service mode ⚠️

Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.

⭐ Important ⭐

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:

  1. Set yourself as 'Not watching' https://github.com/openjournals/joss-reviews:

watching

  1. You may also like to change your default settings for this watching repositories in your GitHub profile here: https://github.com/settings/notifications

notifications

For a list of things I can do to help you, just type:

@whedon commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Jan 25, 2022

Software report (experimental):

github.com/AlDanial/cloc v 1.88  T=0.16 s (396.3 files/s, 143004.9 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          30           1995           1963           4615
Jupyter Notebook                11              0           9723           1496
MATLAB                           9            558            790           1406
Markdown                         2             94              0            234
YAML                             2             10             10             42
reStructuredText                 8             29             40             36
DOS Batch                        1              8              1             26
make                             1              4              7              9
-------------------------------------------------------------------------------
SUM:                            64           2698          12534           7864
-------------------------------------------------------------------------------


Statistical information for the repository '0f55aadd4137f41905c03063' was
gathered on 2022/01/25.
The following historical commit information, by author, was found:

Author                     Commits    Insertions      Deletions    % of changes
Alexander Kiefer                 2             5              3            0.01
Beren                            4           193             54            0.32
Brennan Klein                    1             1              1            0.00
Conor Heins                     87          8074           2193           13.16
alec-tschantz                   55          8626           6334           19.18
arun                             3            88             73            0.21
conorheins                     237         26192          26172           67.13

Below are the number of rows from each author that have survived and are still
intact in the current revision:

Author                     Rows      Stability          Age       % in comments
Alexander Kiefer              5          100.0          6.5                0.00
Beren                        13            6.7         20.0               15.38
alec-tschantz              1245           14.4         18.4               12.21
arun                         13           14.8         11.6                0.00
conorheins                 7297           27.9          7.3                9.09

@whedon
Copy link
Author

whedon commented Jan 25, 2022

PDF failed to compile for issue #4098 with the following error:

 Can't find any papers to compile :-(

@emdupre
Copy link
Member

emdupre commented Jan 25, 2022

@whedon generate pdf from branch paper_branch

@whedon
Copy link
Author

whedon commented Jan 25, 2022

Attempting PDF compilation from custom branch paper_branch. Reticulating splines etc...

@whedon
Copy link
Author

whedon commented Jan 25, 2022

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@emdupre
Copy link
Member

emdupre commented Jan 25, 2022

@whedon check references from branch paper_branch

@whedon
Copy link
Author

whedon commented Jan 25, 2022

Attempting to check references... from custom branch paper_branch

@whedon
Copy link
Author

whedon commented Jan 25, 2022

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1371/journal.pone.0006421 is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.1162/neco_a_01354 is OK
- 10.1080/17588928.2015.1020053 is OK
- 10.1038/s41598-018-38246-3 is OK
- 10.1561/2200000001 is OK
- 10.1167/jov.20.4.12 is OK
- 10.1038/ncomms14218 is OK
- 10.3390/e22050552 is OK
- 10.1162/neco.1992.4.3.415 is OK
- 10.1016/j.neuroimage.2004.07.041 is OK
- 10.1080/01621459.2017.1285773 is OK
- 10.1126/science.1238406 is OK
- 10.1007/s00422-012-0512-8 is OK
- 10.1016/j.tics.2011.11.018 is OK
- 10.1162/neco_a_01357 is OK
- 10.1109/IJCNN48605.2020.9207382 is OK
- 10.1016/0166-2236(83)90190-X is OK
- 10.1523/JNEUROSCI.11-03-00641.1991 is OK
- 10.1162/NECO_a_00912 is OK
- 10.3390/e21030257 is OK
- 10.3389/frobt.2019.00020 is OK
- 10.1007/s00422-018-0785-7 is OK
- 10.1371/journal.pcbi.1007805 is OK
- 10.1109/ICASSP40776.2020.9054364 is OK
- 10.1016/B978-0-12-372560-8.X5000-1 is OK
- 10.1038/nrn2787 is OK
- 10.1016/j.jmp.2020.102447 is OK
- 10.1016/S0004-3702(98)00023-X is OK
- 10.1162/neco_a_01351 is OK
- 10.1093/cercor/bhu159 is OK
- 10.1016/j.drugalcdep.2020.108208 is OK
- 10.1503/jpn.200032 is OK
- 10.31234/osf.io/b4jm6 is OK
- 10.1016/j.neuroimage.2008.02.054 is OK
- 10.1016/j.jmp.2020.102348 is OK
- 10.1007/978-3-030-64919-7_1 is OK
- 10.1016/j.neubiorev.2016.06.022 is OK
- 10.1162/neco.1995.7.5.889 is OK
- 10.1037/13536-000 is OK
- 10.1016/j.neunet.2021.05.010 is OK
- 10.1109/LRA.2021.3090015 is OK
- 10.1016/B978-0-323-88506-5.50066-8 is OK
- 10.1007/s00422-019-00805-w is OK
- 10.3390/e23020198 is OK
- 10.1080/10407413.2021.1965480 is OK
- 10.1098/rsif.2013.0475 is OK
- 10.7554/eLife.41703 is OK
- 10.1162/neco_a_00999 is OK

MISSING DOIs

- 10.1162/neco_a_01427 may be a valid DOI for title: Chance-Constrained Active Inference
- 10.1017/s0140525x19001353 may be a valid DOI for title: Generative models as parsimonious descriptions of sensorimotor loops
- 10.7551/mitpress/7111.003.0009 may be a valid DOI for title: Perceptions as hypotheses
- 10.31234/osf.io/2rzu5 may be a valid DOI for title: Active inference, selective attention, and the cocktail party problem
- 10.1016/j.schres.2021.07.032 may be a valid DOI for title: Everything is connected: Inference and attractors in delusions
- 10.31234/osf.io/bsuh8 may be a valid DOI for title: Long-term stability of computational parameters during approach-avoidance conflict in a transdiagnostic psychiatric patient sample

INVALID DOIs

- None

@emdupre
Copy link
Member

emdupre commented Jan 25, 2022

Hi everyone 👋 Thanks again for agreeing to review this submission ! The review will take place in this issue.

Whenever possible, please open relevant issues on the linked software repository (and cross-link them with this issue) rather than discussing them here. This helps to make sure that feedback is translated into actionable items to improve the software.

If you aren't sure how to get started, please see the Reviewing for JOSS guide -- and, of course, feel free to ping me with any questions !

@seankmartin
Copy link

Cool, thanks!
I should be able to get to doing the review fairly soon

@seankmartin
Copy link

@whedon commands

@whedon
Copy link
Author

whedon commented Jan 25, 2022

Here are some things you can ask me to do:

# List Whedon's capabilities
@whedon commands

# List of editor GitHub usernames
@whedon list editors

# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers

EDITORIAL TASKS

# Compile the paper
@whedon generate pdf

# Compile the paper from alternative branch
@whedon generate pdf from branch custom-branch-name

# Ask Whedon to check the references for missing DOIs
@whedon check references

# Ask Whedon to check repository statistics for the submitted software
@whedon check repository

@seankmartin
Copy link

I'm in progress with the review.
I've raised a non-blocking issue about some missing API documentation here infer-actively/pymdp#67.
The paper is missing an explicit summary section, which I think should be added.
Will post a final update after checking functionality!

@seankmartin
Copy link

@whedon remind @seankmartin in 4 days

@whedon
Copy link
Author

whedon commented Feb 1, 2022

I'm sorry @seankmartin, I'm afraid I can't do that. That's something only editors are allowed to do.

@patrickmineault
Copy link

I'm going to wait until @seankmartin completes a first pass until I look at this.

@emdupre
Copy link
Member

emdupre commented Feb 2, 2022

@whedon remind @seankmartin in 3 days

@whedon
Copy link
Author

whedon commented Feb 2, 2022

Reminder set for @seankmartin in 3 days

@emdupre
Copy link
Member

emdupre commented Feb 2, 2022

@seankmartin I've set the reminder :) Thanks for starting on this and cross-linking the opened issue !

@whedon
Copy link
Author

whedon commented Feb 5, 2022

👋 @seankmartin, please update us on how your review is going (this is an automated reminder).

1 similar comment
@whedon
Copy link
Author

whedon commented Feb 8, 2022

👋 @seankmartin, please update us on how your review is going (this is an automated reminder).

@whedon
Copy link
Author

whedon commented Feb 8, 2022

👋 @patrickmineault, please update us on how your review is going (this is an automated reminder).

@editorialbot
Copy link
Collaborator

Done! branch is now master

@emdupre
Copy link
Member

emdupre commented May 2, 2022

@editorialbot check references

@editorialbot
Copy link
Collaborator

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1371/journal.pone.0006421 is OK
- 10.1162/neco_a_01427 is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.1162/neco_a_01354 is OK
- 10.1080/17588928.2015.1020053 is OK
- 10.1038/s41598-018-38246-3 is OK
- 10.1561/2200000001 is OK
- 10.1167/jov.20.4.12 is OK
- 10.1038/ncomms14218 is OK
- 10.3390/e22050552 is OK
- 10.1162/neco.1992.4.3.415 is OK
- 10.1016/j.neuroimage.2004.07.041 is OK
- 10.1080/01621459.2017.1285773 is OK
- 10.1126/science.1238406 is OK
- 10.1007/s00422-012-0512-8 is OK
- 10.1016/j.tics.2011.11.018 is OK
- 10.1162/neco_a_01357 is OK
- 10.1109/IJCNN48605.2020.9207382 is OK
- 10.1016/0166-2236(83)90190-X is OK
- 10.1523/JNEUROSCI.11-03-00641.1991 is OK
- 10.1162/NECO_a_00912 is OK
- 10.3390/e21030257 is OK
- 10.3389/frobt.2019.00020 is OK
- 10.1007/s00422-018-0785-7 is OK
- 10.1371/journal.pcbi.1007805 is OK
- 10.1109/ICASSP40776.2020.9054364 is OK
- 10.1016/B978-0-12-372560-8.X5000-1 is OK
- 10.1038/nrn2787 is OK
- 10.1016/j.jmp.2020.102447 is OK
- 10.1016/S0004-3702(98)00023-X is OK
- 10.1162/neco_a_01351 is OK
- 10.1093/cercor/bhu159 is OK
- 10.1016/j.drugalcdep.2020.108208 is OK
- 10.1503/jpn.200032 is OK
- 10.1016/j.jmp.2021.102632 is OK
- 10.1016/j.neuroimage.2008.02.054 is OK
- 10.1016/j.jmp.2020.102348 is OK
- 10.1007/978-3-030-64919-7_1 is OK
- 10.1016/j.ijar.2018.11.002 is OK
- 10.1098/rstb.1980.0090 is OK
- 10.1016/j.neubiorev.2016.06.022 is OK
- 10.1162/neco.1995.7.5.889 is OK
- 10.1037/13536-000 is OK
- 10.1007/978-3-030-93736-2_48 is OK
- 10.1016/j.neunet.2021.05.010 is OK
- 10.1109/LRA.2021.3090015 is OK
- 10.1016/B978-0-323-88506-5.50066-8 is OK
- 10.1007/s00422-019-00805-w is OK
- 10.3390/e23020198 is OK
- 10.1080/10407413.2021.1965480 is OK
- 10.1098/rsif.2013.0475 is OK
- 10.7554/eLife.41703 is OK
- 10.1162/neco_a_00999 is OK
- 10.1016/j.neubiorev.2021.09.038 is OK
- 10.1016/j.schres.2021.07.032 is OK
- 10.1038/s41598-021-91308-x is OK

MISSING DOIs

- 10.3389/fpsyg.2022.855074 may be a valid DOI for title: Enactive-Dynamic Social Cognition and Active Inference

INVALID DOIs

- None

@emdupre
Copy link
Member

emdupre commented May 2, 2022

Thank you, @conorheins ! I have one last reference request, since the included Hipólito reference was published in Frontiers over the weekend. Can you please update this reference to:

@article{hipolito2021enactive,
author = {Hip{\'o}lito, In{\^e}s and van Es, Thomas},
title = {Enactive-Dynamic Social Cognition and Active Inference},
journal = {Frontiers in Psychology},
volume = {13},
year = {2022},
url = {https://www.frontiersin.org/article/10.3389/fpsyg.2022.855074},
doi = {10.3389/fpsyg.2022.855074},
issn = {1664-1078}
}

@conorheins
Copy link

Hi @emdupre , I removed that reference as well as several others that weren't used here (some of them were left over from the arxiv version). Thanks

@emdupre
Copy link
Member

emdupre commented May 2, 2022

@editorialbot check references

@editorialbot
Copy link
Collaborator

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1371/journal.pone.0006421 is OK
- 10.1162/neco_a_01427 is OK
- 10.1162/neco_a_01354 is OK
- 10.1080/17588928.2015.1020053 is OK
- 10.1038/s41598-018-38246-3 is OK
- 10.1016/j.neuroimage.2004.07.041 is OK
- 10.1007/s00422-012-0512-8 is OK
- 10.1016/j.tics.2011.11.018 is OK
- 10.1162/neco_a_01357 is OK
- 10.1109/IJCNN48605.2020.9207382 is OK
- 10.1162/NECO_a_00912 is OK
- 10.3390/e21030257 is OK
- 10.3389/frobt.2019.00020 is OK
- 10.1007/s00422-018-0785-7 is OK
- 10.1371/journal.pcbi.1007805 is OK
- 10.1109/ICASSP40776.2020.9054364 is OK
- 10.1016/B978-0-12-372560-8.X5000-1 is OK
- 10.1038/nrn2787 is OK
- 10.1016/j.jmp.2020.102447 is OK
- 10.1016/S0004-3702(98)00023-X is OK
- 10.1162/neco_a_01351 is OK
- 10.1093/cercor/bhu159 is OK
- 10.1016/j.drugalcdep.2020.108208 is OK
- 10.1503/jpn.200032 is OK
- 10.1016/j.jmp.2021.102632 is OK
- 10.1016/j.neuroimage.2008.02.054 is OK
- 10.1016/j.jmp.2020.102348 is OK
- 10.1007/978-3-030-64919-7_1 is OK
- 10.1016/j.ijar.2018.11.002 is OK
- 10.1098/rstb.1980.0090 is OK
- 10.1016/j.neubiorev.2016.06.022 is OK
- 10.1162/neco.1995.7.5.889 is OK
- 10.1037/13536-000 is OK
- 10.1007/978-3-030-93736-2_48 is OK
- 10.1016/j.neunet.2021.05.010 is OK
- 10.1109/LRA.2021.3090015 is OK
- 10.1016/B978-0-323-88506-5.50066-8 is OK
- 10.1007/s00422-019-00805-w is OK
- 10.3390/e23020198 is OK
- 10.1080/10407413.2021.1965480 is OK
- 10.1098/rsif.2013.0475 is OK
- 10.7554/eLife.41703 is OK
- 10.1162/neco_a_00999 is OK
- 10.1016/j.neubiorev.2021.09.038 is OK
- 10.1016/j.schres.2021.07.032 is OK
- 10.1038/s41598-021-91308-x is OK

MISSING DOIs

- None

INVALID DOIs

- None

@emdupre
Copy link
Member

emdupre commented May 2, 2022

@openjournals/joss-eics, this is ready for final review !

@kyleniemeyer
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1371/journal.pone.0006421 is OK
- 10.1162/neco_a_01427 is OK
- 10.1162/neco_a_01354 is OK
- 10.1080/17588928.2015.1020053 is OK
- 10.1038/s41598-018-38246-3 is OK
- 10.1016/j.neuroimage.2004.07.041 is OK
- 10.1007/s00422-012-0512-8 is OK
- 10.1016/j.tics.2011.11.018 is OK
- 10.1162/neco_a_01357 is OK
- 10.1109/IJCNN48605.2020.9207382 is OK
- 10.1162/NECO_a_00912 is OK
- 10.3390/e21030257 is OK
- 10.3389/frobt.2019.00020 is OK
- 10.1007/s00422-018-0785-7 is OK
- 10.1371/journal.pcbi.1007805 is OK
- 10.1109/ICASSP40776.2020.9054364 is OK
- 10.1016/B978-0-12-372560-8.X5000-1 is OK
- 10.1038/nrn2787 is OK
- 10.1016/j.jmp.2020.102447 is OK
- 10.1016/S0004-3702(98)00023-X is OK
- 10.1162/neco_a_01351 is OK
- 10.1093/cercor/bhu159 is OK
- 10.1016/j.drugalcdep.2020.108208 is OK
- 10.1503/jpn.200032 is OK
- 10.1016/j.jmp.2021.102632 is OK
- 10.1016/j.neuroimage.2008.02.054 is OK
- 10.1016/j.jmp.2020.102348 is OK
- 10.1007/978-3-030-64919-7_1 is OK
- 10.1016/j.ijar.2018.11.002 is OK
- 10.1098/rstb.1980.0090 is OK
- 10.1016/j.neubiorev.2016.06.022 is OK
- 10.1162/neco.1995.7.5.889 is OK
- 10.1037/13536-000 is OK
- 10.1007/978-3-030-93736-2_48 is OK
- 10.1016/j.neunet.2021.05.010 is OK
- 10.1109/LRA.2021.3090015 is OK
- 10.1016/B978-0-323-88506-5.50066-8 is OK
- 10.1007/s00422-019-00805-w is OK
- 10.3390/e23020198 is OK
- 10.1080/10407413.2021.1965480 is OK
- 10.1098/rsif.2013.0475 is OK
- 10.7554/eLife.41703 is OK
- 10.1162/neco_a_00999 is OK
- 10.1016/j.neubiorev.2021.09.038 is OK
- 10.1016/j.schres.2021.07.032 is OK
- 10.1038/s41598-021-91308-x is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator

👋 @openjournals/joss-eics, this paper is ready to be accepted and published.

Check final proof 👉 openjournals/joss-papers#3194

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3194, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@kyleniemeyer
Copy link

Hi @conorheins, I'm the AEIC on duty this week doing some final checks.

In your article, can you remove the explicit arXiv URL from the end of the statement of need section? The citation you included is sufficient and includes the URL.

Similarly, the article already links to the software repository, so I think you should remove the URL pointing to that in the same paragraph. If you really want to keep a link in the text, perhaps just make the word "repository" a hyperlink like [repository](https://github.com/infer-actively/pymdp).

In the Introduction first paragraph, can you wrap "e.g." with commas, like "... in, e.g., psychophysics ...". Similarly, please add a comma after "e.g." in later uses.

It looks like the Parr et al. 2020 article from Cerebral Cortex is missing a DOI, can you check if one is available?

conorheins added a commit to infer-actively/pymdp that referenced this issue May 4, 2022
-removed github URL from statement of need section
-wrapped e.g.'s in commas
-added doi to parr2020prefrontal citation

In response to: openjournals/joss-reviews#4098 (comment)
@conorheins
Copy link

Hi @kyleniemeyer, thanks for the final checks. I have made the changes you requested, let me know if anything else needs fixing.

@kyleniemeyer
Copy link

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@kyleniemeyer
Copy link

@editorialbot accept

@editorialbot
Copy link
Collaborator

Doing it live! Attempting automated processing of paper acceptance...

@editorialbot
Copy link
Collaborator

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

@editorialbot
Copy link
Collaborator

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.04098 joss-papers#3198
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.04098
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels May 4, 2022
@kyleniemeyer
Copy link

Congratulations @conorheins on your article's publication in JOSS! (Conor Heins)

Many thanks to @seankmartin and @patrickmineault for reviewing this, and @emdupre for editing.

@editorialbot
Copy link
Collaborator

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

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.04098/status.svg)](https://doi.org/10.21105/joss.04098)

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

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

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:

@conorheins
Copy link

Thanks very much (on behalf of all the authors) for the great news, and thank you again @seankmartin and @patrickmineault for your helpful reviews. And finally many thanks @emdupre for all your help/patience during the review process!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Matlab published Papers published in JOSS Python recommend-accept Papers recommended for acceptance in JOSS. review
Projects
None yet
Development

No branches or pull requests

7 participants