[REVIEW]: Rasusa: Randomly subsample sequencing reads to a specified coverage

[whedon]

Submitting author: @mbhall88 (Michael Hall)
Repository: https://github.com/mbhall88/rasusa
Version: v0.6.1
Editor: @mikldk
Reviewer: @k3yavi, @holtgrewe
Archive: 10.5281/zenodo.5895111

⚠️ JOSS reduced service mode ⚠️

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.

Status

Status badge code:

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

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

@k3yavi & @holtgrewe, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:

1. Make sure you're logged in to your GitHub account
2. Be sure to accept the invite at this URL: https://github.com/openjournals/joss-reviews/invitations

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @mikldk 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 ✨

Review checklist for @k3yavi

✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the repository url?
• License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@mbhall88) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Does the paper have a section titled 'Statement of Need' that clearly states what problems the software is designed to solve and who the target audience is?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

Review checklist for @holtgrewe

✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the repository url?
• License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@mbhall88) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Does the paper have a section titled 'Statement of Need' that clearly states what problems the software is designed to solve and who the target audience is?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[whedon]

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @k3yavi, @holtgrewe it looks like you're currently assigned to review this paper 🎉.

⚠️ JOSS reduced service mode ⚠️

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.

⭐ Important ⭐

If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿

To fix this do the following two things:

1. Set yourself as 'Not watching' https://github.com/openjournals/joss-reviews:

2. You may also like to change your default settings for this watching repositories in your GitHub profile here: https://github.com/settings/notifications

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

[whedon]

Software report (experimental):

github.com/AlDanial/cloc v 1.88  T=0.04 s (345.9 files/s, 86114.5 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Rust                             5            318            278           1528
Markdown                         2            187              0            516
YAML                             3             40             12            298
TOML                             2              3              1             32
Dockerfile                       1              9              0             14
-------------------------------------------------------------------------------
SUM:                            13            557            291           2388
-------------------------------------------------------------------------------


Statistical information for the repository '7d29f2b8405fd72a4e0460a4' was
gathered on 2021/11/22.
No commited files with the specified extensions were found.

[whedon]

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

 Can't find any papers to compile :-(

[mikldk]

@whedon check references from branch joss_paper

[whedon]

Attempting to check references... from custom branch joss_paper

[whedon]

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

OK DOIs

- 10.1186/s40793-019-0347-1 is OK
- 10.1186/s12859-018-2445-2 is OK
- 10.1099/mgen.0.000294 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[mikldk]

@whedon generate pdf from branch joss_paper

[whedon]

Attempting PDF compilation from custom branch joss_paper. Reticulating splines etc...

[whedon]

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

[mikldk]

@k3yavi, @holtgrewe: Thanks for agreeing to review. Please carry out your review in this issue by updating the checklist above and giving feedback in this issue. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If possible create issues (and cross-reference) in the submission's repository to avoid too specific discussions in this review thread.

If you have any questions or concerns please let me know.

[mikldk]

@k3yavi, @holtgrewe, can you please give a brief status of your review? This is not to rush you, merely to give me an impression of the progress and time-frame.

[whedon]

👋 @k3yavi, please update us on how your review is going (this is an automated reminder).

[whedon]

👋 @holtgrewe, please update us on how your review is going (this is an automated reminder).

[k3yavi]

Hi @mikldk , according to JOSS guidelines, I think the paper and the tool passes all the criteria mentioned in the checklist.

I do have some minor points to mention, is it Ok to mention them here or the review is strictly checklist based ?

[mikldk]

@k3yavi Sounds good. Your input would be very valuable. Please create issues in the repo and mention this issue such that they are linked.

[mikldk]

@holtgrewe, can you please give a brief status of your review? This is not to rush you, merely to give me an impression of the progress and time-frame.

[holtgrewe]

@mikldk sorry for the delay, will do it over christmas

[mikldk]

@holtgrewe, can you please give a brief status of your review? This is not to rush you, merely to give me an impression of the progress and time-frame.

[holtgrewe]

@mikldk I'm starting now.

[holtgrewe]

The invitation link has expired. I'll continue my review anyway now. Let me know how to proceed in the "formal" process.

[holtgrewe]

I could not edit the checklist above. I took the one from the joss docs, below are the fields I filled. I need to actually test the software on Monday.

manuscript

summary

• actually also useful for benchmarks

main text

• Can review guideline be addressed? "Mentions (if applicable) of any ongoing research projects using the software or recent scholarly publications enabled by it."
• The link to the software archive appears to not work.

review considerations

• software license: MIT, license file is there
• scholarly effort: check
• documentation
  • statement of need: check
  • installation instructions: excellent
  • example usage: excellent
  • functionality: TODO
  • tests: excellent
• authorship: check
• novelty: check
• proprietary software: not applicable

checklist

general

• repository URL: OK
• license: OK
• contribution and authorship: OK

functionality

• installation: check
• functionality: check
• performance: check

documentation

• statement of need: check
• installation: check
• example usage: check
• functionality documentation: check
• automated tests: check
• community guidelines: (1) check, for (2,3): it's a github project with issues, so these work for me - check

software paper

• summary: check
• statement of need: check
• state of the field: check
• quality of writing: check
• reference: check

[mikldk]

@whedon re-invite @holtgrewe as reviewer

[whedon]

OK, the reviewer has been re-invited.

@holtgrewe please accept the invite by clicking this link: https://github.com/openjournals/joss-reviews/invitations

[whedon]

Attempting PDF compilation from custom branch joss_paper. Reticulating splines etc...

[whedon]

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

[mbhall88]

@mikldk I am happy with the final proofs.

Regarding the tagged release: I have Zenodo integrated with the repository already, so when I tag a release, a Zenodo archive will be created automatically. Is this fine?

One question before I tag a new release: should I merge the joss_paper branch into the master branch and then tag? That way the paper is included with the release?

[mikldk]

@mbhall88 You don't have to merge the joss_paper branch into the main branch. It's up to you. Please let me know once you have made a release that is accessible at e.g. Zenodo.

[mbhall88]

Hi @mikldk I have merged joss_paper into master and tagged a release with v0.6.1. It's on Zenodo at https://doi.org/10.5281/zenodo.5895111

[mikldk]

@whedon set 10.5281/zenodo.5895111 as archive

[whedon]

OK. 10.5281/zenodo.5895111 is the archive.

[mikldk]

@whedon set v0.6.1 as version

[whedon]

OK. v0.6.1 is the version.

[mikldk]

@mbhall88: Can you add "B." initial to Zenodo? (Or remove it from the paper.)

[mbhall88]

@mbhall88: Can you add "B." initial to Zenodo? (Or remove it from the paper.)

Changed on Zenodo.

[mikldk]

@whedon check references

[whedon]

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

OK DOIs

- 10.1186/s40793-019-0347-1 is OK
- 10.1186/s12859-018-2445-2 is OK
- 10.1099/mgen.0.000294 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[mikldk]

@whedon recommend-accept

[whedon]

Attempting dry run of processing paper acceptance...

[whedon]

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

OK DOIs

- 10.1186/s40793-019-0347-1 is OK
- 10.1186/s12859-018-2445-2 is OK
- 10.1099/mgen.0.000294 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[whedon]

👋 @openjournals/joss-eics, this paper is ready to be accepted and published.

Check final proof 👉 openjournals/joss-papers#2906

If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#2906, then you can now move forward with accepting the submission by compiling again with the flag deposit=true e.g.

@whedon accept deposit=true

[mbhall88]

Final proof looks good to me. Do I accept this or do you @mikldk?

[mikldk]

@mbhall88 Neither of us - an EiC will do that when they have checked that everything looks fine.

[arfon]

@whedon accept deposit=true

[whedon]

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

[whedon]

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

[whedon]

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

Here's what you must now do:

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

Any issues? Notify your editorial technical team...

[arfon]

@k3yavi, @holtgrewe – many thanks for your reviews here and to @mikldk for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨

@mbhall88 – your paper is now accepted and published in JOSS ⚡🚀💥

[whedon]

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

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

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

This is how it will look in your documentation:

We need your help!

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:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://joss.theoj.org/reviewer-signup.html
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss