-
-
Notifications
You must be signed in to change notification settings - Fork 39
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]: lpcde: Estimation and Inference for Local Polynomial Conditional Density Estimators #7241
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: 🔴 Failed to discover a valid open source license |
Review checklist for @salbalkusConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Hi @rajitachandak, I have a few substantive comments on the software that I'd like to post as issues in the GitHub repo, as recommended by JOSS. Would you mind enabling the "Issues" tab on your package's repo so that I can do so? Thanks! |
Hello @salbalkus, I have enabled Issues/Discussions for the repo, you should now be able to add your comments there. Thanks! |
Hi @rajitachandak my first pass is now complete; overall, the paper and the software look great. The remaining unchecked items pertain to some issues that I've filed above; @spholmes I assume I should wait to check these until the issues have been addressed? Thanks! |
Dear @salbalkus, Thank you for your thorough review and feedback of our package and paper. We have addressed each of the issues raised on our repository and provided a note regarding the changes we have made on each issue individually. Just to summarize our revision -- We made all the changes requested. We have added a discussion on the issue regarding implementing the predict method that we hope will help explain our implementation of this request. Please feel free to reach out if you have any questions. |
Hi @rajitachandak, Thank you for the in-depth explanations and attention to detail on this response. All of my previous concerns have been addressed! As noted in JOSS review: Fix license nppackages/lpcde#6 the only remaining issue I see is to change the GPL license GitHub shield and license tabs in the README to be consistent with the MIT license that you have included. Once that is complete, I will recommend the software for publication! |
Dear @salbalkus, Thanks for pointing out that inconsistency! I have update all license files in our repository to GPL >=3.0. The changes will reflect on CRAN shortly. |
Hi @rajitachandak, Thanks again for the update. It looks like I'm still seeing an MIT license in the README.md file located in the top level of the repository (the one that displays at this link directly). It is located in the section titled "License", just after the "References" section that cites your papers. Since the GPL license is included in a separate file elsewhere it may be best to just remove this section of the top level README.md. |
Dear @salbalkus, Done, thanks! |
Hi @spholmes, just wanted to let you know I've completed my review! I am recommending to accept. |
Dear @spholmes, I hope you are well. I just wanted to enquire regarding the status of the review process -- do let us know if there's any additional edits or steps you would like us to complete before moving forward with the next steps of the review. Thank you. Best, |
Dear @rajitachandak |
Dear @spholmes, I see. Perhaps you could check with Grant McDermott (https://grantmcdermott.com/) or David Drukker ( https://scholar.google.com/citations?user=ao8I7PcAAAAJ&hl=en), if either of them would be willing to help out. Best, |
Submitting author: @rajitachandak (Rajita Chandak)
Repository: https://github.com/nppackages/lpcde
Branch with paper.md (empty if default branch):
Version: v.0.1.4
Editor: @spholmes
Reviewers: @salbalkus
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
@salbalkus, 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 @spholmes 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 @salbalkus
The text was updated successfully, but these errors were encountered: