[REVIEW]: TorchGAN: A Flexible Framework for GAN Training and Evaluation

[whedon]

Submitting author: @avik-pal (Avik Pal)
Repository: https://github.com/torchgan/torchgan/
Version: v0.0.4
Editor: @arfon
Reviewers: @NMontanaBrown, @terrytangyuan
Archive: 10.5281/zenodo.5575758

⚠️ 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 badge code:

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

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

@Paul92, @urbanophile, @NMontanaBrown, 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 @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 ✨

Review checklist for @NMontanaBrown

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

• I confirm that I read and will adhere to the JOSS 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 (@avik-pal) 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: Do the authors clearly state 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]

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @Paul92, @urbanophile 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:

2. You may also like to change your default settings for this watching repositories in your GitHub profile here: https://github.com/settings/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]

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

Can't find any papers to compile :-(

[avik-pal]

@whedon generate pdf from branch ap/joss_paper

[whedon]

Attempting PDF compilation from custom branch ap/joss_paper. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[kthyng]

Hello! I am the rotating associate editor in chief and am checking in on stale reviews. Will reviewers @Paul92, @urbanophile have a chance to start on/continue your reviews sometime soon? It's been over a month since the review started. Thanks!

[urbanophile]

Hi apologies, yes. I will continue on the review.

[avik-pal]

bump.

[terrytangyuan]

@Paul92 and @urbanophile, did you get a chance to review this yet?

[arfon]

👋 @Paul92 and @urbanophile - could you please update us on the status of your reviews?

[arfon]

I've just emailed both @Paul92 and @urbanophile to see if they are able to return to this review sometime soon. I'm sorry this is taking so long @avik-pal.

[arfon]

@avik-pal - I'm afraid I think we need to find some new reviewers here 😞 . Could you take a look a this list of potential reviewers and identify a few people who would be good candidates to review this submission?

[arfon]

@whedon assign me as editor

[arfon]

@vs74 @NMontanaBrown - would you be 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/reviewer_guidelines.html

The submission we'd be asking you to review is TorchGAN: A Flexible Framework for GAN Training and Evaluation

[NMontanaBrown]

Hi @arfon, I should be able to, if this is still in need of a reviewer.

[arfon]

Hi @arfon, I should be able to, if this is still in need of a reviewer.

Yes please! I'll go ahead and set you up on the review now.

[whedon]

OK, @terrytangyuan is now a reviewer

[terrytangyuan]

Review checklist for @terrytangyuan

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

• I confirm that I read and will adhere to the JOSS 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 (@avik-pal) 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: Do the authors clearly state 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?

[terrytangyuan]

@avik-pal Just some small feedback. Not a blocker but nice to have.

1. There might be some papers that you cited in arXiv but have been published to somewhere more formally. Could you check and update them accordingly?
2. The paper has been here for a year and some things might have been changed, such as the feature tables for existing frameworks. Could you update those wherever necessary? If the API of TorchGAN has changed, please update as well.

[arfon]

@avik-pal – how are you getting on with the reviewer feedback here?

[avik-pal]

@whedon generate pdf from branch ap/joss_paper

[whedon]

Attempting PDF compilation from custom branch ap/joss_paper. Reticulating splines etc...

[whedon]

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

[arfon]

@avik-pal – have you made changes to your submission based on the reviewer feedback?

[avik-pal]

Yes the latest pdf has the updated references

[arfon]

@avik-pal – At this point 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:

• The title of the archive is the same as the JOSS paper title
• That the authors of the archive are the same as the JOSS paper authors

I can then move forward with accepting the submission.

[avik-pal]

@arfon I have uploaded the archive to Zenodo: https://doi.org/10.5281/zenodo.5575758

[arfon]

@whedon set 10.5281/zenodo.5575758 as archive

[whedon]

OK. 10.5281/zenodo.5575758 is the archive.

[arfon]

@whedon recommend-accept from branch ap/joss_paper

[whedon]

Attempting dry run of processing paper acceptance...

[whedon]

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

Check final proof 👉 openjournals/joss-papers#2690

If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#2690, then you can now move forward with accepting the submission by compiling again with the flag deposit=true e.g.

@whedon accept deposit=true from branch ap/joss_paper 

[whedon]

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

OK DOIs

- 10.1109/cvpr.2016.90 is OK
- 10.1109/cvpr.2017.243 is OK
- 10.1109/iccv.2017.304 is OK
- 10.1109/iccv.2017.244 is OK
- 10.1109/cvpr.2017.19 is OK
- 10.1109/cvpr.2018.00916 is OK

MISSING DOIs

- 10.1109/cvpr.2018.00165 may be a valid DOI for title: MoCoGAN: Decomposing Motion and Content for Video Generation

INVALID DOIs

- None

[arfon]

@whedon accept deposit=true from branch ap/joss_paper

[whedon]

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

[whedon]

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

[whedon]

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

Here's what you must now do:

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

Any issues? Notify your editorial technical team...

[arfon]

@NMontanaBrown, @terrytangyuan – 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 ✨

@avik-pal – your paper is now accepted and published in JOSS ⚡🚀💥

[whedon]

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

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

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

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:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://joss.theoj.org/reviewer-signup.html
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss