-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: Walkboutr: Extracting Walk Bouts from GPS and Accelerometry Data for Physical Activity Research #7649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello human, 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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for 🔴 Failed to discover a |
License info: 🟡 License found: |
Five most similar historical JOSS papers: activAnalyzer: An R Shiny app to analyse ActiGraph accelerometer data and to implement the use of the PROactive Physical Activity in COPD instruments mhealthtools: A Modular R Package for Extracting Features from Mobile and Wearable Sensor Data Sit2StandPy: An Open-Source Python Package for Detecting and Quantifying Sit-to-Stand Transitions Using an Accelerometer on the Lower Back SleepPy: A python package for sleep analysis from accelerometer data Beiwe: A data collection platform for high-throughput digital phenotyping |
Hello! I think Pierre-Yves de Müllenheim and Phil Snyder would be good fits for reviewers. |
Added a statement of need section. @Kevin-Mattheus-Moerman @editorialbot can you advice on how to move forward? |
@editorialbot check repository |
Software report:
Commit count by author:
|
Paper file info: 🚨 Wordcount for ✅ The paper includes a |
License info: 🟡 License found: |
@editorialbot generate pdf |
@laurenwilner thanks for making those changes. I see you use a BSD-3 clause license. It seems both our system and GitHub do not recognise it. Can you check if your license text exactly confirms to the official text: https://opensource.org/license/bsd-3-clause? |
@laurenwilner I've just flagged this submission for scope review so the editorial board can help check if this work is in scope and conforms to our substantial scholarly effort criterion. This scope review should take about 2 weeks to complete. |
confirming that the text matches the official text @Kevin-Mattheus-Moerman |
Thank you for flagging for scope review -- we look forward to hearing from you! |
@Kevin-Mattheus-Moerman @laurenwilner – assuming this submission makes it through scope review, this paper looks very very long. @laurenwilner – our guideline is ~1000 words. |
Hello! Thanks for flagging. Is there any update on the scope review? |
@laurenwilner - thanks for your submission to JOSS. Unfortunately, after review by the JOSS editorial team we've determined that this submission doesn't meet our substantial scholarly effort criterion. One possible alternative to JOSS is to follow GitHub's guide on how to create a permanent archive and DOI for your software. This DOI can then be used by others to cite your work. |
@editorialbot reject |
Paper rejected. |
Submitting author: @laurenwilner (Lauren Wilner)
Repository: https://github.com/rwalkbout/walkboutr
Branch with paper.md (empty if default branch): paper
Version: v0.6.0
Editor: Pending
Reviewers: Pending
Managing EiC: Kevin M. Moerman
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @laurenwilner. Currently, there isn't a JOSS editor assigned to your paper.
@laurenwilner if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: