Closed editorialbot closed 7 months ago
Done! archive is now 10.5281/zenodo.10641293
@editorialbot set v1.0.0 as version
Done! version is now v1.0.0
@AndresRTejedor the title and author list on the archive must match exactly that of the paper. Currently, neither do. Please can you update the Zenodo repo accordingly? (ie, title will be "Mold: a LAMMPS package to compute interfacial free energies and nucleation rates" and the author list will match that in the JOSS paper).
Your reference lists are not formatted correctly. Where there are multiple references, use square brackets separated by semi-colons e.g. [@anderson2020hoomd; @lammps_2022]
In your paper I suggest re-phrasing for clarity:
In the particular case of liquid-to-solid transitions, obtaining this quantity is not straightforward neither experimentally nor computationally.
--> In the particular case of liquid-to-solid transitions, it is not straightforward to obtain this quantity through experiment or computation.
Here, we present a computational package integrated in the Molecular Dynamics open-source software LAMMPS (Large-Scale Atomic/Molecular Massively Parallel Simulator)(Thompson et al., 2022), which enables the direct calculation of the interfacial free energy between arbitrarily complex crystal structures and liquids/solutions at coexistence conditions through the Mold Integration method (J. Espinosa et al., 2014).
--> Here, we present the computational package Mold, which is integrated in the Molecular Dynamics open-source software LAMMPS (Large-Scale Atomic/Molecular Massively Parallel Simulator)(Thompson et al., 2022). Mold enables direct calculation of the interfacial free energy between arbitrarily complex crystal structures and liquids/solutions at coexistence conditions through the Mold Integration method (J. Espinosa et al., 2014).
implemented to be included in the MD package LAMMPS.
--> implemented to work alongside the MD package LAMMPS.
Adjustments to paper
Your reference lists are not formatted correctly. Where there are multiple references, use square brackets separated by semi-colons e.g.
[@anderson2020hoomd; @lammps_2022]
In your paper I suggest re-phrasing for clarity:
In the particular case of liquid-to-solid transitions, obtaining this quantity is not straightforward neither experimentally nor computationally.
-->In the particular case of liquid-to-solid transitions, it is not straightforward to obtain this quantity through experiment or computation.
Here, we present a computational package integrated in the Molecular Dynamics open-source software LAMMPS (Large-Scale Atomic/Molecular Massively Parallel Simulator)(Thompson et al., 2022), which enables the direct calculation of the interfacial free energy between arbitrarily complex crystal structures and liquids/solutions at coexistence conditions through the Mold Integration method (J. Espinosa et al., 2014).
-->Here, we present the computational package Mold, which is integrated in the Molecular Dynamics open-source software LAMMPS (Large-Scale Atomic/Molecular Massively Parallel Simulator)(Thompson et al., 2022). Mold enables direct calculation of the interfacial free energy between arbitrarily complex crystal structures and liquids/solutions at coexistence conditions through the Mold Integration method (J. Espinosa et al., 2014).
implemented to be included in the MD package LAMMPS.
-->implemented to work alongside the MD package LAMMPS.
Dear @lucydot
Thank you for all your suggestions. We have included your re-phrasing, and also we have corrected the format of the references.
Please let me know if you need any further information.
list on the archive must match exactly that of the paper. C
Dear @lucydot
I have updated the repo to match the title and authors in the JOSS paper.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1063/1.4896621 is OK
- 10.1063/5.0139699 is OK
- 10.1039/C4CP03948C is OK
- 10.1063/1.5018303 is OK
- 10.1039/C1CP22167A is OK
- 10.1016/j.bpj.2023.03.006 is OK
- 10.1063/1.1747248 is OK
- 10.1038/s41598-021-94309-y is OK
- 10.1039/C6FD00141F is OK
- 10.1016/j.softx.2015.06.001 is OK
- 10.1063/1.3578182 is OK
- 10.1016/j.cossms.2011.07.003 is OK
- 10.1063/1.3153843 is OK
- 10.1080/00268978300100971 is OK
- 10.1039/D1CP01784E is OK
- 10.1103/PhysRevLett.130.118001 is OK
- 10.1063/1.4921185 is OK
- 10.1021/acs.jpcc.5b11221 is OK
- 10.1021/ie50510a027 is OK
- 10.1016/j.actamat.2008.10.020 is OK
- 10.1016/j.jcis.2022.05.029 is OK
- 10.1063/5.0101383 is OK
- 10.1063/1.5098551 is OK
- 10.1073/pnas.1917569117 is OK
- 10.1016/j.bpj.2021.01.031 is OK
- 10.3390/biom11020278 is OK
- 10.1063/5.0101529 is OK
- 10.1063/1.1563248 is OK
- 10.1016/j.cpc.2021.108171 is OK
- 10.1063/1.445633 is OK
- 10.1063/5.0028219 is OK
MISSING DOIs
- None
INVALID DOIs
- https://doi.org/10.1063/5.0101746 is INVALID because of 'https://doi.org/' prefix
The paper's PDF and metadata files generation produced some warnings that could prevent the final paper from being published. Please fix them before the end of the review process.
\AA
^
unexpected control sequence \AA
expecting "%", "\\label", "\\tag", "\\nonumber" or whitespace
\AA
^
unexpected control sequence \AA
expecting "%", "\\label", "\\tag", "\\nonumber" or whitespace
:warning: Error preparing paper acceptance. The generated XML metadata file is invalid.
Element doi: [facet 'pattern'] The value 'https://doi.org/10.1063/5.0101746' is not accepted by the pattern '10\.[0-9]{4,9}/.{1,200}'.
@editorialbot commands
Hello @AndresRTejedor, here are the things you can ask me to do:
# List all available commands
@editorialbot commands
# Get a list of all editors's GitHub handles
@editorialbot list editors
# Check the references of the paper for missing DOIs
@editorialbot check references
# Perform checks on the repository
@editorialbot check repository
# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist
# Set a value for branch
@editorialbot set joss-paper as branch
# Generates the pdf paper
@editorialbot generate pdf
# Generates a LaTeX preprint file
@editorialbot generate preprint
# Get a link to the complete list of reviewers
@editorialbot list reviewers
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1063/1.4896621 is OK
- 10.1063/5.0139699 is OK
- 10.1039/C4CP03948C is OK
- 10.1063/1.5018303 is OK
- 10.1039/C1CP22167A is OK
- 10.1016/j.bpj.2023.03.006 is OK
- 10.1063/1.1747248 is OK
- 10.1038/s41598-021-94309-y is OK
- 10.1039/C6FD00141F is OK
- 10.1016/j.softx.2015.06.001 is OK
- 10.1063/1.3578182 is OK
- 10.1016/j.cossms.2011.07.003 is OK
- 10.1063/1.3153843 is OK
- 10.1080/00268978300100971 is OK
- 10.1039/D1CP01784E is OK
- 10.1103/PhysRevLett.130.118001 is OK
- 10.1063/1.4921185 is OK
- 10.1021/acs.jpcc.5b11221 is OK
- 10.1021/ie50510a027 is OK
- 10.1016/j.actamat.2008.10.020 is OK
- 10.1063/5.0101746 is OK
- 10.1016/j.jcis.2022.05.029 is OK
- 10.1063/5.0101383 is OK
- 10.1063/1.5098551 is OK
- 10.1073/pnas.1917569117 is OK
- 10.1016/j.bpj.2021.01.031 is OK
- 10.3390/biom11020278 is OK
- 10.1063/5.0101529 is OK
- 10.1063/1.1563248 is OK
- 10.1016/j.cpc.2021.108171 is OK
- 10.1063/1.445633 is OK
- 10.1063/5.0028219 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Dear @lucydot
I have corrected the DOI that was invalid before.
Many thanks
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@AndresRTejedor there also seems to be an issue with \AA
; it might be as it is used in mathmode. Could you try inserting directly into the markdown (you can copy and paste I have done here: Å) - and see if that works?
@lucydot I have included Å directly into the markdown and it seems it worked. Thank you for noticing that.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @AndresRTejedor - there are double brackets ((
and ))
in the paper.md (occuring where there are lists of references). Please can you correct this?
@lucydot thank you for noticing it. I have already corrected it.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
It's also best to avoid the consecutive brackets on line 20/21 and the nested brackets on line 118/119. I suggest removing the brackets around the references by using square brackets around the sentence (see: https://stackoverflow.com/questions/64209134/r-markdown-suppress-parentheses-in-specific-citations), or re-phrasing.
I have changed those lines by using brackets instead for the clarification. Please let me know if that works.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@AndresRTejedor - hmm, not what I was expecting. I've tried fixing another way (removing square brackets from reference) and issued a PR. Could you merge and then we can check if that looks correct?
@lucydot I have already merged your patch. Please let me know if it works now.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @AndresRTejedor - it hasn't.
I'll message the other editors to see how to include citations without the brackets. There is also the option of re-phrasing to avoid the citation within a bracket. We are very close to being finished!
FYI I'm going on leave for one week starting tomorrow, will check back here on the 18th. Please also note that if you make changes and want to verify correct, you can also check yourself using the @editorialbot generate pdf
command.
Best,
Lucy
Hi @lucydot , thanks for your help! I hope it can be solved soon for publication!
Can I re-phrase those lines and finish it today?
Many thanks
Hi @AndresRTejedor - yes, go ahead and re-phrase then we can finish.
Hi @lucydot , I re-phrased the corresponding parts. Please let me know if it works now!
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@AndresRTejedor - I have just spotted that the software version on the Zenodo archive (Lammps
) does not match that which is set here (v1.0.0
). To ensure consistency, you need to update the version number on Zenodo. To do this I think you can create a v1.0.0 release on Github and then Zenodo should issue a new doi.
@lucydot I have created a new release with the correct tag. Here is the doi: 10.5281/zenodo.10843863
@editorialbot set 10.5281/zenodo.10843863 as archive
Done! archive is now 10.5281/zenodo.10843863
@AndresRTejedor you need to make the archive title and author list match exactly that of the JOSS submission. Please update. I'll re-paste the author to-do list from earlier message below so you can confirm all tasks complete:
Submitting author: !--author-handle-->@AndresRTejedor<!--end-author-handle-- (Andrés R. Tejedor) Repository: https://github.com/AndresRTejedor/Mold Branch with paper.md (empty if default branch): joss Version: v1.0.0 Editor: !--editor-->@lucydot<!--end-editor-- Reviewers: @mattwthompson, @marjanalbooyeh Archive: 10.5281/zenodo.10843863
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
@mattwthompson & @marjanAlbouye, 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 @lucydot 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 @marjanAlbouye
📝 Checklist for @mattwthompson