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=1.32 s (1072.1 files/s, 242003.0 lines/s)
--------------------------------------------------------------------------------
Language files blank comment code
--------------------------------------------------------------------------------
CUDA 502 24816 32955 94842
C/C++ Header 641 15793 43769 62412
C++ 161 4935 3557 19975
Markdown 12 1107 0 3938
CMake 60 711 1208 3478
Python 11 926 1132 2220
make 12 146 141 471
Perl 1 99 41 461
Bourne Again Shell 6 119 151 430
SVG 1 0 1 271
YAML 6 21 20 198
Bourne Shell 6 32 8 130
TeX 1 3 0 25
--------------------------------------------------------------------------------
SUM: 1420 48708 82983 188851
--------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 430
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.15803/ijnc.7.2_208 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
š @robertszafa and @wimvanderbauwhede - Thanks for agreeing to review this submission. This is the review thread for the paper. All of our communications will happen here from now on.
As you can see above, you each should use the command @editorialbot generate my checklist
to create your review checklist. @editorialbot commands need to be the first thing in a new comment.
As you go over the submission, please check any items that you feel have been satisfied. There are also links to the JOSS reviewer guidelines.
The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#4589
so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.
We aim for reviews to be completed within about 2-4 weeks. Please let me know if either of you require some more time. We can also use editorialbot (our bot) to set automatic reminders if you know you'll be away for a known period of time.
Please feel free to ping me (@danielskatz) if you have any questions/concerns.
Hi @yogi-tud, I've added a few issues related to documentation. The rest looks good to me.
Hi @robertszafa
Thanks for the input. I have added the documentation and a readme file providing an example.
Also some information about contributing in a file called CONTRIBUTE.
@editorialbot commands
Hello @wimvanderbauwhede, 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
# Get a link to the complete list of reviewers
@editorialbot list reviewers
@danielskatz All issues are closed, both forms completed @robertszafa
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@yogi-tud - I'm suggesting a number of small changes to your paper in https://github.com/yogi-tud/space_gpu/pull/4. In addition, I think a reference would be useful for "the NVIDIA-supplied CUB library" Once this is done, we can move to the final acceptance steps
@danielskatz There is already a reference to the cub main page. I renamed it to "NVIDIA CUB library" in the bib. Is that okay?
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
ok, thanks.
At this point could you:
I can then move forward with accepting the submission.
I have a question about meta data in Zenodo. Should it be "publication" or "software"?
Software. The archival deposit is mainly of the software, though the source of the publication may also in the archived repo
https://doi.org/10.5281/zenodo.6884000
I uploaded the 1.0 release which was just created from the github repo to zenodo. As my funding institutions were not listes as possible options, I did not add them unter the optional funding category.
@editorialbot set 10.5281/zenodo.6884000 as archive
Done! Archive is now 10.5281/zenodo.6884000
@editorialbot set 1.0 as version
Done! version is now 1.0
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.15803/ijnc.7.2_208 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/3391, 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 @yogi-tud (Johannes Fett) and co-authors!
And thanks to @robertszafa and @wimvanderbauwhede for reviewing! We couldn't do this without you
I'm going to leave this open for now, as I realize we had intended to mention Euro-Par in the final published PDF, which I think @arfon will need to do manually.
Thanks for the review and the smooth editorial process.
Also @wimvanderbauwhede, do we know the DOI for the Euro-Par paper? If so, we could also mention that in the left column, as we do with AAS-partnered papers, such as in https://joss.theoj.org/papers/10.21105/joss.04417
@danielskatz I have the DOIs for the conference papers but they are not live yet so if we put them in the JOSS paper they won't work yet.
@wimvanderbauwhede - Can we continue this discussion in the email I sent you around the same time as the comment above?
@yogi-tud ā could you please merge this PR to associate this submission with your Europar submission? https://github.com/yogi-tud/space_gpu/pull/5
@editorialbot generate pdf
@arfon I just merged your MR.
:warning: An error happened when generating the pdf.
@editorialbot reaccept
Rebuilding paper!
š Paper updated!
New PDF and metadata files :point_right: https://github.com/openjournals/joss-papers/pull/3411
What do you think @wimvanderbauwhede and @danielskatz?: https://github.com/openjournals/joss-papers/blob/e881a2735349adace33e66f83a60aab1852227a7/joss.04589/10.21105.joss.04589.pdf
Submitting author: !--author-handle-->@yogi-tud<!--end-author-handle-- (Johannes Fett) Repository: https://github.com/yogi-tud/space_gpu Branch with paper.md (empty if default branch): Version: 1.0 Editor: !--editor-->@danielskatz<!--end-editor-- Reviewers: @robertszafa, @wimvanderbauwhede Archive: 10.5281/zenodo.6884000
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
@robertszafa & @wimvanderbauwhede, 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 @danielskatz 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 @robertszafa
š Checklist for @wimvanderbauwhede