-
-
Notifications
You must be signed in to change notification settings - Fork 36
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]: SNEWPY: A Data Pipeline from Supernova Simulations to Neutrino Signals #3729
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post. 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 |
|
A few suggestions for potential reviewers: apizzuto, bradkav (who has previously reviewed a JOSS paper I submitted), peterdenton (not on the JOSS reviewer list, but interested in neutrino codes) and rafaelab. (And, if we extend the search a bit, also kostunin, KAClough or people in the list of potential reviewers who include "astrophysics" in their topics.) Note also that, later this week, we plan to submit a separate paper that’s more focussed on the underlying physics to AAS Journals and would like to make use of the AAS/JOSS collaboration. |
@JostMigenda thanks for this submission. As you can see from my comment, many of our editors in this domain are currently pre-ocupied with other submissions as JOSS is processing a bit of a backlog at the moment. As such I have listed this work as |
@whedon assign me as editor I'm happy to edit! As @Kevin-Mattheus-Moerman mentioned, we're a little swamped, but I'll do a first pass of editing and start tracking down reviewers in the next week or so. Thanks in advance for your patience! |
OK, the editor is @dfm |
Thanks for volunteering—and yes, happy to wait a few days longer if it helps you stick to a sustainable workload! One first question to the editor right away: As is common in astro/particle physics, this work was done not just by a small number of people but as part of a larger collaboration (in this case the SNEWS Collaboration). Is it possible to include the collaboration name after the author list in a JOSS paper? (E.g. like the AASTeX class, which has a special |
@JostMigenda: I'm working on finding reviewers now and I'll keep you posted on that!
Sorry about the delay on this response, but I actually had to do a little digging. We don't currently have a special command for this and our usual recommendation for this is to just add the collaboration as an author. You'll need to include an affiliation, so perhaps choose the primary institution or just label it "no affiliation". |
@whedon add @apizzuto as reviewer Alex has agreed to review this submission - thank you!! I believe that Alex has identified a potential COI that should be shared here. @JostMigenda please let me know here or via email if you or the other authors have any issue with this, otherwise, I'm happy to waive it after it is disclosed. |
OK, @apizzuto is now a reviewer |
@whedon add @PeterDenton as reviewer And Peter has agreed to be our second reviewer - thanks! After we take a look at @apizzuto's potential conflict, we'll be good to get started. @ all: please don't hesitate to ask if you have any questions, comments, or issues as we go. I'm here to help this go smoothly! |
OK, @PeterDenton is now a reviewer |
Hi all, thanks for the submission! |
Thanks for agreeing to review! Re the COI: If this is simply about @apizzuto being a member of the IceCube collaboration together with a few of the authors of this paper, I don't think that's a problem. (Due to SNEWS being a collaboration between most major neutrino experiments, theorists, phenomenologists & modelers, most people in neutrino astrophysics would have that COI.) I'll check with the other lead developers if they see an issue beyond that and will get back to you soon. |
I confirm that we don't think this is an issue and we're happy with waiving this COI. |
Great, thanks for checking on that @JostMigenda . I'll take a look at the paper and code in the coming days, then |
FYI, the waived COI has to be approved by the editor, not by the authors. (not that I see any problem, but please wait for @dfm to decide.) |
Thanks @danielskatz! Yes, given the scope of this potential COI and @JostMigenda's response, I am happy to waive this case and proceed with the review. Thanks again @apizzuto for being transparent. I'll get the review started in a new thread and we'll move over there for the rest of the process. Thanks again, everyone! |
@whedon start review |
OK, I've started the review over in #3772. |
Submitting author: @JostMigenda (Jost Migenda)
Repository: https://github.com/SNEWS2/snewpy
Version: v1.1b3
Editor: @dfm
Reviewers: @apizzuto, @PeterDenton
Managing EiC: Kevin M. Moerman
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @JostMigenda. Currently, there isn't an JOSS editor assigned to your paper.
@JostMigenda 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 @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:
The text was updated successfully, but these errors were encountered: