-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REVIEW]: Accelerated oblique random survival forests #4705
Comments
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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Wordcount for |
Failed to discover a |
|
@bcjaeger - please add a statement of need section to the paper, and in that, or in the introduction, please explain more generally what this software does and what types of applications it has, remembering that JOSS has a very diverse readership, not all of which has detailed machine learning expertise. For example, the paper probably needs to explain what right-censored time-to-event data is and where it appears/is used, what survival decision trees are and where they appear/are used, what risk prediction models are and where they appear/are used, etc. |
Another issue: please address the possibly missing DOIs that editorialbot suggests, but note that some may be incorrect. Please feel free to make changes to your .bib file, then use the command |
And finally, for the first two references, please fix the cases of the journals to "Machine Learning" and "The Annals of Applied Statistics" |
Thanks! I will work on this now. |
@editorialbot check references |
|
@editorialbot generate pdf |
Thanks - this looks good to me. I will also proofread this more carefully when you are ready - please let me know if that's now, and if not, when it is :) |
@danielskatz, thanks for the help today! Here is a list of updates based on your comments.
Done, see lines 23-28 of the updated draft.
Good point. In the intro, I have added a general description of risk prediction (1st paragraph) and a summary of what
Agreed. In the update, I've included
The bibliography and DOIs should also be in order now. |
Thank you! I would like to read through it once more tonight. May I add a post here sometime this evening (about 5 hours from now) to let you know when I've finished? |
sure! |
I think it is ready for your review. The only change I am considering is swapping the statement of need section with the background section so that the background section would come before the statement of need. This change may be helpful because the statement of need covers topics that are introduced in the background. I'm looking forward to hearing what you think. |
@editorialbot recommend-accept |
|
|
ID ref-menze2011oblique already defined |
@bcjaeger - please check your bib file - it seems like there's a bib label (menze2011oblique) that's being used twice. |
Sorry about that, the duplicated label has been removed. |
@editorialbot recommend-accept |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉📄 Download article If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3557, then you can now move forward with accepting the submission by compiling again with the command |
Thanks! I can confirm the final proof of the pdf looks good on my end. |
@bcjaeger - please update the zenodo metadata (which does not require a new deposit, version, or DOI) so that the title and authors match those of the paper |
Good catch - the title and author list on the zenodo release now match the paper. |
@editorialbot accept |
|
🐦🐦🐦 👉 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 @bcjaeger (Byron Jaeger) and co-authors!! |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
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:
|
Thank you!! |
Submitting author: @bcjaeger (Byron Jaeger)
Repository: https://github.com/bcjaeger/aorsf
Branch with paper.md (empty if default branch):
Version: v0.0.3
Editor: @danielskatz
Reviewers: @danielskatz
Archive: 10.5281/zenodo.7116855
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
@danielskatz, 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
@danielskatz, please create your checklist typing:
@editorialbot generate my checklist
The text was updated successfully, but these errors were encountered: