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]: Sapsan: Framework for Supernovae Turbulence Modeling with Machine Learning #3146
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:
|
PDF failed to compile for issue #3146 with the following error: Can't find any papers to compile :-( |
|
👋 @mbobra - are you able to edit this JOSS submission? |
@mbobra has been invited to edit this submission. |
@pikarpov-LANL - Given the comment in your README: "currently Sapsan is in alpha, but we are actively working on it and introduce new feature on a daily basis" and given that JOSS is looking for papers that are complete, I suggest this submission be withdrawn until it is more stable and more mature. Does this seem ok to you? If so, I will mark it as withdrawn. |
Hi Daniel,
This is an outdated note, left behind before I had any physics-informed methods, analytical tools, and wiki. As it stands, Sapsan is full-featured and ready for general use as outlined in the paper. I have removed that note from README.
Thank you for bringing it to my attention!
Plato
…________________________________
From: Daniel S. Katz ***@***.***>
Sent: Monday, April 5, 2021 5:52:19 PM
To: openjournals/joss-reviews
Cc: Karpov, Platon; Mention
Subject: [EXTERNAL] Re: [openjournals/joss-reviews] [PRE REVIEW]: Sapsan: Framework for Supernovae Turbulence Modeling with Machine Learning (#3146)
@pikarpov-LANL<https://github.com/pikarpov-LANL> - Given the comment in your README: "currently Sapsan is in alpha, but we are actively working on it and introduce new feature on a daily basis" and given that JOSS is looking for papers that are complete, I suggest this submission be withdrawn until it is more stable and more mature. Does this seem ok to you? If so, I will mark it as withdrawn.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#3146 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANYOTSJBGVDC4WWW4XOXQFLTHJELHANCNFSM42M6PW3Q>.
|
👋 @dfm - are you able to edit this submission? |
@dfm has been invited to edit this submission. |
@whedon assign me as editor Yes - I'm happy to edit. @pikarpov-LANL: I'll do a first pass and then start looking for reviewers in the next few days. I'll keep you posted as this progresses and if I have any questions. You should also feel free to ask me any questions as we go. |
OK, the editor is @dfm |
@dfm great, thank you! |
@whedon generate pdf from branch joss |
|
PDF failed to compile for issue #3146 with the following error: ORCID looks malformed |
@whedon check references from branch joss |
|
@whedon check repository from branch joss |
|
|
@pikarpov-LANL: Can you make these small changes:
|
Also, would it be possible to add my personal github account (pikarpov) to this thread? This way I will receive email notifications to my personal email box. Work email is a bit harder and it is only available during work hours. LANL requires us to have a separate account that is distinctly LANL, however, I push to Sapsan from both since it is open-sourced now. |
@whedon generate pdf from branch joss |
|
OK, @kburns is now a reviewer |
@pikarpov-LANL: would you like me to switch this review to your @pikarpov account altogether or would you rather the submission still be associated with @pikarpov-LANL? Sorry I didn't get back to you about this sooner! |
@dfm please keep the submission under @pikarpov-LANL, for the lab's record. However, I will reply faster @pikarpov, since I get notifications straight to my personal email, hence my phone. I cannot do the same with the lab's account. |
@whedon add @MilesCranmer as reviewer Thanks Miles for agreeing to be our second reviewer! I'll get the review started shortly in a new thread, so we can all head over there for the rest of the process. Please don't hesitate to ask if you have any questions as the review progresses. |
OK, @MilesCranmer is now a reviewer |
@whedon start review |
OK, I've started the review over in #3199. |
Submitting author: @pikarpov-LANL (Platon I. Karpov)
Repository: https://github.com/pikarpov-LANL/Sapsan
Version: v0.2.5
Editor: @dfm
Reviewers: @kburns, @MilesCranmer
Managing EiC: Daniel S. Katz
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.
Author instructions
Thanks for submitting your paper to JOSS @pikarpov-LANL. Currently, there isn't an JOSS editor assigned to your paper.
@pikarpov-LANL 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: