Closed whedon closed 4 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @EduPH, @mzszym, @corybrunson it looks like you're currently assigned to review this paper :tada:.
:star: Important :star:
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:
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
Attempting to check references...
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1944 with the following error:
Can't find any papers to compile :-(
@whedon generate pdf from branch joss-pape
Attempting PDF compilation from custom branch joss-pape. Reticulating splines etc...
PDF failed to compile for issue #1944 with the following error:
error: pathspec 'joss-pape' did not match any file(s) known to git. Can't find any papers to compile :-(
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
OK DOIs
- 10.1524/zkri.1901.34.1.449 is OK
- 10.1016/0022-0248(83)90184-7 is OK
- https://doi.org/10.1016/0001-6160(67)90206-4 is OK
- https://doi.org/10.1016/j.commatsci.2012.10.028 is OK
- 10.1007/s10853-012-6739-x is OK
- 10.1016/S0927-0256(97)00167-5 is OK
- 10.1145/235815.235821 is OK
- 10.1109/MCSE.2007.55 is OK
- 10.1088/1361-648X/aa680e is OK
MISSING DOIs
- None
INVALID DOIs
- None
I believe that I am done with the review. I think it is a very good small module with a well defined function and a rather complete description. It is well implemented and I found no important issues. I could run the examples without problems. Constructed nanoparticles seem to be according to my expectations. The only thing I missed was the description how "this software compares to other commonly-used packages?", which I understand as a comparison with other packages offering the same or similar functionality.
Edit: I found the sentence about it. It seems to have a missing citation: I would appreciate slightly more information, but I think, a very basic comparison is provided.
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
Thank you, @mzszym! The comparison to other packages was indeed very short. It is updated (and the missing reference has been fixed) in the latest version of the paper, like so:
The regular Wulff construction has been implemented in several software packages, including a submodule of the Python package pymatgen (Ong et al., 2013), a no longer maintained C++ package (Roosen, McCormack, & Carter, 1998), and a Wolfram Mathematica implementation with a graphical user interace (Zucker, Chatain, Dahmen, Hagรจge, & Carter, 2012). While the latter code has support for Winterbottom constructions, we have found no publicly available software that implements the icosahedral and decahedral Wulff construction. The aforementioned codes also seem to lack the ability to transform the created shapes into an atomistic representation, a feature of critical importance if the Wulff construction is to be used for atomistic simulations.
@magnusrahm Well done. I am confident that the package fulfills all requirements.
I will be checking GitHub in a limited capacity over the next couple of weeks.
@drvinceknight and @magnusrahm thank you for your patience. I'm beginning my review now.
@magnusrahm thank you for the elegant software and thorough documentation behind this submission. In most respects i think it quite meets the needs of JOSS, and the few issues i've raised should be quick to resolve. I had no problems along the way other than those raised in the issues. The concepts are quite new to me, but i hope that i've grasped them well enough to give useful feedback. I'll be quick to respond to any questions about it, and i'll check off the remaining items as the issues are addressed.
I agree with the other two reviewers. The package fulfils all the requirements.
(Me closing the issue was a miss click)
Thank you very much for your work reviewing @EduPH, @mzszym, @corybrunson!
I'll be looking through this later today with any final minor editorial requests :+1:
@whedon generate pdf
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1944 with the following error:
Can't find any papers to compile :-(
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
@whedon check references from branch joss-paper
Attempting to check references... from custom branch joss-paper
OK DOIs
- 10.1524/zkri.1901.34.1.449 is OK
- 10.1016/0022-0248(83)90184-7 is OK
- 10.1016/0001-6160(67)90206-4 is OK
- 10.1016/j.commatsci.2012.10.028 is OK
- 10.1007/s10853-012-6739-x is OK
- 10.1016/S0927-0256(97)00167-5 is OK
- 10.1145/235815.235821 is OK
- 10.1109/MCSE.2007.55 is OK
- 10.1088/1361-648X/aa680e is OK
MISSING DOIs
- None
INVALID DOIs
- None
@magnusrahm everything looks good to me, would you be able to make a Zenodo archive, and report the DOI in the review thread (here).
Could you make sure the Zenodo deposit has the correct metadata (title and author list should match the paper).
@drvinceknight I have uploaded a Zenodo archive (10.5281/zenodo.3600252, https://doi.org/10.5281/zenodo.3600252). I have also merged the joss-paper branch into the master branch and deleted the former. Some very minor additions were made to the paper (https://gitlab.com/materials-modeling/wulffpack/commit/82b4e1771798733a6022ff292982bc17ea7b6310).
@whedon generate pdf
@whedon set 10.5281/zenodo.3600252 as archive
OK. 10.5281/zenodo.3600252 is the archive.
@openjournals/joss-eics this paper is ready to be accepted :+1:
@magnusrahm - it looks like this is now version 1.1 - correct?
Yes, that's correct.
@whedon set v1.1 as version
OK. v1.1 is the version.
@whedon accept
Attempting dry run of processing paper acceptance...
Reference check summary:
OK DOIs
- 10.1088/0953-8984/28/5/053001 is OK
- 10.1524/zkri.1901.34.1.449 is OK
- 10.1016/0022-0248(83)90184-7 is OK
- 10.1016/0001-6160(67)90206-4 is OK
- 10.1016/j.commatsci.2012.10.028 is OK
- 10.1007/s10853-012-6739-x is OK
- 10.1016/S0927-0256(97)00167-5 is OK
- 10.1145/235815.235821 is OK
- 10.1109/MCSE.2007.55 is OK
- 10.1088/1361-648X/aa680e is OK
MISSING DOIs
- None
INVALID DOIs
- None
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/1205
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/1205, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
@whedon accept deposit=true
Doing it live! Attempting automated processing of paper acceptance...
๐ฆ๐ฆ๐ฆ ๐ Tweet for this paper ๐ ๐ฆ๐ฆ๐ฆ
๐จ๐จ๐จ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! ๐จ๐จ๐จ
Here's what you must now do:
Party like you just published a paper! ๐๐๐ฆ๐๐ป๐ค
Any issues? notify your editorial technical team...
Submitting author: @magnusrahm (Magnus Rahm) Repository: https://gitlab.com/materials-modeling/wulffpack Version: v1.1 Editor: @drvinceknight Reviewer: @EduPH, @mzszym, @corybrunson Archive: 10.5281/zenodo.3600252
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
@EduPH & @mzszym & @corybrunson, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @drvinceknight know.
โจ Please try and complete your review in the next two weeks โจ
Review checklist for @EduPH
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @mzszym
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @corybrunson
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper