-
-
Notifications
You must be signed in to change notification settings - Fork 38
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]: Omnizart: A General Toolbox for Automatic Music Transcription #3218
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. 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. 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:
|
Failed to discover a |
|
|
@BreezeWhite thanks for this submission. Our editors in this domain are currently not able to take on this submission. I have therefore added the "waitlisted" label, which means one of our editors will pick up this work once they become available. Thanks for your patience. In the mean time please consider these comments:
|
Perhaps @bmcfee or @terrytangyuan could take this submission once they are available. |
@Kevin-Mattheus-Moerman Thank you for your mention! And also thanks for the quick advice on our submission. We are currently modifying the content according to your suggestion. As for the third point, the word count we see on the editor shows there are total 1000 words, just fit in the upper limit. Would that still be a problem? If so, we will try continue to shorten the paper. |
@BreezeWhite if you are at the 1000 word limit that could be fine. As long as you are not repeating content from the documentation. Thanks. |
@faroit has been invited to edit this submission. |
@whedon assign me as editor |
OK, the editor is @faroit |
👋 Hi @BreezeWhite, thanks for your submission to JOSS! I will be serving as the editor for this. We'll use this issue to identify reviewers and resolve technical issues. As this toolbox implements a bunch of transcription models, it would be great to have reviewers with domain knowledge who also have experience with frameworks used in the MIR community... I have a few potential reviewers in mind:
@BreezeWhite, I am also interested in your input on potential reviewers, so any suggestions you have are also welcome. |
@BreezeWhite while we find potential reviewers, can you please address #3218 (comment) and add the missing DOIs as indicated by the reference check summary? |
@whedon generate pdf |
Hi @faroit, thank you for the suggestions. For the DOI issue, I've just updated the missing DOIs in the |
@whedon check references |
@whedon set v0.4.1 as version |
I'm sorry @BreezeWhite, I'm afraid I can't do that. That's something only editors are allowed to do. |
|
@whedon set v0.4.1 as version |
OK, @hagenw is now a reviewer |
@whedon add @keunwoochoi as reviewer |
OK, @keunwoochoi is now a reviewer |
@whedon list reviewers |
@whedon check references |
@whedon check repository |
|
|
@Kevin-Mattheus-Moerman Is there anything left in the comments you made in #3218 (comment) that should be addressed by @BreezeWhite before we proceed with the review process? |
@whedon generate pdf |
@faroit thanks for letting me check this before moving on. Yes I ticked those boxes. I have one more minor comment/recommendation below. I recommend that the following sentence is rephrased: I have 2 issues with this sentence.
I'm not saying the following is the best possible sentence (give this some thought and formulate something yourself) but the following would be an example to avoid the above issues (perhaps summarize something in place of those dots): @faroit I'll leave you to follow up with this if that is okay, and if you agree. |
Hi @Kevin-Mattheus-Moerman, thank you for the advises. I have rephrased the sentences as you have pointed out. Please see if there are still needs to modify the content. |
@Kevin-Mattheus-Moerman thanks for your suggestions, @BreezeWhite has addressed your comment. |
@whedon generate pdf |
@whedon check repository |
@whedon check references |
|
|
@whedon start review |
OK, I've started the review over in #3391. |
Submitting author: @BreezeWhite (Yu Te Wu)
Repository: https://github.com/Music-and-Culture-Technology-Lab/omnizart
Version: v0.4.1
Editor: @faroit
Reviewers: @hagenw, @keunwoochoi
Managing EiC: Arfon Smith
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.
Author instructions
Thanks for submitting your paper to JOSS @BreezeWhite. Currently, there isn't an JOSS editor assigned to your paper.
@BreezeWhite 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 @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:
The text was updated successfully, but these errors were encountered: