Closed editorialbot closed 2 years ago
@nicoguaro you have some boxes unticked, can you have a look if there are any updates, or provide points that still need to be addressed?
All of them have been addressed except for the "state of the field". @JulianKarlBauer mentioned something before about it, but I don't see anything about it in the compiled version of the paper.
Sorry, I had not yet merged pull request mentioned above. After having merged it, are your concerns addressed @nicoguaro ?
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
point_rightpage_facing_up Download article proof page_facing_up View article proof on GitHub page_facing_up point_left
Branch "master" had not been merged to branch "paper" from which editorialbot is compiling...
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Sorry, I had not yet merged pull request mentioned above. After having merged it, are your concerns addressed @nicoguaro ?
Yes.
@Kevin-Mattheus-Moerman, I have marked all the boxes now and recommend the publication.
@likask can you check the response to your comments? :point_up: https://github.com/openjournals/joss-reviews/issues/4389#issuecomment-1212835958
@JulianKarlBauer @Kevin-Mattheus-Moerman
Hi, I am happy from your modifications. Green light from me.
Yes, some time ago I was working on second-order continuum description, dealing with third order tensors was painful in vector notation.
Great @likask can you check those last boxes? :point_right: https://github.com/openjournals/joss-reviews/issues/4389#issuecomment-1173047773
@Kevin-Mattheus-Moerman It seems that all boxes are ticked now :)
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1177/10812865211057602 is OK
- 10.1016/0020-7225(84)90090-9 is OK
- 10.1007/978-3-319-19566-7 is OK
- 10.1007/978-1-4757-1275-9 is OK
- 10.1093/qjmam/43.1.15 is OK
- 10.1016/0022-5096(92)90029-2 is OK
- 10.1088/978-0-7503-1454-1 is OK
- 10.1016/0020-7225(70)90024-8 is OK
- 10.1122/1.549945 is OK
- 10.5281/zenodo.4679756 is OK
- 10.5281/zenodo.1173115 is OK
- 10.5281/zenodo.5938012 is OK
- 10.5281/zenodo.5564818 is OK
MISSING DOIs
- 10.21468/scipostphyslectnotes.5 may be a valid DOI for title: Efficient numerical simulations with tensor networks: Tensor Network Python (TeNPy)
INVALID DOIs
- None
@JulianKarlBauer can you check that potentially missing DOI? :point_up:
@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 check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1177/10812865211057602 is OK
- 10.1016/0020-7225(84)90090-9 is OK
- 10.1007/978-3-319-19566-7 is OK
- 10.1007/978-1-4757-1275-9 is OK
- 10.1093/qjmam/43.1.15 is OK
- 10.1016/0022-5096(92)90029-2 is OK
- 10.1088/978-0-7503-1454-1 is OK
- 10.1016/0020-7225(70)90024-8 is OK
- 10.1122/1.549945 is OK
- 10.5281/zenodo.4679756 is OK
- 10.5281/zenodo.1173115 is OK
- 10.5281/zenodo.5938012 is OK
- 10.5281/zenodo.5564818 is OK
- 10.21468/SciPostPhysLectNotes.5 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@JulianKarlBauer can you check that potentially missing DOI? point_up
@Kevin-Mattheus-Moerman Thank you! Sorry I could have checked the references on my own... Repeated the checks and build.
@JulianKarlBauer I read your paper and have two remaining very minor points:
several ... , exist but mainly...
it looks like the comma should go after exist
(but feel free to disagree)several ... , exist but mainly...
it looks like the comma should go after exist
(but feel free to disagree)@Kevin-Mattheus-Moerman Thank you! Fixed both.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@JulianKarlBauer Great, looks like we are good to proceed. At this point can you please:
Thanks.
@Kevin-Mattheus-Moerman Perfect, thank you for the detailed instructions. I created release v0.4.0 with DOI https://zenodo.org/record/7185691 and manually edited the title, author, license and added a funding note.
@editorialbot set v0.4.0 as version
Done! version is now v0.4.0
@editorialbot set 10.5281/zenodo.7185691 as archive
Done! Archive is now 10.5281/zenodo.7185691
@JulianKarlBauer Looks like we are all set. :rocket:
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1177/10812865211057602 is OK
- 10.1016/0020-7225(84)90090-9 is OK
- 10.1007/978-3-319-19566-7 is OK
- 10.1007/978-1-4757-1275-9 is OK
- 10.1093/qjmam/43.1.15 is OK
- 10.1016/0022-5096(92)90029-2 is OK
- 10.1088/978-0-7503-1454-1 is OK
- 10.1016/0020-7225(70)90024-8 is OK
- 10.1122/1.549945 is OK
- 10.5281/zenodo.4679756 is OK
- 10.5281/zenodo.1173115 is OK
- 10.5281/zenodo.5938012 is OK
- 10.5281/zenodo.5564818 is OK
- 10.21468/SciPostPhysLectNotes.5 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/joss-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/3607, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@editorialbot accept
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:
Any issues? Notify your editorial technical team...
Congratulations on your new publication to @JulianKarlBauer! Many thanks to editor @Kevin-Mattheus-Moerman and reviewers @nicoguaro, @likask, and @lizarett for your time, hard work, and expertise!!
: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.04389/status.svg)](https://doi.org/10.21105/joss.04389)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04389">
<img src="https://joss.theoj.org/papers/10.21105/joss.04389/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04389/status.svg
:target: https://doi.org/10.21105/joss.04389
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:
(: thanks for the great experience of publishing in JOSS. Thank you @Kevin-Mattheus-Moerman for your efforts in moderation! Thanks to the reviewers @nicoguaro @likask @lizarett for your valuable suggestions and dedication and thank you @kthyng for finalizing the process.
Submitting author: !--author-handle-->@JulianKarlBauer<!--end-author-handle-- (Julian Karl Bauer) Repository: https://github.com/JulianKarlBauer/mechkit Branch with paper.md (empty if default branch): paper Version: v0.4.0 Editor: !--editor-->@Kevin-Mattheus-Moerman<!--end-editor-- Reviewers: @nicoguaro, @likask, @lizarett Archive: 10.5281/zenodo.7185691
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
@nicoguaro & @likask & @lizarett, 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 @Kevin-Mattheus-Moerman 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 @nicoguaro
📝 Checklist for @likask
📝 Checklist for @lizarett