-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
[REVIEW]: LiGuard: A GUI-powered Python Framework for Processing Point-Cloud Data #6751
Comments
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:
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 ✅ The paper includes a |
License info: ✅ License found: |
|
Review checklist for @chenzhaiyuConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Review checklist for @tgoellesConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
@chenzhaiyu @tgoelles just a small reminder not to forget this review |
Mine can be found here: m-shahbaz-kharal/LiGuard-JOSS#1 |
I will complete my review by next week. |
I missed this @tgoelles sorry. I think it's better if the review is here but this is fine. I agree with most of @tgoelles points, and while the 2nd reviewer will do his review next week, I am interested in hearing about the main point raised:
Actually, the authors recommend "reject" but this is not really how JOSS proceeds. We aim at bringing the submission to a certain standard that we deem accepted, in this case when all the checklists can be checked. |
The authors present a Python GUI for processing LiDAR data, optionally accompanying imagery. They claim the contribution user-friendly with five sub-modules for IO, configuration, inter-process data sharing, data processing, and visualization. General Concerns
Paper
Documentation
|
Hi, I believe all the reviews are submitted as the assigned reviewers (@chenzhaiyu and @tgoelles) have submitted their responses; please inform me if that is not correct. In the following the response to the reviews is submitted. Dear Reviewers, Thanks for a thorough review. The submitted comments/recommendations/decisions helped us a lot in understanding the process of publication in JOSS more clearly, and more importantly, it has helped us see the potential issues in both the paper and the code/repository. The issues discussed in the reviews primarily included incomprehensive statement-of-need, missing references and comparisons to some similar libraries, broader (than evident) claims, improper tests and documentation, and a lack of enough commit history. Based on the comment from @hugoledoux ("We aim at bringing the submission to a certain standard that we deem accepted, in this case when all the checklists can be checked."), it seems like the submission can be improved and eventually published if it checks all the requirements; please inform us if that is not the case for this submission. While it may take us sometime before all the raised points/concerns are covered/fixed, some quick comments are provided in the following to answer some of those questions.
Summary of Future Updates
Note: The updates will be posted and informed in this thread in the same order as given in Summary of Future Updates above. Please let us know if anything is still missing/unaccounted from our side regarding the review process. Thanks. |
Sorry for taking so long to getting back to this. A few answers and comments:
So I suggest you improve the software, the docs, and the paper. And then you let us know here what changes you've made, and then we can continue the review. How long do you reckon it will take you? |
Submitting author: @m-shahbaz-kharal (Muhammad Shahbaz )
Repository: https://github.com/m-shahbaz-kharal/LiGuard-JOSS
Branch with paper.md (empty if default branch): main
Version: v1.0.0
Editor: @hugoledoux
Reviewers: @chenzhaiyu, @tgoelles
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
@chenzhaiyu & @tgoelles, 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 @hugoledoux 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 @chenzhaiyu
📝 Checklist for @tgoelles
The text was updated successfully, but these errors were encountered: