Closed editorialbot closed 1 week ago
Hello human, 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.11 s (1098.7 files/s, 262104.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
JSON 3 0 0 18576
JSX 42 328 49 5060
JavaScript 55 248 106 2918
Python 5 177 90 653
Markdown 4 144 0 491
YAML 4 14 4 87
TeX 1 7 0 70
Dockerfile 2 13 0 17
HTML 1 3 21 17
CSS 1 1 0 6
CSV 4 0 0 4
-------------------------------------------------------------------------------
SUM: 122 935 270 27899
-------------------------------------------------------------------------------
Commit count by author:
192 seveibar
88 sumn2u
71 Severin Ibarluzea
47 semantic-release-bot
13 Oleh Yasenytsky
7 Henry LIANG
7 Tamay Eser Uysal
6 Emiliano Castellano
5 sreevardhanreddi
4 Suman Kunwar
3 Mews
3 Mykyta Holubakha
3 OmG2011
2 Josep de Cid
2 Katsuhisa Yuasa
2 Mohammed Eldadah
2 linyers
1 HoangHN
1 Hummer12007
1 Joey Figaro
1 Puskuruk
1 Shahidul Islam Majumder
1 ThibautGeriz
1 beru
1 harith-hacky03
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1145/3343031.3350535 is OK
- 10.5281/ZENODO.11543564 is OK
- 10.1109/I2C2.2017.8321819 is OK
- 10.1007/s11042-022-12100-1 is OK
- 10.48550/ARXIV.2401.01454 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Paper file info:
📄 Wordcount for paper.md
is 964
✅ 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:
:wave: @sumn2u - thank you for your submission to JOSS! I have a few clarifying questions for you:
seveibar
). Could you explain why they are not listed as co-authors? Sure @crvernon
- I notice that you are the sole lead author on this work. However, many others have made commits to this repository (e.g.,
seveibar
). Could you explain why they are not listed as co-authors?
This work is a fork, so commits from the parent repository are also present here. I have acknowledged and given credit to these contributors in the acknowledgment section.
- I know that you have made many commits since forking this work, but could you explain the relationship between your product and the parent repository?
The parent repository is a toolkit/library that enables users to create annotations. My product uses this toolkit, in addition to other libraries, to create annotations, store their behavior, and provide additional functions like masking annotated images, saving configurations, and more. Furthermore, the parent toolkit lacked test cases, but these have now been added. The parent toolkit has been updated to incorporate these changes, address bugs, and introduce new features.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot query scope
Thanks for the clarification @sumn2u! I am going to get the larger editorial board to take a look as well to ensure this submission qualifies under our submission requirements. This process usually takes about 2 weeks to do and I will notify you of the decision as soon as possible.
Submission flagged for editorial review.
Thanks, @crvernon. If there's any further work needed from my side, please let me know. I'll be happy to take care of it.
@sumn2u we are in discussion with the larger editorial board about your submission and it would help us a bit if we could get a detailed list of your additions to this project (not the commit log, but the list of contributions in terms of new features that have been implemented). Could you post that here? Thanks!
Sure @crvernon . The features implemented in this project represent a significant contribution, enhancing functionality, usability, and scalability. The key features include:
Configuration Screen: This screen allows users to configure tools, tags, and upload images for annotation. For more details, please refer to Configuration Setup.
File List Management: Based on the uploaded images, a comprehensive file list is provided. Users can navigate through this list and perform annotation operations efficiently.
Circular Selection Tool: A new tool for annotating circular or oval regions of interest has been added, expanding the annotation capabilities.
Server Integration: A dedicated server has been introduced to store annotated information in CSV format, ensuring data persistence and easy retrieval.
Masked Image Download: Users can now mask annotated images and download them, enhancing data privacy and usability.
Annotated Image and Settings Download: This feature allows users to download the annotated images along with their settings, facilitating their use in machine learning applications.
Client-Server Separation: The client and server sides have been separated to improve scalability and manage complex logic effectively. This also includes the implementation of comprehensive test cases.
Intuitive Design and Bug Fixes: The interface design has been made more intuitive, and several bugs have been fixed to enhance user experience.
Comprehensive Documentation: Detailed documentation has been created, guiding users on how to utilize and run the application efficiently.
Thanks @sumn2u and how long have you been contributing to this project. I see your earliest commit about 20 days ago is that correct?
Thanks @sumn2u and how long have you been contributing to this project. I see your earliest commit about 20 days ago is that correct?
@crvernon I've been working on it for a while, maybe more than 2 and a half months, but on the forked version, yes, it's been 20 days.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot reject
:wave: @sumn2u. - Thanks for your patience during our larger editorial board review. At this time we have to reject your submission based on the following findings of the editorial board:
We do think you have done good work here and we wish you the best in continuing the growth of your software.
Paper rejected.
Thanks @crvernon for the updates. I understand the points about the changes being UI-focused and the short commit history. I'll continue to develop the software to better meet the criteria and resubmit in the future.
Submitting author: !--author-handle-->@sumn2u<!--end-author-handle-- (Suman Kunwar) Repository: https://github.com/sumn2u/annotate-lab Branch with paper.md (empty if default branch): paper Version: v1.0.0 Editor: Pending Reviewers: Pending Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @sumn2u. Currently, there isn't a JOSS editor assigned to your paper.
@sumn2u if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type: