Closed editorialbot closed 1 year ago
@dhhagan - @nicoleyghu has now fixed the minor typos, and I think this is ready to go. Let us know once its official!
@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 remove @professoralkmin as reviewer
@professoralkmin removed from the reviewers list!
@ajmedford this looks great. Can you do the following?
@mshuaibii @zulissi - can one of you take care of this? It seems that Nicole does not have the necessary permissions.
I changed @nicoleyghu to maintainer on the repo; let me know if that's not sufficient!
@dhhagan - We have released and tagged the version and archived it. The release is here: https://github.com/ulissigroup/amptorch/releases/tag/v0.2.0-alpha, and the archived version is here: https://zenodo.org/record/8103323.
Let us know if you need anything else to get this finalized!
Hi @ajmedford - sorry for the delay! Can you update the title in Zenodo to match the paper title? Also, are you planning to update the release version to no longer indicate a pre-release? If so, now would be a good time to do that so that the paper and release in GitHub/zenodo all align?
@dhhagan Sure thing -- here is the updated Zenodo: https://zenodo.org/record/8151492
It has a new DOI (10.5281/zenodo.8151492), so maybe best to link to that one. Looking forward to having this out!
@editorialbot set v1.0 as version
Done! version is now v1.0
@editorialbot set https://zenodo.org/record/8151492 as doi
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@editorialbot commands
@editorialbot set https://zenodo.org/record/8151492 as archive
That doesn't look like a valid DOI value
@editorialbot set 10.5281/zenodo.8151492 as archive
Done! archive is now 10.5281/zenodo.8151492
@editorialbot generate pdf
:warning: An error happened when generating the pdf.
@editorialbot generate pdf
Looks like there is an issue with one of the services used to build the pdf. Will try again and try again later today if needed.
: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.1021/acs.jpclett.2c02100 is OK
- 10.1088/2632-2153/ACA7B1 is OK
- 10.1016/j.cpc.2016.05.010 is OK
- 10.48550/arxiv.1908.08381 is OK
- 10.1088/2632-2153/ac8fe0 is OK
- 10.1021/acs.jpcc.0c04225 is OK
- 10.1002/qua.24890 is OK
- 10.1088/1361-648X/AA680E is OK
- 10.1021/acscatal.0c04525 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:warning: Error preparing paper acceptance.
@dhhagan - not sure what's causing this error. Let us know if any action is needed from our side.
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1021/acs.jpclett.2c02100 is OK
- 10.1088/2632-2153/ACA7B1 is OK
- 10.1016/j.cpc.2016.05.010 is OK
- 10.48550/arxiv.1908.08381 is OK
- 10.1088/2632-2153/ac8fe0 is OK
- 10.1021/acs.jpcc.0c04225 is OK
- 10.1002/qua.24890 is OK
- 10.1088/1361-648X/AA680E is OK
- 10.1021/acscatal.0c04525 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/dsais-eics, this paper is ready to be accepted and published.
Check final proof :point_right::page_facing_up: Download article
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/4428, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Looks good to me!
Everything looks to be in good shape here. I'm proceeding with final acceptance.
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
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:
``` cff-version: "1.2.0" authors: - family-names: Shuaibi given-names: Muhammed - family-names: Hu given-names: Yuge orcid: "https://orcid.org/0000-0003-3648-7749" - family-names: Lei given-names: Xiangyun - family-names: Comer given-names: Benjamin M. - family-names: Adams given-names: Matt - family-names: Paras given-names: Jacob - family-names: Chen given-names: Rui Qi - family-names: Musa given-names: Eric - family-names: Musielewicz given-names: Joseph - family-names: Peterson given-names: Andrew A. orcid: "https://orcid.org/0000-0003-2855-9482" - family-names: Medford given-names: Andrew J. orcid: "https://orcid.org/0000-0001-8311-9581" - family-names: Ulissi given-names: Zachary orcid: "https://orcid.org/0000-0002-9401-4918" contact: - family-names: Ulissi given-names: Zachary orcid: "https://orcid.org/0000-0002-9401-4918" doi: 10.5281/zenodo.8151492 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Shuaibi given-names: Muhammed - family-names: Hu given-names: Yuge orcid: "https://orcid.org/0000-0003-3648-7749" - family-names: Lei given-names: Xiangyun - family-names: Comer given-names: Benjamin M. - family-names: Adams given-names: Matt - family-names: Paras given-names: Jacob - family-names: Chen given-names: Rui Qi - family-names: Musa given-names: Eric - family-names: Musielewicz given-names: Joseph - family-names: Peterson given-names: Andrew A. orcid: "https://orcid.org/0000-0003-2855-9482" - family-names: Medford given-names: Andrew J. orcid: "https://orcid.org/0000-0001-8311-9581" - family-names: Ulissi given-names: Zachary orcid: "https://orcid.org/0000-0002-9401-4918" date-published: 2023-07-26 doi: 10.21105/joss.05035 issn: 2475-9066 issue: 87 journal: Journal of Open Source Software publisher: name: Open Journals start: 5035 title: "AmpTorch: A Python package for scalable fingerprint-based neural network training on multi-element systems with integrated uncertainty quantification" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05035" volume: 8 title: "AmpTorch: A Python package for scalable fingerprint-based neural network training on multi-element systems with integrated uncertainty quantification" ```
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...
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
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.05035/status.svg)](https://doi.org/10.21105/joss.05035)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05035">
<img src="https://joss.theoj.org/papers/10.21105/joss.05035/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05035/status.svg
:target: https://doi.org/10.21105/joss.05035
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:
Submitting author: !--author-handle-->@ajmedford<!--end-author-handle-- (Andrew Medford) Repository: https://github.com/ulissigroup/amptorch Branch with paper.md (empty if default branch): master Version: v1.0 Editor: !--editor-->@dhhagan<!--end-editor-- Reviewers: @ml-evs, @ianfhunter Archive: 10.5281/zenodo.8151492
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
@ml-evs & @professoralkmin, 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 @dhhagan 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 @ml-evs
📝 Checklist for @ianfhunter