[REVIEW]: LightLogR: Reproducible analysis of personal light exposure data

[editorialbot]

Submitting author: @JZauner (Johannes Zauner)
Repository: https://github.com/tscnlab/LightLogR
Branch with paper.md (empty if default branch): paper
Version: v0.4.1
Editor: @rwegener2
Reviewers: @cansavvy, @welch16
Archive: Pending

Status

Status badge code:

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

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

@cansavvy & @welch16, 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 @rwegener2 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 @welch16

📝 Checklist for @cansavvy

[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.90  T=0.06 s (1592.1 files/s, 367204.7 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
CSV                              2              0              0          11432
R                               81            776           3413           5183
Markdown                        10            245              0            642
Rmd                              5            472            619            579
YAML                             4             22              9            184
TeX                              1             17              0            163
-------------------------------------------------------------------------------
SUM:                           103           1532           4041          18183
-------------------------------------------------------------------------------

Commit count by author:

   121	Johannes Zauner
    71	Jzauner
    22	Manuel Spitschan
    22	steffenhartmeyer
     3	Steffen Hartmeyer
     2	JZauner

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 1503

✅ The paper includes a Statement of need section

[editorialbot]

License info:

🟡 License found: Other (Check here for OSI approval)

[editorialbot]

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

✅ OK DOIs

- 10.1111/jsr.14225 is OK
- 10.1177/14771535241248540 is OK
- 10.1101/2024.02.11.24302663 is OK
- 10.1177/14771535221103258 is OK
- 10.1101/2024.10.02.616112 is OK
- 10.1123/jmpb.2018-0063 is OK
- 10.12688/wellcomeopenres.20557.1 is OK
- 10.1177/20552076221144858 is OK
- 10.20944/preprints202409.1285.v1 is OK
- 10.1016/j.measurement.2024.114909 is OK
- 10.1038/sdata.2016.18 is OK
- 10.21203/rs.3.rs-3771881/v1 is OK
- 10.5281/zenodo.13839724 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: LightLogR: Process Data from Wearable Light Logger...
- No DOI given, and none found for title: LightLogR: Process Data from Wearable Light Logger...
- No DOI given, and none found for title: LightLogR: Process Data from Wearable Light Logger...
- No DOI given, and none found for title: LightLogR: Tutorial: The whole game
- No DOI given, and none found for title: ggplot2: Elegant Graphics for Data Analysis

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

[rwegener2]

👋🏼 @JZauner @cansavvy, @welch16 this is the review thread for the paper. All of our communications will happen here from now on.

As a reviewer, the first step is to create a checklist for your review by entering

@editorialbot generate my checklist

as the top of a new comment in this thread.

These checklists contain the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. The first comment in this thread also contains 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 openjournals/joss-reviews#REVIEW_NUMBER 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 reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period of time.

Please feel free to ping me (@rwegener2) if you have any questions/concerns.

[editorialbot]

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

[welch16]

Review checklist for @welch16

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/tscnlab/LightLogR?
• 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 (@JZauner) 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?

[cansavvy]

Review checklist for @cansavvy

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/tscnlab/LightLogR?
• 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 (@JZauner) 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?

[cansavvy]

@JZauner This is a very cool software! I really appreciate the thoroughness here. Enjoyed taking a look at the code base and paper! I don't work with light loggers so the application is not something I have experience with but can certainly understand the need and appreciate software that attempts to standardize data!

So only have the minorest of comments and questions here:

• Your tutorial articles are great! Very nice. So often I see developers not put much care into those even though that's what really increases your usability.
• There doesn't appear to be a contributing guide or information for contributors anywhere. I think GitHub has a template one you can borrow and adjust if you go to Settings > Community Standards and click the add button next to "CONTRIBUTING.md"
• I ran through the steps in order on the README and many of the steps worked quite seamlessly! But it did tell me LLdata was not found and it was unclear in the code where that should be pulled from?
• One of your sentences in the summary in the paper was a very long and a bit hard to keep track of so breaking that up into two might be helpful.