Submitting author: @telegraphic (Danny Price)
Repository: https://github.com/UCBerkeleySETI/blimpy
Version: 1.3.6
Editor: @xuanxu
Reviewers: @garrettj403, @zhampel
Author instructions
Thanks for submitting your paper to JOSS @telegraphic. Currently, there isn't an JOSS editor assigned to your paper.
@telegraphic 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
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
What happens now?
This submission is currently in a pre-review state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience :smile_cat:
You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here.
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1534 with the following error:
Can't find any papers to compile :-(
Hi @xuanxu, this submission looks right up your alley. Can you edit?
Hey @arfon, I see paper.md and paper.bib right at the top level of the repo, any idea why whedon doesn't see those?
Hi @telegraphic, thanks for your submission. While we get things initiated here, I noticed that your article is quite short; although we don't publish full-length papers here, we do expect 250-1000 words (one or two pages in PDF format is typical). Can you expand on your software a bit more, for example talking about features, infrastructure, etc., or even giving one or two examples?
@whedon generate pdf
Attempting PDF compilation. Reticulating splines etc...
Hi @xuanxu, this submission looks right up your alley. Can you edit?
@kyleniemeyer yes, I can edit this
@whedon assign @xuanxu as editor
OK, the editor is @xuanxu
Hi @kyleniemeyer -- happy to expand on the software, will add a few paragraphs
:wave: @garrettj403 and @dhuppenkothen: Would you be willing to review this paper? I think your expertise in Python and Jupyter notebooks and your background on Astronomy/Radioastronomy makes both of you a great fit for this submission.
@xuanxu Unfortunately I'm going to be travelling/teaching/organizing at a school for the next few weeks, so I don't think I can do this on a timescale earlier than about a month from now. I'm really sorry!
Hi @xuanxu, I'm happy to review this repo. I'm not very familiar with SETI or the Breakthrough Listen program, but it looks like an interesting project!
Thanks for agreeing to review @garrettj403, I will assign you now.
I'll start the review issue once I find the second reviewer. Stay tuned.
@whedon assign @garrettj403 as reviewer
OK, the reviewer is @garrettj403
:wave: @benjaminrose — would you be willing to contribute a review for JOSS on this submission?
Hi @telegraphic - In case you didn't know this, ApJ has an agreement with JOSS where you can submit two papers in parallel: one to JOSS and one to ApJ. You can find more info here: https://iopscience.iop.org/article/10.3847/1538-4357/aaf876
Thanks @garrettj403 for bringing that to my attention!
:wave: @zhampel — would you be willing to contribute a review for JOSS on this submission?
@xuanxu Yes I can provide a review for this submission.
Great, thanks @zhampel
I'm going to move this forward to review
@whedon add @zhampel as reviewer
OK, @zhampel is now a reviewer
@whedon start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/1554. Feel free to close this issue now!
@garrettj403, @zhampel - please head over to #1554 where the review will take place.