-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
[PRE REVIEW]: Trash AI: A Web GUI for Serverless Computer Vision Analysis of Images of Trash #5005
Comments
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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Wordcount for |
|
@wincowgerDEV – thanks for your submission to JOSS. Can you help me understand where the code contributions are for this project? It looks to be a Python-based project but I'm trying to understand if significant aspects of the codebase are indeed in TypeScript. Any pointers you could give us here would be very welcome. Also as we're managing a backlog of submissions in this area I think it's appropriate to add the |
Thanks so much for following up on this. No worries at all about
waitlisting. We anticipated that especially with the holidays coming up.
Hope you're able to get some vacation time. I will check in with the JS
team about how much of the JS is written in typescript vs vue and get back
to you. I will also follow up on the aspects listed previously after the
holidays in early January.
…On Wed, Dec 14, 2022, 8:29 AM Arfon Smith ***@***.***> wrote:
@wincowgerDEV <https://github.com/wincowgerDEV> – thanks for your
submission to JOSS. Can you help me understand where the code contributions
are for this project? It looks to be a Python-based project but I'm trying
to understand if significant aspects of the codebase are indeed in
TypeScript.
Any pointers you could give us here would be very welcome. Also as we're
managing a backlog of submissions in this area I think it's appropriate to
add the waitlisted label for now.
—
Reply to this email directly, view it on GitHub
<#5005 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGMUJU2V33NX2CENCXRDLTDWNFZMDANCNFSM6AAAAAAS4OB7K4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@arfon I got confirmation from the JS team that the JS is written in Typescript. They think that a reviewer familiar with JS could review the Typescript without much challenge. |
@editorialbot and @arfon here are some reviewers from the list of potential reviewers I think might be appropriate: Typescript: luxaritas, matthewbeleck, domna Let me know if there is anything else I can do to get us moved from the waitlist to active review. |
I'm sorry human, I don't understand that. You can see what commands I support by typing:
|
@editorialbot commands |
Hello @wincowgerDEV, here are the things you can ask me to do:
|
updated DOIs code4sac/trash-ai@52380b0 |
@editorialbot generate my checklist |
Checklists can only be created once the review has started in the review issue |
@editorialbot assign me as editor |
Assigned! @arfon is now the editor |
@wincowgerDEV – apologies for the delay here. I'm still struggling to understand exactly what this submission is composed of. It looks to be:
Is that about right? If so, I'm not sure this is eligible for review in JOSS as we don't review ML models here and generally review underlying libraries/codebases that are designed for maintainable extension rather than user-interfaces driving them (which is where the majority of the code in this submission seems to be focused). To be clear, I'm not entirely convicted about my feedback here but as I conduct my initial assessment here this is where my head is at. |
@arfon
Thanks for getting back to me and no worries about the delay. You are
correct with your three points about the major aspects of our software. I
will add though that the UI and backend itself is a substantial codebase
development, the deployment code is too but is a smaller component of this
work and we are asking for review of those, not the ML model. The reason I
decided to submit this software to JOSS was inspired by a review I did for
JOSS. You can see the review here:
#4038
The software was very similar to ours in that it primarily made adoption of
ML and AI by linking existing UI packages together in a new and useful way
that advances AI and ML practitioners ability to conduct their science.
Doing computer vision without the aid of UIs is extremely challenging so I
anticipate this area of statistics will need many open source UI software
packages to move forward.
How I understood the maintainable extension requirement during that review
was that the code needed to demonstrate enough uniqueness to stand alone
and that their needed to be clear enough guidance to promote contribution
and maintenance by others in the future. Our software has these features.
There are clear contribution guidelines in the repo and a team composed of
software developers around the USA affiliated with the volunteer group Code
for America developed the code with many hundreds of hours of effort.
Happy to continue the conversation and appreciate you willingness to
discuss.
Warm Regards,
Win
…On Sun, Jan 22, 2023, 12:49 AM Arfon Smith ***@***.***> wrote:
@wincowgerDEV <https://github.com/wincowgerDEV> – apologies for the delay
here. I'm still struggling to understand exactly what this submission is
composed of. It looks to be:
- Some kind of pre-trained ML model for detecting items of trash in
images.
- A web-ui for driving the model (on serverless compute)
- Some code for deploying the infrastructure
Is that about right? If so, I'm not sure this is eligible for review in
JOSS as we don't review ML models here and generally review underlying
libraries/codebases that are designed for maintainable extension
<https://joss.readthedocs.io/en/latest/submitting.html#substantial-scholarly-effort>
rather than user-interfaces driving them (which is where the majority of
the code in this submission seems to be focused).
To be clear, I'm not entirely convicted about my feedback here but as I
conduct my initial assessment here this is where my head is at.
—
Reply to this email directly, view it on GitHub
<#5005 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGMUJUZXRHE4S3FXSCEM4DTWTTYAHANCNFSM6AAAAAAS4OB7K4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@luxaritas, @domna, @a2un, @MikeHughesKent 👋 would any of you be willing to review this submission for JOSS? The submission under consideration is Trash AI: A Web GUI for Serverless Computer Vision Analysis of Images of Trash The review process at JOSS is unique: it takes place in a GitHub issue, is open, and author-reviewer-editor conversations are encouraged. You can learn more about the process in these guidelines: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html Based on your experience, we think you might be able to provide a great review of this submission. Please let me know if you think you can help us out! Many thanks |
Hi @arfon , I would be happy to review the paper. It would be my first review for JOSS. Judging from the reviewer guidelines I feel confident to deliver a good review for the paper. It may just take a little longer since it's my first time and I just need to adapt to the processes. |
Would also be a new reviewer, but I'm up for reviewing. |
Awesome stuff, thank you both! I'll add you both now and get the review started. |
@editorialbot add @domna as reviewer |
@domna added to the reviewers list! |
@editorialbot add @luxaritas as reviewer |
@luxaritas added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #5136. |
Thanks again @domna & @luxaritas – see you over in #5136 where the actual review will take place. |
Submitting author: @wincowgerDEV (Win Cowger)
Repository: https://github.com/code4sac/trash-ai
Branch with paper.md (empty if default branch):
Version: 1.0
Editor: @arfon
Reviewers: @domna, @luxaritas
Managing EiC: Arfon Smith
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @wincowgerDEV. Currently, there isn't a JOSS editor assigned to your paper.
@wincowgerDEV if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).
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:
The text was updated successfully, but these errors were encountered: