Open editorialbot opened 3 days 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
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
✅ OK DOIs
- 10.1109/LGRS.2024.3376992 is OK
- 10.1109/36.964973 is OK
- 10.1109/36.898661 is OK
- 10.1088/0266-5611/14/4/001 is OK
- 10.1201/9781420054989 is OK
- 10.48550/arXiv.2006.12485 is OK
- 10.1109/MGRS.2020.3046356 is OK
- 10.1109/TGRS.2004.828196 is OK
- 10.1109/TGRS.2024.3419083 is OK
- 10.1109/JSTARS.2022.3180994 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: Synthetic aperture radar
❌ MISSING DOIs
- None
❌ INVALID DOIs
- None
Software report:
github.com/AlDanial/cloc v 1.90 T=0.34 s (658.3 files/s, 381601.2 lines/s)
---------------------------------------------------------------------------------------
Language files blank comment code
---------------------------------------------------------------------------------------
C++ 32 5012 10190 40132
C 22 2460 5027 22001
Python 73 2767 2278 10051
C/C++ Header 34 1325 4135 4386
C Shell 20 824 1737 3655
Bourne Shell 11 612 835 2997
Jupyter Notebook 8 0 5975 743
XML 8 6 3 463
make 4 74 195 311
Markdown 4 48 0 129
TeX 1 6 0 107
Windows Module Definition 1 1 2 52
JSON 1 0 0 39
Bourne Again Shell 1 5 0 38
Dockerfile 1 6 4 27
YAML 1 2 4 18
---------------------------------------------------------------------------------------
SUM: 222 13148 30385 85149
---------------------------------------------------------------------------------------
Commit count by author:
77 Ling Chang
62 espiritocz
45 LC-SAR
16 XuZhangUT
13 Milan Lazecky
6 AlignSAR
2 Anurag
1 Jose Manuel Delgado Blasco
1 unknown
Paper file info:
📄 Wordcount for paper.md
is 1088
✅ The paper includes a Statement of need
section
License info:
✅ License found: Apache License 2.0
(Valid open source OSI approved license)
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
👋🏼 @LC-SAR, @philippemiron, and @shahchiragh 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#REVIEW_NUMBER
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.
We aim for reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period of time.
Please feel free to ping me (@rwegener2) if you have any questions/concerns.
Submitting author: !--author-handle-->@LC-SAR<!--end-author-handle-- (Ling Chang) Repository: https://github.com/AlignSAR/alignSAR Branch with paper.md (empty if default branch): main Version: v1.1 Editor: !--editor-->@rwegener2<!--end-editor-- Reviewers: @philippemiron, @shahchiragh 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
@philippemiron & @shahchiragh, 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 @rwegener2 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 @philippemiron