[REVIEW]: sierra-local: A lightweight standalone application for drug resistance prediction

[whedon]

Submitting author: @ArtPoon (Art Poon)
Repository: https://github.com/PoonLab/sierra-local
Version: v0.1.2
Editor: @pjotrp
Reviewer: @azneto
Archive: 10.5281/zenodo.2548745

Status

Status badge code:

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

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

@azneto , 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.theoj.org/about#reviewer_guidelines. Any questions/concerns please let @pjotrp know.

✨ Please try and complete your review in the next two weeks ✨

Review checklist for @azneto

Conflict of interest

• As the reviewer I confirm that I have read the JOSS conflict of interest policy and that there are no conflicts of interest for me to review this work.

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?
• Version: Does the release version given match the GitHub release (v0.1.2)?
• Authorship: Has the submitting author (@ArtPoon) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

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 function 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

• Authors: Does the paper.md file include a list of authors with their affiliations?
• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• References: Do all archival references that should have a DOI list one (e.g., papers, datasets, software)?

[whedon]

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @azneto it looks like you're currently assigned as the reviewer for this paper 🎉.

⭐ 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

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[pjotrp]

@ArtPoon, we are starting review in this issue tracker. To expedite the review process do you mind going through above list of check boxes and make sure they can be ticked (you can't tick them). Also check the PDF output carefully. Ping us here when you are done.

[ArtPoon]

Thanks for your help @pjotrp. I confirm that I am unable to tick the checkboxes above.

I've read through the current article proof. The only issue I've noticed is that the capitalization of some article and journal titles was not properly protected in the .bib file. I have made corrections - is it ok for me to re-render the proof?

[pjotrp]

Of course. '@whedon generate pdf' will do it.

[ArtPoon]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[ArtPoon]

OK @pjotrp, I've checked the revised PDF output and it looks OK to me.

[pjotrp]

Thanks @ArtPoon. @azneto you can start review here. Please read the reviewer guidelines above.

[azneto]

@ArtPoon, congratulations! This is a very useful tool to run the analyses on HIVdb. It considerably improves the user experience in every way by allowing to run analyses locally. I've ran the software a few times during the last days using Ubuntu. The software is well documented and runs really fast.

Though the documentation for the end users is really good and comprehensive, the code itself is not so inviting. It doesn't follow the PEP8 (Style Guide for Python Code) and the PEP20 (The Zen of Python). There are variables and libraries that were created/loaded and never used (eg. definitions, database, comments, pathlib.Path, requests, default_grange). The software flake8 can find those and also check if the code is compatible with the PEP8, in future releases. I also recommend using typing (https://docs.python.org/3/library/typing.html).

The software should be ACCEPTED with minor revisions:
PoonLab/sierra-local#52
PoonLab/sierra-local#53

[pjotrp]

Thank you @azneto. @ArtPoon ping me when you are done. There are tools to automatically convert styles, btw. Also for PEP8. Good idea to try mentioned flake8.

[pjotrp]

Also a good idea to add a few lines on community guidelines. How can people contribute. Sometimes it happens ;)

[azneto]

@ArtPoon, the style is important but not required for this review. Just focus on the two pending issues and let the other improvements for the next releases.

[ArtPoon]

Thanks @azneto for your review! As you suggest, I will address the issues you've opened for the paper, and then in the longer term work on improving the code style. I'll also add a CONTRIBUTING file as suggested and report back here.

[ArtPoon]

Hi @azneto and @pjotrp, I've addressed and closed the issues.

[pjotrp]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[pjotrp]

@ArtPoon The review process is now complete. To finalize your submission and
accept your paper in JOSS, we need two things. First, can you confirm
that all references in your bibliography have a DOI in the bibliography
(if one exists).

Second, we need you to deposit a copy of your software repository
(including any revisions made during the JOSS review process) with a data-archiving service.

To do so:

1. Create a GitHub release of the
   current version of your software repository
2. Deposit that release with Zenodo, figshare,
   or a similar DOI issuer.
3. Post a comment here with the DOI for the release.

[ArtPoon]

[ArtPoon]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[ArtPoon]

@pjotrp, I have deposited the current release of the repository to Zenodo, obtained and posted the DOI above. I also found and restored some missing DOIs for cited references in the paper. Unfortunately a couple of the journals we referenced do not provide DOIs (namely AIDS and Antiviral Therapy).

Further, I replaced a citation to a bioRxiv preprint with the recently published version of that manuscript (Rasmussen et al. 2018), and I removed a broken URL associated with Van Laethem et al. (2002).

[pjotrp]

Hi @ArtPoon, can you post the zenodo or figshare doi of the software release here?

[ArtPoon]

I did post the Zenodo DOI in this issue.

[pjotrp]

Ah, sorry. Somehow it did not show.

[pjotrp]

@whedon set 10.5281/zenodo.2548745 as archive

[whedon]

OK. 10.5281/zenodo.2548745 is the archive.

[pjotrp]

@whedon accept

[whedon]

Attempting dry run of processing paper acceptance...

[whedon]

Check final proof 👉 openjournals/joss-papers#455

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

@whedon accept deposit=true

[pjotrp]

@arfon I think we are ready!

[arfon]

@whedon accept deposit=true

[whedon]

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

[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.01186 joss-papers#456
1. Wait a couple of minutes to verify that the paper DOI resolves https://doi.org/10.21105/joss.01186
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]

@azneto - many thanks for your review and to @pjotrp for editing this submission ✨

@ArtPoon - your paper is now accepted into 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](http://joss.theoj.org/papers/10.21105/joss.01186/status.svg)](https://doi.org/10.21105/joss.01186)

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

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

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: http://joss.theoj.org/reviewer-signup.html
• Making a small donation to support our running costs here: https://www.flipcause.com/secure/cause_pdetails/Mjk3Nzk=

[ArtPoon]

Thanks @azneto for your review and @pjotrp for handling the process!
This has been a fascinating experience 😀