Closed whedon closed 3 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @nistara, @adithirgis it looks like you're currently assigned to review this paper :tada:.
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
:star: Important :star:
If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿
To fix this do the following two things:
For a list of things I can do to help you, just type:
@whedon commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@whedon generate pdf
@nistara, @adithirgis: Thanks for agreeing to review. Please carry out your review in this issue by updating the checklist above and giving feedback in this issue. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If possible create issues (and cross-reference) in the submission's repository to avoid too specific discussions in this review thread.
If you have any questions or concerns please let me know.
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.18637/jss.v014.i09 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon commands
Here are some things you can ask me to do:
# List Whedon's capabilities
@whedon commands
# List of editor GitHub usernames
@whedon list editors
# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers
EDITORIAL TASKS
# Compile the paper
@whedon generate pdf
# Compile the paper from alternative branch
@whedon generate pdf from branch custom-branch-name
# Ask Whedon to check the references for missing DOIs
@whedon check references
# Ask Whedon to check repository statistics for the submitted software
@whedon check repository
Started review here.
@whedon check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.18637/jss.v014.i09 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@VincentAlcazer, can you give a brief status on the review issues raised in the separate threads by @nistara and @adithirgis?
Dear @mikldk, I am currently working on the issues raised by the reviewers and their comments are really helping me improving the software. Due to the pandemic evolution in France, I am also quite busy at the hospital with only few moments to work on StatAid. However, I already corrected the main issues reported and I hope I'll be able to provide my complete answer soon. I am very sorry for this delay and will do my best to proceed through the reviewing in time. Best regards,
@VincentAlcazer No need to be sorry - take your time. I just wanted to check in, also for the reviewers' sake. Be safe.
Hi @VincentAlcazer, please take your time, we're in no hurry. Thanks for your important work right now during the pandemic.
Hi @VincentAlcazer, I totally agree with @nistara and @mikldk, please take your time. And please stay safe. Take care.
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Dear @mikldk,
I have completed my review process. Thanks again for inviting me to review.
Thanks @VincentAlcazer for the wonderful application. This is a really interesting and useful software!
Regards and Stay Safe Adithi
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Dear @mikldk and @VincentAlcazer ,
I'm done with my review. Thank you for inviting me as a reviewer. This package is pretty awesome and should help many people explore various descriptive and statistical tools and visualizations with one tool!! I also appreciate the careful consideration give to what potential users might need to customize their analysis and plots.
Best wishes, Nistara
Dear @mikldk ,
Thank you for giving me the opportunity to have my software reviewed by JOSS. I would like to thanks @nistara and @adithirgis who did an amazing job thoroughly reviewing StatAid and really helped me to improve the software.
Please let me know if there is anything else I should do now for the following submission process.
Best regards,
Vincent Alcazer
@whedon check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.18637/jss.v014.i09 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Thanks for @nistara and @adithirgis for their reviews.
@VincentAlcazer :
@whedon generate pdf
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Dear @mikldk ,
I did not know iNZight which seems to be a pretty good software developed by a serious team. This software is however different from StatAid in multiple points:
All-together, I would say that StatAid is more convenient for quickly accessing publication-ready graph and table, really guiding the authors through their data analysis. iNZight seems to have a more complete solution (with data modification and recoding possibilities), to the cost of less user-friendly / guiding interface. Only StatAid is providing a time-dependent variable analysis option and has this evolving / contributive aspect.
I checked the paper.md and everything seems OK. I uploaded the 1.1 version on zenodo with the following DOI:
10.5281/zenodo.4081353
Thank you.
Best regard,
Vincent Alcazer
@VincentAlcazer: I think the paper would benefit from including some of these considerations. What do you think, @nistara and @adithirgis?
Hi @mikldk and @VincentAlcazer,
I think it would good to add the strong points (for the benefit of the users) in the paper.
I agree as well...these points provide a contrast for StatAid and also highlight some of its salient features. In addition to options for different statistical tests, I particularly liked the visualization options and the choice of different color palettes. A lot of consideration should go into analyses in general, and there could be models more suitable than those provided at the moment (e.g. mixed models), but I can see lots of people, including students, benefiting from exploring their data with this software and using it for their work. So yes, including the above considerations would definitely benefit the paper and the readers in understanding what the software offers.
Dear @mikldk @nistara @adithirgis ,
Thank you again for your messages and suggestions.
The paper.md has been updated taking into account these considerations:
Addition in the summary: "Other free software exist such as iNZight or Jamovi. However, while providing solutions with multiple features such as variable recoding, these software do not guide the user through the analysis and can lack some key features such as time-dependent outcome analysis."
In the Statement of need: "Compared to other free similar software, StatAid has been designed to quickly produce publication-ready graph and table by really guiding the user through their data analysis and providing multiple graph customization options. By limiting the number of choices and integrating different check and variable controls, StatAid hence help the user to prevent bad test use or bad graph choice. Besides, as an evolving software, only StatAid is providing the possibility for users to ask for the implementation of a particular feature or to contribute to the software development. Its open-source aspect can also be seen as a security for people working with sensitive data (e.g. data from clinical trials / patients). The online version of StatAid renders it accessible everywhere, even on computers with restrictive software installation policies such as hospitals or research centers."
Please let me know if you have anything else in mind to improve the paper/software.
Best regards,
Vincent
I think this is summarised well. I had a small suggestion if everyone else agrees (and also if I am not wrong :))
In the Statement of need: "Compared to other free similar software, StatAid has been designed to quickly produce publication-ready graph and table by ~really~ guiding the user through their data analysis and providing multiple graph customization options. By limiting the number of choices and integrating different check and variable controls, StatAid ~hence~ helps the user to prevent bad test use or bad graph choice. Besides, as an evolving software, ~only~ StatAid ~is~ also provides the possibility for users to ~ask~ request for the implementation of a particular feature or to contribute to the software development. Its open-source aspect can also be seen as a security for people working with sensitive data (e.g. data from clinical trials / patients). The online version of StatAid renders it accessible everywhere, even on computers with restrictive software installation policies such as hospitals or research centers. (Can this sentence be modified a little?)"
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Dear @mikldk @nistara @adithirgis ,
The paper.md has been updated with @adithirgis 's suggestions.
Best regards,
Vincent
@nistara, @adithirgis: Can you confirm that you have finished the review and recommend that this paper is now published?
@VincentAlcazer:
@whedon generate pdf
Hi all!
I confirm that I have reviewed the paper and I recommend to publish this. All the best @VincentAlcazer! StatAid is an amazing and useful software.
Though I am not a good English language speaker/ user, but I do feel that the first point of plural usage seems correct.
Thanks so much again for inviting me!
Regards and Stay Safe Adithi
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @mikldk, @VincentAlcazer, and @adithirgis
I had previously submitted a pull request for typos and minor issues of the like in the paper/software (https://github.com/VincentAlcazer/StatAid/commit/d0afe60a93836b246158fe15b35f81567d1b8fc8), however, I am not sure if I can make extensive grammatical edits as a reviewer. I do realize/respect that as multilingual people we might require some assistance in one or the other language, and so if it's acceptable, I conducted some extra proofreading and can create another pull request for it: https://github.com/nistara/StatAid/commit/85fe82e6da936b829988c61a747db3865766c115
If it's fine by you, I would recommend this paper once the above edits have been incorporated.
Regards, Nistara
Dear @nistara ,
Thank you for this complete proofread of the paper. If it's fine for everybody, I am waiting your pull request to integrate it and make the new Zenodo archive.
Best regards,
Vincent
@nistara @VincentAlcazer That sounds like a good plan. Thanks. Please ping me once the PR has been merged and the archive updated.
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Dear @mikldk ,
The paper has been completely reviewed and the software archive updated on zenodo (StatAid v1.1.0 - DOI 10.5281/zenodo.4146739).
I would like to thank again the reviewers @nistara and @adithirgis for their amazing work and the time they have taken to help me improving both the software and the paper.
Best regards,
Vincent Alcazer
@whedon set v1.1.0 as version
OK. v1.1.0 is the version.
@whedon set 10.5281/zenodo.4146739 as archive
OK. 10.5281/zenodo.4146739 is the archive.
Submitting author: @VincentAlcazer (Vincent Alcazer) Repository: https://github.com/VincentAlcazer/StatAid Version: v1.1.2 Editor: @mikldk Reviewer: @nistara, @adithirgis Archive: 10.5281/zenodo.4152933
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
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
@nistara & @adithirgis, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @mikldk 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 ✨
Review checklist for @nistara
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @adithirgis
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper