Skip to content
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]: remotePARTS: Spatiotemporal autoregression analyses for large data sets #7937

Open
editorialbot opened this issue Mar 21, 2025 · 7 comments
Assignees
Labels

Comments

@editorialbot
Copy link
Collaborator

Submitting author: @morrowcj (Clay J. Morrow)
Repository: https://github.com/morrowcj/remotePARTS
Branch with paper.md (empty if default branch): joss_submission
Version: v1.0.4.2
Editor: @jGaboardi
Reviewers: @iosefa, @karlosmantilla
Archive: Pending

Status

status

Status badge code:

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

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

@iosefa & @karlosmantilla, 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 @jGaboardi 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

@iosefa, please create your checklist typing: @editorialbot generate my checklist

@karlosmantilla, please create your checklist typing: @editorialbot generate my checklist

@editorialbot
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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

✅ OK DOIs

- 10.1016/j.rse.2021.112678 is OK
- 10.1016/j.mex.2022.101660 is OK
- doi/10.1111/gcb.16800 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Alaska: NDVI analysis with remotePARTS

❌ MISSING DOIs

- 10.32614/cran.package.remoteparts may be a valid DOI for title: remotePARTS: Spatiotemporal autoregression analyse...

❌ INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.98  T=1.00 s (65.7 files/s, 394198.4 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
CSV                              4              0              0         384730
HTML                             3            207             40           2286
R                               36            376           2576           2094
Markdown                         8            209              6            737
C++                              6             68            273            472
Rmd                              3            342            910            200
YAML                             3             27              8            136
TeX                              1              5              0             49
C/C++ Header                     2             13             12             37
-------------------------------------------------------------------------------
SUM:                            66           1247           3825         390741
-------------------------------------------------------------------------------

Commit count by author:

   336	Clay Morrow
    19	Anthony R. Ives
    13	morrowcj
     2	Anthony R. ives
     1	=

@editorialbot
Copy link
Collaborator Author

Paper file info:

📄 Wordcount for paper.md is 375

✅ The paper includes a Statement of need section

@editorialbot
Copy link
Collaborator Author

License info:

🟡 License found: GNU General Public License v3.0 (Check here for OSI approval)

@editorialbot
Copy link
Collaborator Author

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

@jGaboardi
Copy link

Let me know if you have any questions!

👋🏼 @iosefa, @karlosmantilla – 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#7937, 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.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants