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.06 s (444.5 files/s, 151670.3 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
HTML 4 144 8 3424
R 11 115 664 1929
Rmd 4 356 1369 245
TeX 1 11 0 105
Markdown 3 31 0 61
YAML 2 11 6 52
-------------------------------------------------------------------------------
SUM: 25 668 2047 5816
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 339
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1002/ejsp.2023 is OK
- 10.1177/0146167220913363 is OK
- 10.5334/irsp.181 is OK
- 10.5964/meth.2811 is OK
- 10.1111/2041-210X.12504 is OK
- 10.1177/2515245920951503 is OK
MISSING DOIs
- 10.1016/c2013-0-10517-x may be a valid DOI for title: Statistical power analysis for the behavioral sciences
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@mmrabe and @mingzehuang - how are the reviews going? Please feel free to discuss here any revisions that the authors must make before publication. Thanks again!
Hi @fboehm ! I expect to finish the review by Tuesday. I hope that still works. Sorry for the delay.
Hi, @gasparl, your package looks nice:) I see you have "contribution" section in your README file. I would suggest you also include code of conduct like many other open source packages:)
Hi, @fboehm, I'm reviewing! Hopefully I can get it done by this weekend:)
Hi, @gasparl, you have numerous great example with the link in your README:) Would you mind picking one simple example as an illustration of functionality and putting it in your JOSS paper like many other papers on JOSS?
Thanks so much, @mmrabe and @mingzehuang ! Please feel free to ask me questions - here, in the comments - if you're unsure about anything. Thanks again!
Sure.
@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, @gasparl, there is a requirement about automatic test in checklist. Would you mind using codecov and embedding the badge of coverage rate into your README.md?
Hi, @gasparl, there is a requirement about automatic test in checklist. Would you mind using codecov and embedding the badge of coverage rate into your README.md?
Sure, I added it. (The relatively low percentage [52%] is because I included lots of warning messages for making the functions more foolproof, but these don't really need to be tested.)
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
The author @gasparl has written a very useful and flexible tool for simulation-based power analysis. The documentation and vignettes exceed the expected extent by far and provide many helpful examples. The submitted paper has become a lot stronger after adding a simple example, as @mingzehuang suggested.
Before I can check off all items on my checklist and recommend this software paper for publication, please attend to the following:
I would also like to make a minor suggestion, which may make the package more straightforward to use for the average R user and possibly increase the audience:
@gasparl already worked on the issues I posted to the repo as I was writing the lines above. So I can check off the remaining two boxes from my checklist right away. Thanks!
Thank you very much @mmrabe for your kind and helpful review. Yes, I already answered the request (pardon my haste ;) ).
I'll also think about and address your suggestion, hopefully in the coming days.
Thank you @gasparl ! I see the codecov!
Thank you very much for your nice review, @mingzehuang!
I confirm that the new get_p(...)
method is working and well documented. It has even found its way into the vignettes already. Thanks for adding this right away, @gasparl! I believe this will be very helpful to some potential users. I can without any concern recommend this paper for publication in JOSS. Great job!
Thanks again @mmrabe !
Thanks to the reviewers, @mmrabe and @mingzehuang for thorough and helpful reviews, and to @gasparl for timely implementation of the suggestions. The next step is for me to proofread the paper. I might have minor suggestions once I do that. I'll mention you, @gasparl, once I've completed this step.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
The paper looks really good. I have a minor correction that is needed:
line 50 in the pdf: capitalize R One way to do this is to put braces around capital R in your bib file: {R}
I have no other edits to suggest for the paper
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1002/ejsp.2023 is OK
- 10.1093/biomet/64.2.191 is OK
- 10.1177/0146167220913363 is OK
- 10.5334/irsp.181 is OK
- 10.5964/meth.2811 is OK
- 10.1111/2041-210X.12504 is OK
- 10.1177/2515245920951503 is OK
MISSING DOIs
- 10.1016/c2013-0-10517-x may be a valid DOI for title: Statistical power analysis for the behavioral sciences
INVALID DOIs
- None
@gasparl - can you check to see if the suggested "missing DOI" is valid? If so, please add it to the bib file (and the resulting pdf). Thanks again!
I manually checked the currently present DOIs, and they all resolved to the intended targets.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Excellent, @gasparl! thanks for making those additions.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
The references all look good now. For the next steps, @gasparl, we need you to make a new release of the package and archive it, for example, with zenodo.org. Once you complete those tasks, please report here the version number and doi. Please ensure that the archive's author names and title match exactly those of the paper.pdf.
Sure @fboehm, here it is: Version number: v0.6.1 DOI: https://doi.org/10.5281/zenodo.7027767
(The Zenodo badge with permanent DOI is also displayed on the GitHub repo.)
@editorialbot set 10.5281/zenodo.7027767 as doi
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@editorialbot commands
@editorialbot set 10.5281/zenodo.7027767 as archive
Done! Archive is now 10.5281/zenodo.7027767
@editorialbot set v0.6.1 as version
Done! version is now v0.6.1
Submitting author: !--author-handle-->@gasparl<!--end-author-handle-- (Gáspár Lukács) Repository: https://github.com/gasparl/possa/ Branch with paper.md (empty if default branch): Version: v0.6.1 Editor: !--editor-->@fboehm<!--end-editor-- Reviewers: @mingzehuang, @mmrabe Archive: 10.5281/zenodo.7027767
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
@mingzehuang & @mmrabe, 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 @fboehm 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 @mmrabe
📝 Checklist for @mingzehuang