Open editorialbot opened 2 weeks ago
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
Software report:
github.com/AlDanial/cloc v 1.90 T=0.12 s (995.4 files/s, 147075.2 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 97 2563 3218 7056
XML 9 3 18 2482
Markdown 3 147 0 542
Cython 1 179 286 422
TeX 1 22 0 228
reStructuredText 2 59 77 31
YAML 1 4 2 28
DOS Batch 1 8 1 26
make 1 4 7 9
Dockerfile 1 2 3 5
TOML 1 0 0 3
-------------------------------------------------------------------------------
SUM: 118 2991 3612 10832
-------------------------------------------------------------------------------
Commit count by author:
663 Alexander Fabisch
17 jklemm
3 Marc Otto
2 wood
1 Baptiste Busch
1 Enrico Eberhard
1 mulo01
Paper file info:
π Wordcount for paper.md
is 2195
β
The paper includes a Statement of need
section
License info:
π‘ License found: Other
(Check here for OSI approval)
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1109/ROBOT.2002.1014739 is OK
- 10.1109/ROBOT.2009.5152385 is OK
- 10.1162/NECO_a_00393 is OK
- 10.1177/0278364912472380 is OK
- 10.1109/IROS.2013.6697172 is OK
- 10.1109/ICRA.2014.6907291 is OK
- 10.1007/s10514-016-9556-2 is OK
- 10.1007/s10514-017-9648-7 is OK
- 10.21105/joss.01159 is OK
- 10.1177/02783649231201196 is OK
- 10.21105/joss.01225 is OK
- 10.1177/1729881420913741 is OK
- 10.21105/joss.03054 is OK
- 10.1016/j.robot.2021.103779 is OK
- 10.26092/elib/1547 is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.1109/ICRA46639.2022.9811843 is OK
- 10.1109/MCSE.2010.118 is OK
MISSING DOIs
- No DOI given, and none found for title: Active Contextual Policy Search
- No DOI given, and none found for title: Probabilistic Movement Primitives
- No DOI given, and none found for title: Open3D: A Modern Library for 3D Data Processing
- No DOI given, and none found for title: PyBullet, a Python module for physics simulation f...
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@gautam-sharma1 and @ishaanamahajan - Dear reviewers, you can start your review by creating your tasklist with the following command:
@editorialbot generate my checklist
In that list, there are several tasks. Whenever you perform a task, you can check on the corresponding checkbox. You can also reference the JOSS reviewer guidelines which is linked in first comment in this thread. Since the review process of JOSS is interactive, you can always interact with the author, the other reviewers, and the editor during the process. You can open issues and pull requests in the target repo. Please mention the url of this page in there so that we can keep tracking what is going on.
Thank you in advance.
Created an issue related to test (https://github.com/dfki-ric/movement_primitives/issues/42), author resolved it, so marking tests as complete.
@ishaanamahajan let me know if you are able to get started on this soon. Thanks!
@ishaanamahajan let me know if you are able to get started on this soon. Thanks!
I will be able to get started on it this weekend, hope that is fine.
@ishaanamahajan great thanks for the update!
Hi, just checking in to see if there are any updates on the review status. Let me know if I can be of any help.
Submitting author: !--author-handle-->@AlexanderFabisch<!--end-author-handle-- (Alexander Fabisch) Repository: https://github.com/dfki-ric/movement_primitives/ Branch with paper.md (empty if default branch): joss Version: 0.7.0 Editor: !--editor-->@ymzayek<!--end-editor-- Reviewers: @ishaanamahajan, @gautam-sharma1 Archive: Pending
Status
Status badge code:
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
@ishaanamahajan & @gautam-sharma1, 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:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @ymzayek 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 @gautam-sharma1
π Checklist for @ishaanamahajan