-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
[PRE REVIEW]: Re-Envisioning Numerical Information Field Theory (NIFTy.re): A Library for Gaussian Processes and Variational Inference #6382
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Wordcount for |
Failed to discover a valid open source license |
|
@editorialbot set NIFTy_8 as branch |
Done! branch is now NIFTy_8 |
|
@editorialbot check repository |
|
Failed to discover a |
@editorialbot set paper as branch |
Done! branch is now paper |
@Edenhofer — Thanks for your submission! All the suitable JOSS editors are currently working at capacity so I'm going to "waitlist" this review until an editor with the relevant expertise is available to take it on. Thanks for your patience! In the meantime, there are a few issues with your paper ☝️ Can you check the affiliations and make sure you have a "Statement of need" section in the paper? |
Thanks for opening the pre review issue so quickly! I see that having the paper branch's history being unrelated to the main development branch's history is undesirable for JOSS. I merged both histories so that the paper and the code now share a history.
The paper has a "statement of need" section and Reimar not having an affiliation was intentional. Reimar left academia and his contribution to this work are not related to his employer. I added a placeholder affiliation for now to make the bot happy :) I will discuss further with Reimar what we want to put there. |
I talked with Reimar and he prefers to have no affiliation. I thus added a new affiliation with "No Affiliation" as title. I hope this is acceptable. P.S. I also fixed the DOI warning while at it. |
Thanks! Our preferred notation for that is "Independent researcher", but otherwise all good. |
@editorialbot generate pdf |
Five most similar historical JOSS papers: infotheory: A C++/Python package for multivariate information theoretic analysis hIPPYlib: An Extensible Software Framework for Large-Scale Inverse Problems FNFT: A Software Library for Computing Nonlinear Fourier Transforms fgivenx: A Python package for functional posterior plotting GPJax: A Gaussian Process Framework in JAX |
I think the following JOSS reviewers might be suitable for this submission
|
I hate to bug you, but is there a rough ETA when this submission might be considered for review? |
@Edenhofer — Thanks for checking in. Unfortunately there are quite a few submissions in the queue before this one (there was a big burst of submissions a month ago) and all the editors in this track are working at capacity. I expect it will still be a couple more weeks. Thanks for your patience! |
@dfm I've been following the paper for a while and it's interesting for me to dive deeper and review it. 👍🏻 |
@Abinashbunty — Thanks for volunteering! Once an editor is assigned, they will follow up. |
@editorialbot assign me as editor Hi all — I'm now available to edit this submission. Thanks for your patience! I'll work on recruiting reviewers now, and once we have two, the main review will get started in a new thread. |
Assigned! @dfm is now the editor |
@editorialbot add @Abinashbunty as reviewer @Abinashbunty — if your offer to review still stands, I've added you as a reviewer. If you don't have the capacity anymore, I'm happy to remove you. Either way, let me know and many thanks!! |
@Abinashbunty added to the reviewers list! |
👋 @williamjameshandley, @thomaspinder, @apizzuto — Would any of you be available and willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@dfm I'm still available for the review. So it's fine. 👍🏻 I'll get started with the review already but will post my feedback in the new issue once that is initiated. 😄 |
I am also happy to review this submission! |
@editorialbot add @apizzuto as reviewer Thanks @apizzuto!! I'll get the main review started in a new thread, and I'll have a lot more information for everyone over there. Thanks all! |
@apizzuto added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #6593. |
Submitting author: @Edenhofer (Gordian Edenhofer)
Repository: https://github.com/nifty-ppl/nifty
Branch with paper.md (empty if default branch): paper
Version: v8.5
Editor: @dfm
Reviewers: @Abinashbunty, @apizzuto
Managing EiC: Dan Foreman-Mackey
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @Edenhofer. Currently, there isn't a JOSS editor assigned to your paper.
@Edenhofer if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: