[REVIEW]: sleev: An R Package for Semiparametric Likelihood Estimation with Errors in Variables

[editorialbot]

Submitting author: @JiangmeiRubyXiong (Jiangmei Xiong)
Repository: https://github.com/dragontaoran/sleev
Branch with paper.md (empty if default branch):
Version: v1.0.3
Editor: @jbytecode
Reviewers: @alemermartinez, @aalfons
Archive: Pending

Status

Status badge code:

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

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

@alemermartinez & @aalfons, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

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

Checklists

📝 Checklist for @aalfons

[editorialbot]

Hello humans, 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:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

[editorialbot]

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

✅ OK DOIs

- 10.1002/sim.8799 is OK
- 10.1111/biom.13512 is OK
- 10.1017/CBO9780511618994 is OK
- 10.1080/01621459.2017.1295864 is OK
- 10.2307/2669386 is OK
- 10.1214/20-aoas1343 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: An empirical study for impacts of measurement erro...

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.90  T=0.03 s (1498.9 files/s, 242374.7 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
R                               30            524           1164           2131
C++                              5            252            360           1379
Markdown                         2             80              0            375
TeX                              1              0              0             71
C/C++ Header                     1             19             67             22
YAML                             1              1              4             19
-------------------------------------------------------------------------------
SUM:                            40            876           1595           3997
-------------------------------------------------------------------------------

Commit count by author:

   112	Joey Sherrill
    26	Sarah Lotspeich
     9	JiangmeiRubyXiong
     5	Sarah
     3	Ran Tao
     3	Sarah Lotspeich (She/Her)
     2	Ruby XIONG
     2	dragontaoran
     1	Shawn Garbett

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 2168

✅ The paper includes a Statement of need section

[editorialbot]

License info:

🟡 License found: GNU General Public License v3.0 (Check here for OSI approval)

[editorialbot]

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

[jbytecode]

@editorialbot remind @aalfons in four weeks

@aalfons - You will get reminded by our bot automatically. As you emphasized in pre-review issue, we expect your report in 8-10 weeks. Thank you in advance

[editorialbot]

Reminder set for @aalfons in four weeks

[jbytecode]

Dear @alemermartinez & @aalfons, you can start your review by generating your tasklist, please just type

@editorialbot generate my checklist

Thank you in advance

[jbytecode]

@editorialbot remind @alemermartinez in 15 days

[editorialbot]

Reminder set for @alemermartinez in 15 days

[aalfons]

Review checklist for @aalfons

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 https://github.com/dragontaoran/sleev?
• License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@JiangmeiRubyXiong) 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
• Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
• Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
• Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

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, who the target audience is, and its relation to other work?
• 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?