Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

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

What happens now?

This submission is currently in a pre-review state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience 😸

You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here.

Attempting PDF compilation. Reticulating splines etc...

Failed to discover a valid open source license.

PDF failed to compile for issue #1659 with the following error:

/app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/lib/whedon.rb:143:in block in check_orcids': Problem with ORCID (0000-0000-0000-0000) for Stefan Uhlich (RuntimeError) from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/lib/whedon.rb:141:in each'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/lib/whedon.rb:141:in check_orcids' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/lib/whedon.rb:88:in initialize'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/lib/whedon/processor.rb:36:in new' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/lib/whedon/processor.rb:36:in set_paper'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/bin/whedon:55:in prepare' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-80a4e9edb5a6/bin/whedon:116:in <top (required)>'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in load' from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in

Please merge sigsep/open-unmix-paper-joss#1 and see if that enables the paper to build by entering @whedon generate pdf as a new comment here. (also note that I suggested a number of language changes as well in the PR - these are all optional...

👋 @arokem - would you be willing to edit this submission?

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

👉 Check article proof 📄 👈

@danielskatz regarding the use of submodules, please note my questions I asked earlier in JOSS#565.

Thanks for pointing that out - please also mention it in the review thread that will be created once there are an editor and reviewers assigned.

Also, while we wait for that, you might want to make some fixes in the bib part of the paper - anything in a title or booktitle that should be in Upper Case needs to be protected with {}s, for example
booktitle={Proc. {IEEE} Intl. Conf. on Acoustics, Speech and Signal Processing (ICASSP)},
could be
booktitle={{Proc. IEEE Intl. Conf. on Acoustics, Speech and Signal Processing (ICASSP)}},
to preserve all cases, or you could manually select parts to preserve, noting that the "." triggers automatic capitalization of the following word...

Another example is
title = {MUSDB18-HQ - an uncompressed version of MUSDB18},
which could be
title = {{MUSDB18-HQ} - an uncompressed version of {MUSDB18}},
or
title = {{MUSDB18-HQ - an uncompressed version of MUSDB18}},

Also, while we wait for that, you might want to make some fixes in the bib part of the paper

sure, will do.

Another question: can you please point me to JOSSs pre-print policy? E.g. can I simultaneously submit to arxiv?

This is fine, although it's a little unusual - JOSS papers are usually short and focus on the software itself, while authors often write longer papers about the use of the software, for journals or conferences, and those longer papers are the ones that are usually submitted as pre-prints.

This is fine, although it's a little unusual - JOSS papers are usually short and focus on the software itself, while authors often write longer papers about the use of the software, for journals or conferences, and those longer papers are the ones that are usually submitted as pre-prints.

maybe our contribution is a bit unusual here, indeed. We actually wrote the paper to be significanlty longer, describing the technical details of the model (see arxiv branch) and then shortened it to <2000 words to comply with the JOSS policy.
Since there are not many scientific contributions being made – the model is basically the distillation of multiple former methods, we therefore, really would like to stick to a JOSS-only contribution for now and will probably write a longer journal later this year, that include larger scale experiments, hence a more rigor scientific contribution.

Now, we still want to offer a DOI for the community as quickly as possible, because we expect them to cite this paper very soon with the upcoming deadlines of the major conferences in our field.

Ok, thanks