-
-
Notifications
You must be signed in to change notification settings - Fork 40
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]: Zoobot: Adaptable Deep Learning Models for Galaxy Morphology #5241
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 |
|
@mwalmsley — Thanks for your submission! It looks like there's a syntax error in the author list of your manuscript. The affiliation for the author "Crisel Suárez" should be a single quoted string, not an array! |
@editorialbot generate pdf |
Hi @dfm, apologies for that - typo has been fixed and paper generates correctly. |
@editorialbot check references |
|
@editorialbot query scope @mwalmsley — I'm going to flag this submission for editorial review so that the editorial board can weigh in on the scope, since we explicitly don't publish pre-trained ML models in JOSS. This process normally takes about a week, and I'll keep you posted. I understand that |
Submission flagged for editorial review. |
@dfm thank you for the explanation and for your time considering this submission. I would phrase Zoobot as a package for finetuning (and creating from scratch) deep learning galaxy morphology models, which naturally includes many pretrained models, rather than e.g. a list of pretrained models. I haven't published in JOSS before but my understanding is that code which extracts knowledge from large datasets is in-scope. I would argue that Zoobot meets this bar. It has already been used to measure galaxy morphology in several published works (including the largest detailed morphology catalog to-date) and runs server-side at the Zooniverse selecting which galaxies Galaxy Zoo volunteers should be shown. Zoobot includes all the code needed for training morphology models from scratch. This is how Galaxy Zoo uses it and this makes up a substantial portion of the code (see e.g. this user-facing function). Training these models required some significant research progress to e.g. handle the Galaxy Zoo decision tree labels as well as a substantial software engineering effort. Zoobot is our effort to package this work and extend it for future Galaxy Zoo projects (including for Euclid, for which Zoobot is part of the official software pipeline) and indeed any project using a decision tree-esque structure. Further, Zoobot includes extensive code for finetuning these models. User feedback over the beta made it clear that most external users are primarily interested in finetuning the models to their own data. We therefore refocused the API and docs on finetuning. See e.g. the finetuning API, the finetuning guides, and the finetuning and representations examples. I hope that making finetuning straightforward for astronomers without ML backgrounds will be helpful for our field. I appreciate that if Zoobot was simply, say, a Dropbox folder full of pretrained models (which of course we do include), that would clearly not be a meaningful software package and not be appropriate for JOSS. I do not think that would be an accurate characterization of Zoobot and I am more than happy to discuss this further with the Board. |
Thanks @mwalmsley! The editorial team agrees that this submission is within scope and I'm now looking for an editor to handle the submission. I'll post here as soon as someone is assigned. |
Thanks @dfm, great news to end the week with. |
@editorialbot assign @plaplant as editor |
Assigned! @plaplant is now the editor |
@mwalmsley thanks for your submission to JOSS! I'll be the editor for this submission. I will begin reaching out to potential reviewers. If you have any suggestions for people who might be good fits to review, please let me know! |
Great @plaplant, appreciate you taking the time! Let me know if potential reviewers aren't immediately available and I can suggest some. |
@editorialbot add @crhea93 as reviewer |
@crhea93 added to the reviewers list! |
@editorialbot add @devanshkv as reviewer |
@devanshkv added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #5312. |
Submitting author: @mwalmsley (Mike Walmsley)
Repository: https://github.com/mwalmsley/zoobot
Branch with paper.md (empty if default branch): docs
Version: v1.0.0
Editor: @plaplant
Reviewers: @crhea93, @devanshkv
Managing EiC: Dan Foreman-Mackey
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @mwalmsley. Currently, there isn't a JOSS editor assigned to your paper.
@mwalmsley 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: