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]: Surjectors: surjective normalizing flows for density estimation #6188
Comments
Hello humans, 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 |
|
@sandeshkatakam, @animikhaich – This is the review thread for the paper. All of our communications will happen here from now on. Please read the "Reviewer instructions & questions" in the first comment above. Please create your checklist typing:
As you go over the submission, please check any items that you feel have been satisfied. There are also links to the JOSS reviewer guidelines. The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention We aim for the review process to be completed within about 4-6 weeks but please make a start well ahead of this as JOSS reviews are by their nature iterative and any early feedback you may be able to provide to the author will be very helpful in meeting this schedule. |
Review checklist for @sandeshkatakamConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Review checklist for @animikhaichConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
@arfon I will be traveling for the next few days. I'll the review post January 25th. |
👋 @sandeshkatakam, @animikhaich – just checking in here to see how you're getting along with your reviews? |
@arfon - Literature/Documentation review is completed, currently running functionality checks by installing the package and testing it out. The checklist has been updated accordingly. |
Hi @arfon, Barring a very minor pending fix in the documentation, the review is completed from my end. Once the author has made the fix, I'll update you here. Meanwhile, please let me know if anything else is needed. Thanks! |
Hi @arfon, The Review is completed from my end. We are good to go! Please let me know if anything else is needed. Please refer to the author's comments for the aforementioned documentation fix: dirmeier/surjectors#26 (comment) |
Thanks for the update @animikhaich! |
Hey, Sorry for the delay |
@sandeshkatakam and @animikhaich , thank you both very much for reviewing! |
@dirmeier – looks like we're very close to being done here. I will circle back here next week, but in the meantime, please give your own paper a final read to check for any potential typos etc. After that, could you make a new release of this software that includes the changes that have resulted from this review. Then, please make an archive of the software in Zenodo/figshare/other service and update this thread with the DOI of the archive? For the Zenodo/figshare archive, please make sure that:
|
@editorialbot commands |
Hello @dirmeier, here are the things you can ask me to do:
|
1 similar comment
@editorialbot generate pdf |
Dear @arfon , thank you very much! Here are the link to Zenodo and DOI:
Best, |
@editorialbot set 10.5281/zenodo.10679869 as archive |
Done! archive is now 10.5281/zenodo.10679869 |
@dirmeier – could you update the license of the Zenodo record to be the same as the software please? |
@editorialbot recommend-accept |
|
👋 @openjournals/dsais-eics, this paper is ready to be accepted and published. Check final proof 👉📄 Download article If the paper PDF and the deposit XML files look good in openjournals/joss-papers#5037, then you can now move forward with accepting the submission by compiling again with the command |
|
@editorialbot recommend-accept |
|
👋 @openjournals/dsais-eics, this paper is ready to be accepted and published. Check final proof 👉📄 Download article If the paper PDF and the deposit XML files look good in openjournals/joss-papers#5067, then you can now move forward with accepting the submission by compiling again with the command |
|
@editorialbot accept |
|
Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository. If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file. You can copy the contents for your CITATION.cff file here: CITATION.cff
If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation. |
🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘 |
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨 Here's what you must now do:
Any issues? Notify your editorial technical team... |
@sandeshkatakam, @animikhaich – many thanks for your reviews here! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨ @dirmeier – your paper is now accepted and published in JOSS ⚡🚀💥 |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
This is how it will look in your documentation: 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:
|
Hi @arfon , that's great! Thank you very much! @sandeshkatakam and @animikhaich, thanks again for reviewing :) |
Submitting author: @dirmeier (Simon Dirmeier)
Repository: https://github.com/dirmeier/surjectors
Branch with paper.md (empty if default branch): joss
Version: v0.0.3
Editor: @arfon
Reviewers: @sandeshkatakam, @animikhaich
Archive: 10.5281/zenodo.10679869
Status
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) 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
@sandeshkatakam & @animikhaich, 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:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @arfon 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 @sandeshkatakam
📝 Checklist for @animikhaich
The text was updated successfully, but these errors were encountered: