Open editorialbot opened 1 month 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.13 s (384.7 files/s, 719299.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 23 712 808 1605
Jupyter Notebook 6 0 86320 905
Markdown 13 243 0 478
TOML 1 35 12 188
TeX 1 13 0 170
YAML 4 4 2 92
JSON 1 0 0 23
-------------------------------------------------------------------------------
SUM: 49 1007 87142 3461
-------------------------------------------------------------------------------
Commit count by author:
62 Farthofer Laurenz (KAI DSC)
4 Laurenz Farthofer
1 Hundgeburth Laurenz (KAI DSC)
1 Laurenz
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
✅ OK DOIs
- 10.48550/arXiv.2010.15277 is OK
- 10.1109/TKDE.2018.2876857 is OK
- 10.48550/arXiv.2106.02585 is OK
- 10.3389/frai.2022.829842 is OK
- 10.1109/TSM.2014.2364237 is OK
- 10.48550/arXiv.2403.05175 is OK
- 10.1109/CVPRW53098.2021.00399 is OK
- 10.48550/arXiv.2102.06253 is OK
- 10.48550/arXiv.1903.12261 is OK
- 10.1002/1097-024X(200009)30:11<1203::AID-SPE338>3.0.CO;2-N is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: PyTorch: An Imperative Style, High-Performance Dee...
- No DOI given, and none found for title: TorchVision: PyTorch’s Computer Vision library
- No DOI given, and none found for title: anytree: Python tree data library
❌ MISSING DOIs
- None
❌ INVALID DOIs
- None
Paper file info:
📄 Wordcount for paper.md
is 1194
✅ The paper includes a Statement of need
section
License info:
✅ License found: MIT License
(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:
@firefly-cpp @hoanganhngo610 Thanks for agreeing to review this submission! This is the review thread for the paper. All of our communications will happen here from now on. :+1:
As you can see above, you each should use the command @editorialbot generate my checklist
to create your review checklist. @editorialbot commands need to be the first thing in a new comment.
As you go over the submission, please check any items that you feel have been satisfied (and if you leave notes on each item that's even better). There are also links to the JOSS reviewer guidelines. I find it particularly helpful to also use the JOSS review criteria and review checklist docs as supplement/guides to the reviewer checklist @editorialbot will make for you.
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, reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#7206
so that a link is created to this Issue 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 4 weeks. Please let me know if either of you require some more time (that's perfectly okay). We can also use @editorialbot to set automatic reminders if you know you'll be away for a known period of time.
Please feel free to ping me (@matthewfeickert) if you have any questions/concerns.
As all reviewers have their checklist generated now I'll have @editorialbot give us reminders in 3 weeks to follow up on the initial state of the review.
@editorialbot remind @firefly-cpp in 3 weeks
Reminder set for @firefly-cpp in 3 weeks
@editorialbot remind @hoanganhngo610 in 3 weeks
Reminder set for @hoanganhngo610 in 3 weeks
:wave: @firefly-cpp, please update us on how your review is going (this is an automated reminder).
:wave: @hoanganhngo610, please update us on how your review is going (this is an automated reminder).
@firefly-cpp @hoanganhngo610, can you please give us an update on the status of your reviews? I see that there are some Issues being opened (and closed :+1:) on https://github.com/Infineon/StreamGen/ which is good.
@matthewfeickert I am still on the way of finishing the checklist along with some additional comments, and all should be finished by the end of next week at the latest!
@matthewfeickert, Thanks for reminding me. I really hope to finish my review by the end of this week.
(I was offline for a few days, so responding now.)
Thanks @firefly-cpp and @hoanganhngo610. The timelines sound good, but as there might be some back and forth needed in discussions I'll set reminders for 2 weeks from now. :+1:
@editorialbot remind @hoanganhngo610 in 2 weeks
Reminder set for @hoanganhngo610 in 2 weeks
@editorialbot remind @firefly-cpp in 2 weeks
Reminder set for @firefly-cpp in 2 weeks
:wave: @hoanganhngo610, please update us on how your review is going (this is an automated reminder).
:wave: @firefly-cpp, please update us on how your review is going (this is an automated reminder).
Submitting author: !--author-handle-->@laurenzbeck<!--end-author-handle-- (Laurenz Farthofer) Repository: https://github.com/Infineon/StreamGen Branch with paper.md (empty if default branch): Version: v1.0.2 Editor: !--editor-->@matthewfeickert<!--end-editor-- Reviewers: @firefly-cpp, @hoanganhngo610 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
@firefly-cpp & @hoanganhngo610, 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 @matthewfeickert 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 @firefly-cpp
📝 Checklist for @hoanganhngo610