Skip to content
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

Closed
editorialbot opened this issue Aug 24, 2022 · 63 comments
Closed

[REVIEW]: Accelerated oblique random survival forests #4705

editorialbot opened this issue Aug 24, 2022 · 63 comments
Assignees
Labels
accepted C++ published Papers published in JOSS R recommend-accept Papers recommended for acceptance in JOSS. review rOpenSci Submissions associated with rOpenSci TeX Track: 5 (DSAIS) Data Science, Artificial Intelligence, and Machine Learning

Comments

@editorialbot
Copy link
Collaborator

editorialbot commented Aug 24, 2022

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

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/414871f081cd8449007d671a7f7f7c3a"><img src="https://joss.theoj.org/papers/414871f081cd8449007d671a7f7f7c3a/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/414871f081cd8449007d671a7f7f7c3a/status.svg)](https://joss.theoj.org/papers/414871f081cd8449007d671a7f7f7c3a)

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:

@editorialbot generate my 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

@editorialbot editorialbot added C++ R review TeX Track: 5 (DSAIS) Data Science, Artificial Intelligence, and Machine Learning labels Aug 24, 2022
@editorialbot
Copy link
Collaborator Author

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

@editorialbot
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.88  T=0.09 s (914.8 files/s, 185191.5 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
R                               45           2138           2154           4583
C++                              2           1216            875           2124
XML                              1              0              2            441
Rmd                             17            634            548            379
Markdown                         6            126              0            315
JSON                             1              0              0            270
YAML                             7             45             20            226
TeX                              1             15              0             84
-------------------------------------------------------------------------------
SUM:                            80           4174           3599           8422
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

@editorialbot
Copy link
Collaborator Author

Wordcount for paper.md is 784

@editorialbot
Copy link
Collaborator Author

Failed to discover a Statement of need section in paper

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.48550/ARXIV.2208.01129 is OK

MISSING DOIs

- 10.1007/978-3-030-56485-8_3 may be a valid DOI for title: Random forests
- 10.1214/19-aoas1261 may be a valid DOI for title: Oblique random survival forests
- 10.1161/circulationaha.120.053134 may be a valid DOI for title: Development and Validation of Machine Learning–Based Race-Specific Models to Predict 10-Year Risk of Heart Failure: A Multicohort Analysis
- 10.1016/j.patcog.2019.107078 may be a valid DOI for title: Heterogeneous oblique random forest

INVALID DOIs

- None

@danielskatz danielskatz added the rOpenSci Submissions associated with rOpenSci label Aug 24, 2022
@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@danielskatz
Copy link

danielskatz commented Aug 24, 2022

@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.

@danielskatz
Copy link

Also, is the "?" in this part of the text right?
Screen Shot 2022-08-24 at 9 12 09 AM

@danielskatz
Copy link

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 @editorialbot check references to check again, and the command @editorialbot generate pdf when the references are right to make a new PDF. editorialbot commands need to be the first entry in a new comment.

@danielskatz
Copy link

And finally, for the first two references, please fix the cases of the journals to "Machine Learning" and "The Annals of Applied Statistics"

@bcjaeger
Copy link

Thanks! I will work on this now.

bcjaeger added a commit to ropensci/aorsf that referenced this issue Aug 24, 2022
@bcjaeger
Copy link

@editorialbot check references

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1214/08-AOAS169 is OK
- 10.48550/ARXIV.2208.01129 is OK
- 10.1023/A:1010933404324 is OK
- 10.1214/19-AOAS1261 is OK
- 10.1161/circulationaha.120.053134 is OK
- 10.1016/j.patcog.2019.107078 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@bcjaeger
Copy link

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@danielskatz
Copy link

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 :)

@bcjaeger
Copy link

@danielskatz, thanks for the help today! Here is a list of updates based on your comments.

Please add a statement of need section to the paper

Done, see lines 23-28 of the updated draft.

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.

Good point. In the intro, I have added a general description of risk prediction (1st paragraph) and a summary of what aorsf does and what applications it has (second paragraph).

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.

Agreed. In the update, I've included

  • what risk prediction is and where it is used (lines 7-14)
  • what censored outcomes are (lines 45-50; they are used in risk prediction, defined earlier)
  • what survival decision trees are is included on lines 51-54

The bibliography and DOIs should also be in order now.

@bcjaeger
Copy link

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 :)

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?

@danielskatz
Copy link

sure!

@bcjaeger
Copy link

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.

@danielskatz
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1214/08-AOAS169 is OK
- 10.48550/ARXIV.2208.01129 is OK
- 10.1023/A:1010933404324 is OK
- 10.1214/19-AOAS1261 is OK
- 10.1161/circulationaha.120.053134 is OK
- 10.1016/j.patcog.2019.107078 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

⚠️ Error preparing paper acceptance. The generated XML metadata file is invalid.

ID ref-menze2011oblique already defined

@danielskatz
Copy link

@bcjaeger - please check your bib file - it seems like there's a bib label (menze2011oblique) that's being used twice.

@bcjaeger
Copy link

Sorry about that, the duplicated label has been removed.

@danielskatz
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1214/08-AOAS169 is OK
- 10.48550/ARXIV.2208.01129 is OK
- 10.1023/A:1010933404324 is OK
- 10.1214/19-AOAS1261 is OK
- 10.1161/circulationaha.120.053134 is OK
- 10.1016/j.patcog.2019.107078 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👋 @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 @editorialbot accept

@editorialbot editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Sep 27, 2022
@bcjaeger
Copy link

Thanks! I can confirm the final proof of the pdf looks good on my end.

@danielskatz
Copy link

@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

@bcjaeger
Copy link

Good catch - the title and author list on the zenodo release now match the paper.

@danielskatz
Copy link

@editorialbot accept

@editorialbot
Copy link
Collaborator Author

Doing it live! Attempting automated processing of paper acceptance...

@editorialbot
Copy link
Collaborator Author

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

@editorialbot
Copy link
Collaborator Author

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.04705 joss-papers#3559
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.04705
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels Sep 28, 2022
@danielskatz
Copy link

Congratulations to @bcjaeger (Byron Jaeger) and co-authors!!

@editorialbot
Copy link
Collaborator Author

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

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.04705/status.svg)](https://doi.org/10.21105/joss.04705)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04705">
  <img src="https://joss.theoj.org/papers/10.21105/joss.04705/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04705/status.svg
   :target: https://doi.org/10.21105/joss.04705

This is how it will look in your documentation:

DOI

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:

@bcjaeger
Copy link

Thank you!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted C++ published Papers published in JOSS R recommend-accept Papers recommended for acceptance in JOSS. review rOpenSci Submissions associated with rOpenSci TeX Track: 5 (DSAIS) Data Science, Artificial Intelligence, and Machine Learning
Projects
None yet
Development

No branches or pull requests

3 participants