Skip to content

[PRE REVIEW]: GAMA: Genetic Automated Machine learning Assistant #1088

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

Closed
whedon opened this issue Nov 20, 2018 · 23 comments
Closed

[PRE REVIEW]: GAMA: Genetic Automated Machine learning Assistant #1088

whedon opened this issue Nov 20, 2018 · 23 comments

Comments

@whedon
Copy link

whedon commented Nov 20, 2018

Submitting author: @PGijsbers (Pieter Gijsbers)
Repository: https://github.com/PGijsbers/GAMA
Version: v0.1.0
Editor: @arokem
Reviewers: @jsgalan

Author instructions

Thanks for submitting your paper to JOSS @PGijsbers. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.

@PGijsbers if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.

Editor instructions

The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:

@whedon commands
@whedon
Copy link
Author

whedon commented Nov 20, 2018

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@whedon commands

@whedon
Copy link
Author

whedon commented Nov 20, 2018

Attempting PDF compilation. Reticulating splines etc...

@whedon
Copy link
Author

whedon commented Nov 20, 2018

@PGijsbers
Copy link

I don't know which reviewers to ask. Anyone comfortable with Python and Machine Learning will probably do the trick, but there are quite a few of those. There is no one in specific that I would like as reviewer.

@labarba
Copy link
Member

labarba commented Nov 22, 2018

@whedon assign @arokem as editor

@whedon
Copy link
Author

whedon commented Nov 22, 2018

OK, the editor is @arokem

@labarba
Copy link
Member

labarba commented Nov 22, 2018

@arokem : This is an obvious submission for you to handle, and it should be easy to find reviewers. For example, @rhiever 👋 …would be ideal to review this, if available & willing. If not, he may be able to help us identify a couple of reviewers.

@rhiever
Copy link

rhiever commented Nov 28, 2018

I'd love to, but I haven't had much extra time for reviewing lately. Maybe @mfeurer? @ledell or someone on the H2O dev team? @weixuanfu?

@weixuanfu
Copy link

I think it is a very interesting tool and I believe @PGijsbers did very good jobs related to autoML, but I didn't have much time for reviewing neither.

@arokem
Copy link

arokem commented Nov 29, 2018

Yep. Thanks for assigning me. Will take a look.

@arokem
Copy link

arokem commented Nov 29, 2018

@fmohr : would you like to review this article for The Journal of Open Source Software?

@mfeurer
Copy link

mfeurer commented Nov 30, 2018

Thanks for suggesting me @rhiever, but I don't feel comfortable reviewing a paper of a collaborator.

@fmohr
Copy link

fmohr commented Nov 30, 2018

Hey, thanks for asking @arokem. In general, I am open to review for JOSS. In this particular case, however, I'm afraid I can't help out; I'm a Java guy and not at all an expert for Python. I don't know to which degree this is a problem, but Pieter mentions this as one of two criterions, so probably speaking Python should be a criterion.

@PGijsbers
Copy link

I have to admit I'm not intimately familiar with the level of code inspection that is done in the JOSS review process. I listed Python as required since the package is written entirely in Python, I figured it would make sense to look for people who are familiar so as to save time in the review process. That said, I would probably feel the same reviewing a package written in Java.

@arokem
Copy link

arokem commented Dec 2, 2018

Yes. That all makes sense. Thanks for your candor, @fmohr.

Let's keep looking for a reviewer that speaks Python...

@arokem
Copy link

arokem commented Dec 2, 2018

Hey @krother, @nilesh-patil : would either or both of you be willing to review this article for JOSS?

@arokem
Copy link

arokem commented Dec 13, 2018

Hey @jsgalan, @tupi: would either or both of you be willing to review this article for JOSS? I realize that we are coming on the holidays. If you think that you will have time to review this in the new year, that's fine too.

@jsgalan
Copy link

jsgalan commented Dec 13, 2018

Hi all,

Yes, i will have time to review it. Please assign it to me :)

Best

@arokem
Copy link

arokem commented Dec 17, 2018

@whedon assign @jsgalan as reviewer

@whedon
Copy link
Author

whedon commented Dec 17, 2018

OK, the reviewer is @jsgalan

@arokem
Copy link

arokem commented Dec 17, 2018

@whedon start review

@whedon
Copy link
Author

whedon commented Dec 17, 2018

OK, I've started the review over in #1132. Feel free to close this issue now!

@arokem
Copy link

arokem commented Dec 17, 2018

Thanks for taking this on @jsgalan ! Please head over to #1132 for the review checklist. I am closing this one.

@arokem arokem closed this as completed Dec 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants