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
[PRE REVIEW]: dsBinVal: Conducting distributed ROC analysis and Calibration using DataSHIELD #4473
Comments
Hello human, 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 |
Note for other editors, this is a re-submission of a previously-rejecting submission (#4287) |
@editorialbot invite @csoneson as editor 👋 @csoneson – would you be able to edit this submission for JOSS? |
Invitation to edit this submission sent! |
@editorialbot invite @csoneson as editor |
Invitation to edit this submission sent! |
@csoneson can you help with this one? |
Sorry for the delay - I must have missed the first invite. This is a bit outside my expertise, but I can give it a go. @schalkdaniel - could you give a brief summary of the differences compared to the previous submission of this work? Also, if you have suggestions for reviewers (e.g. from the list linked in the first post above), please mention them here. |
@editorialbot assign @csoneson as editor |
Assigned! @csoneson is now the editor |
@csoneson - Sure, the first idea we had was to have multiple I don't really have preferences for the reviewer. But, I picked three candidates from the linked list who seem active on GitHub and do have a machine learning / biostats / bioinformatics background:
|
@schalkdaniel - great, thanks for the summary! 👋🏻 @zhiiiyang, @brunomontezano - would you be interested in reviewing this submission for JOSS?
|
@csoneson, I might not have time to review this one. Feel free to pass me. |
@zhiiiyang - no worries, thanks for letting us know! |
👋🏻 @gsfyrakis, @patRyserWelch8, @MaximLippeveld - would (two of) you be available and interested in reviewing this submission for JOSS?
|
@patRyserWelch8 Thank you! We usually ask reviewers to provide a first round of reviews within ~2 weeks (once we have secured two reviewers, I will assign you and open the review issue, where you will be able to generate your review checklist and start the review). However, I should also note that in many cases it is easier to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package. |
Firstly, thanks for the invitation. And secondly, I accept the invite to review this paper. |
@brunomontezano - brilliant, thanks! As we now have our two reviewers, I will start the review issue. |
@editorialbot add @patRyserWelch8 as reviewer |
@patRyserWelch8 added to the reviewers list! |
@editorialbot add @brunomontezano as reviewer |
@brunomontezano added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #4545. |
Submitting author: @schalkdaniel (Daniel Schalk)
Repository: https://github.com/difuture-lmu/dsBinVal
Branch with paper.md (empty if default branch):
Version: v1.0.1
Editor: @csoneson
Reviewers: @patRyserWelch8, @brunomontezano
Managing EiC: Arfon Smith
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @schalkdaniel. Currently, there isn't an JOSS editor assigned to your paper.
The author's suggestion for the handling editor is @csoneson.
@schalkdaniel if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: