[REVIEW]: StreamPoseML: An End-to-End Open-Source Web Application and Python Toolkit for Real-Time Video Pose Classification and Machine Learning

[editorialbot]

Submitting author: @mirlikecoding (N Green)
Repository: https://github.com/mrilikecoding/StreamPoseML
Branch with paper.md (empty if default branch):
Version: v0.1.3
Editor: @arfon
Reviewers: @thejasvibr, @imcatta
Archive: Pending

Status

Status badge code:

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

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

@thejasvibr & @imcatta, 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 @arfon 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 @imcatta

📝 Checklist for @thejasvibr

[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]

Software report:

github.com/AlDanial/cloc v 1.88  T=2.32 s (342.0 files/s, 343159.8 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
JSON                           699              0              0         782901
Python                          59            877           1745           3962
Jupyter Notebook                 6              0           5055           1480
JavaScript                       9             57             52            373
Markdown                         5            162              0            326
YAML                             4             18             65            112
Bourne Shell                     4             25             17             90
CSS                              2             12              0             89
TeX                              1              0              0             79
TOML                             1              3              0             24
HTML                             1              3             20             20
Dockerfile                       2              8              2             18
INI                              1              0              0              2
SVG                              1              0              0              1
-------------------------------------------------------------------------------
SUM:                           795           1165           6956         789477
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

[editorialbot]

Wordcount for paper.md is 1181

[editorialbot]

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

OK DOIs

- None

MISSING DOIs

- 10.1109/anziis.1994.396988 may be a valid DOI for title: Weka: A machine learning workbench
- 10.32614/rj-2009-016 may be a valid DOI for title: Rattle: a data mining GUI for R
- 10.1038/nmeth.2019 may be a valid DOI for title: Fiji: an open-source platform for biological-image analysis
- 10.1093/bioinformatics/btt080 may be a valid DOI for title: eMZed: an open source framework in Python for rapid and interactive development of LC/MS data analysis workflows
- 10.1109/icfhr-2018.2018.00080 may be a valid DOI for title: Deepdiva: a highly-functional python framework for reproducible experiments
- 10.3390/s21113691 may be a valid DOI for title: End-to-end computer vision framework: An open-source platform for research and education

INVALID DOIs

- None

[arfon]

@thejasvibr, @imcatta – This is the review thread for the paper. All of our communications will happen here from now on.

Please read the "Reviewer instructions & questions" in the first comment above. Please create your checklist typing:

@editorialbot generate my checklist

As you go over the submission, please check any items that you feel have been satisfied. There are also links to the JOSS reviewer guidelines.

The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention https://github.com/openjournals/joss-reviews/issues/6392 so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.

We aim for the review process to be completed within about 4-6 weeks but please make a start well ahead of this as JOSS reviews are by their nature iterative and any early feedback you may be able to provide to the author will be very helpful in meeting this schedule.

[editorialbot]

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

[imcatta]

Review checklist for @imcatta

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/mrilikecoding/StreamPoseML?
• 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 (@mirlikecoding) 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?

[thejasvibr]

Review checklist for @thejasvibr

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/mrilikecoding/StreamPoseML?
• 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 (@mirlikecoding) 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?

[thejasvibr]

Hi @arfon I ended being double-booked, by saying yes to two submissions in the pre-review phase and being finalised as a reviewer almost at the same time. Would already like to request some more time for this review (i.e. won't be able to make it in 2-4 weeks).

[arfon]

Hi @arfon I ended being double-booked, by saying yes to two submissions in the pre-review phase and being finalised as a reviewer almost at the same time. Would already like to request some more time for this review (i.e. won't be able to make it in 2-4 weeks).

No problem at all, and thanks for being a willing JOSS reviewer! What about trying to get your review in by mid-late April?

[thejasvibr]

Hi @arfon I ended being double-booked, by saying yes to two submissions in the pre-review phase and being finalised as a reviewer almost at the same time. Would already like to request some more time for this review (i.e. won't be able to make it in 2-4 weeks).

No problem at all, and thanks for being a willing JOSS reviewer! What about trying to get your review in by mid-late April?

Hi @arfon , yes. Mid-late April sounds doable. Was out of action due to illness, and am getting back to shape.

[arfon]

👋 @thejasvibr, @imcatta – it looks like there has been progress by both of you on your reviews, but neither look to be complete. Could you please provide an update on your current status and when you think you will be able to complete your reviews by? Many thanks!

[arfon]

👋 @thejasvibr, @imcatta – it looks like there has been progress by both of you on your reviews, but neither look to be complete. Could you please provide an update on your current status and when you think you will be able to complete your reviews by? Many thanks!

Just bumping again here. Please give us an update here soon please @thejasvibr & @imcatta