Closed editorialbot closed 2 years ago
Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.
For a list of things I can do to help you, just type:
@editorialbot commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@editorialbot generate pdf
Software report:
github.com/AlDanial/cloc v 1.88 T=0.17 s (319.9 files/s, 130240.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
SVG 6 6 6 7477
Python 27 1806 3246 3206
TeX 2 293 0 2623
reStructuredText 15 999 1141 1363
Markdown 2 29 0 124
DOS Batch 1 8 1 26
TOML 1 1 0 17
make 1 4 6 9
-------------------------------------------------------------------------------
SUM: 55 3146 4400 14845
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.energy.2020.118798 is OK
- 10.1016/j.fuel.2020.117049 is OK
- 10.1115/1.4044491 is OK
- 10.1016/j.energy.2021.120692 is OK
- 10.1016/j.egypro.2019.01.549 is OK
- 10.1016/j.apenergy.2019.04.101 is OK
- 10.1016/j.apenergy.2017.03.132 is OK
- 10.3390/app10196653 is OK
- 10.1007/s11831-017-9240-5 is OK
- 10.2514/6.2017-3827 is OK
- 10.3390/en14134027 is OK
- 10.1016/j.jcp.2016.12.015 is OK
- 10.21105/joss.00884 is OK
- 10.21105/joss.00676 is OK
- 10.1061/9780784413609.257 is OK
- 10.1016/j.jocs.2015.08.008 is OK
- 10.21105/joss.00825 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Wordcount for paper.md
is 1043
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@fraukewiese I have started the review, and 9 days ago I filed an issue and a pull request, but I am not getting any response from the author DCoppitters. Can you contact him with a friendly reminder, just to make sure that the review can proceed
@DCoppitters : Have you seen the issue and pull request from @andr1976 regarding the review process?
@fraukewiese : I have seen the issues and pull request. My apologies for not getting back to the reviewers sooner.
@andr1976 Thanks for your review so far! Have your comments been adequately answered/handled?
Yes they have
On Tue, Jun 14, 2022 at 11:36 AM fraukewiese @.***> wrote:
@andr1976 https://github.com/andr1976 Thanks for your review so far! Have your comments been adequately answered/handled?
— Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/4370#issuecomment-1154951307, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6EID44XBJCYPDPVZL7LE3VPBHDNANCNFSM5VBHSNOQ . You are receiving this because you were mentioned.Message ID: @.***>
@andr1976 Thanks for your review, would you recommend this submission for publication?
@ClaraBuettner : Thank you for your review so far. As the checklist is complete: Do you have any comments/suggestions/questions to the author? Would you recommend this submission for publication in its present form or is there anything that should be revised?
@fraukewiese yes indeed
@ClaraBuettner : Thank you for your review so far. As the checklist is complete: Do you have any comments/suggestions/questions to the author? Would you recommend this submission for publication in its present form or is there anything that should be revised?
No, I don't have any other comments or questions. I would recommend this submission for publication in its present form.
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.energy.2020.118798 is OK
- 10.1016/j.fuel.2020.117049 is OK
- 10.1115/1.4044491 is OK
- 10.1016/j.energy.2021.120692 is OK
- 10.1016/j.egypro.2019.01.549 is OK
- 10.1016/j.apenergy.2019.04.101 is OK
- 10.1016/j.apenergy.2017.03.132 is OK
- 10.3390/app10196653 is OK
- 10.1007/s11831-017-9240-5 is OK
- 10.2514/6.2017-3827 is OK
- 10.3390/en14134027 is OK
- 10.1016/j.jcp.2016.12.015 is OK
- 10.21105/joss.00884 is OK
- 10.21105/joss.00676 is OK
- 10.1061/9780784413609.257 is OK
- 10.1016/j.jocs.2015.08.008 is OK
- 10.21105/joss.00825 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:
@andr1976 and @ClaraBuettner: Thank you very much for your review!
@DCoppitters : At this point could you:
I can then move forward with accepting the submission.
@andr1976 and @ClaraBuettner : Thanks a lot for your review, time and efforts!
@fraukewiese : Below the required information:
Thanks a lot for your time and efforts!
@editorialbot set v1.0.0 as version
Done! version is now v1.0.0
@editorialbot set 10.5281/zenodo.6782705 as archive
Done! Archive is now 10.5281/zenodo.6782705
@editorialbot set 10.5281/zenodo.6782705 as archive
Done! Archive is now 10.5281/zenodo.6782705
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.energy.2020.118798 is OK
- 10.1016/j.fuel.2020.117049 is OK
- 10.1115/1.4044491 is OK
- 10.1016/j.energy.2021.120692 is OK
- 10.1016/j.egypro.2019.01.549 is OK
- 10.1016/j.apenergy.2019.04.101 is OK
- 10.1016/j.apenergy.2017.03.132 is OK
- 10.3390/app10196653 is OK
- 10.1007/s11831-017-9240-5 is OK
- 10.2514/6.2017-3827 is OK
- 10.3390/en14134027 is OK
- 10.1016/j.jcp.2016.12.015 is OK
- 10.21105/joss.00884 is OK
- 10.21105/joss.00676 is OK
- 10.1061/9780784413609.257 is OK
- 10.1016/j.jocs.2015.08.008 is OK
- 10.21105/joss.00825 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: https://github.com/openjournals/joss-papers/pull/3327
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/3327, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@DCoppitters - I'm the AEiC this week who will complete processing of this paper. I've suggested some small changes to the paper in https://github.com/rheia-framework/RHEIA/pull/14 - please merge this or let me know what you disagree with, then we can proceed.
@danielskatz : Thank you for improving the paper, I merged the pull request.
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.energy.2020.118798 is OK
- 10.1016/j.fuel.2020.117049 is OK
- 10.1115/1.4044491 is OK
- 10.1016/j.energy.2021.120692 is OK
- 10.1016/j.egypro.2019.01.549 is OK
- 10.1016/j.apenergy.2019.04.101 is OK
- 10.1016/j.apenergy.2017.03.132 is OK
- 10.3390/app10196653 is OK
- 10.1007/s11831-017-9240-5 is OK
- 10.2514/6.2017-3827 is OK
- 10.3390/en14134027 is OK
- 10.1016/j.jcp.2016.12.015 is OK
- 10.21105/joss.00884 is OK
- 10.21105/joss.00676 is OK
- 10.1061/9780784413609.257 is OK
- 10.1016/j.jocs.2015.08.008 is OK
- 10.21105/joss.00825 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/3337, 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 to @DCoppitters (Diederik Coppitters) and co-authors!!
And thanks to @andr1976 and @ClaraBuettner for reviewing and to @fraukewiese for editing! We couldn't do this without you!
: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.04370/status.svg)](https://doi.org/10.21105/joss.04370)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04370">
<img src="https://joss.theoj.org/papers/10.21105/joss.04370/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04370/status.svg
:target: https://doi.org/10.21105/joss.04370
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-->@DCoppitters<!--end-author-handle-- (Diederik Coppitters) Repository: https://github.com/rheia-framework/RHEIA Branch with paper.md (empty if default branch): Version: v1.0.0 Editor: !--editor-->@fraukewiese<!--end-editor-- Reviewers: @andr1976, @ClaraBuettner Archive: 10.5281/zenodo.6782705
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
@andr1976 & @ClaraBuettner, 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 @fraukewiese 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 @andr1976
📝 Checklist for @ClaraBuettner