Closed editorialbot closed 1 year ago
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:
@editorialbot commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@editorialbot generate pdf
Couldn't check the bibtex because branch name is incorrect: https://gitlab.inria.fr/melissa/melissa/-/tree/JOSS-paper
Couldn't check the bibtex because branch name is incorrect: https://gitlab.inria.fr/melissa/melissa/-/tree/JOSS-paper
:warning: An error happened when generating the pdf.
@editorialbot set JOSS-paper as branch
Done! branch is now JOSS-paper
@editorialbot check repository
Software report:
github.com/AlDanial/cloc v 1.88 T=0.21 s (721.5 files/s, 129697.8 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 76 1993 2269 8309
SVG 5 3 4 4462
C 7 286 603 2247
Markdown 24 610 0 1659
JSON 9 0 0 534
Jupyter Notebook 1 0 948 383
Fortran 90 3 121 80 350
TeX 2 49 0 337
C/C++ Header 6 101 113 256
CMake 7 72 144 249
YAML 2 16 5 211
Dockerfile 1 12 5 41
Fortran 77 1 9 15 38
Bourne Shell 3 30 17 20
TOML 1 0 0 3
-------------------------------------------------------------------------------
SUM: 148 3302 4203 19099
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 1714
@editorialbot check references
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1109/SC41405.2020.00005 is OK
- 10.1145/3281464.3281470 is OK
MISSING DOIs
- 10.1007/978-3-030-81627-8_6 may be a valid DOI for title: Unlocking Large Scale Uncertainty Quantification with In Transit Iterative Statistics
- 10.1109/cluster.2012.26 may be a valid DOI for title: Damaris: How to Efficiently Leverage Multicore Parallelism to Achieve Scalable, Jitter-free I/O
- 10.1007/s10586-011-0162-y may be a valid DOI for title: Dataspaces: an interaction and coordination framework for coupled simulation workflows
- 10.1145/3426462.3426468 may be a valid DOI for title: The Challenges of In Situ Analysis for Multiple Simulations
- 10.1177/10943420221110507 may be a valid DOI for title: An elastic framework for ensemble-based large-scale data assimilation
- 10.1115/1.4046020 may be a valid DOI for title: A visual sensitivity analysis for parameter-augmented ensembles of curves
- 10.1109/cluster51413.2022.00051 may be a valid DOI for title: Painless Transposition of Reproducible Distributed Environments with NixOS Compose
- 10.1109/tpds.2021.3105994 may be a valid DOI for title: Design and Performance Characterization of RADICAL-Pilot on Leadership-class Platforms
INVALID DOIs
- None
š @robcaulk - just a note as I look at the repo. The README is very short, and my guess is that the reviewers will ask you to add more to it, such as information about usage and contributions, even if this is also in the documentation. To me, much of the first page of the documentation would make sense on the README (plus information on how others could contribute).
Also, the short name of the conference that you refer to as SuperComputing in the README and Supercomputing in the docs is actually SC17.
In addition, you could work on the possibly missing DOIs that editorialbot suggests, but note that some may be incorrect. Please feel free to make changes to your .bib file, then use the command @editorialbot check references
to check again, and the command @editorialbot generate pdf
when the references are right to make a new PDF. editorialbot commands need to be the first entry in a new comment.
I'll see if we can find an editor now, though this may be delayed a bit, as I'll be offline for about a week starting in a day or so.
š @diehlpk - would you be willing to edit this submission?
@editorialbot invite @diehlpk as editor
Invitation to edit this submission sent!
@editorialbot add @diehlpk as editor
Assigned! @diehlpk is now the editor
Thanks @danielskatz for the tips re: README.md and SC17. We will go ahead and improve the README to summarize the important details for users. The DOIs should be easy to fix as well.
Looks like we got an editor quicker than expected (hey @diehlpk!), please let me know if you would like me to help you find potential reviewers in your JOSS database (will you link the latest reviewer database here?) Oh I see the list is linked in the original post here, I will have a look and post recommendations..
Here are my recommendations for reviewers based on keywords in the list furnished with the original post:
weilewei markhahn rreinecke tupi elauksap diegomcarvalho acrlakshman jamiebramwell p-costa
Keywords used: Sensitivity Analysis, Surrogate modeling, HPC, distributed computing, AI, deep learning, fluid dynamics
Let me know if we should extend the list further.
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1109/SC41405.2020.00005 is OK
- 10.1007/978-3-030-81627-8_6 is OK
- 10.1109/CLUSTER.2012.26 is OK
- 10.1145/1851476.1851481 is OK
- 10.1145/3426462.3426468 is OK
- 10.1177/10943420221110507 is OK
- 10.1115/1.4046020 is OK
- 10.1145/3281464.3281470 is OK
- 10.1109/CLUSTER51413.2022.00051 is OK
- 10.1109/TPDS.2021.3105994 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @weilewei do you have time to review this paper?
Hi @p-costa do you have time to review this paper?
Thanks for the invite @diehlpk. Unfortunately, I am a bit busy at the moment, and though I feel I could review it with sufficient time, this falls a bit outside my expertise.
Hi @jamiebramwell do you have time to review this paper?
Hi @markhahn or @rreinecke would you have time to review this paper?
Sorry @diehlpk I am swamped.
Hi @tupi do you have time to review this paper?
Hi @elauksap do you have time to review this paper?
Hi @diegomcarvalho do you have time to review this paper?
Hi Patrick,
Iām a little taken here without enough time for a few months.
Best wishes, d.c
On 9 Mar 2023, at 20:09, Patrick Diehl @.***> wrote:
Hi @diegomcarvalho https://github.com/diegomcarvalho do you have time to review this paper?
ā Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/5164#issuecomment-1462950431, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABULPAHJTZJDF6MRICDU4M3W3JPKLANCNFSM6AAAAAAU7N7574. You are receiving this because you were mentioned.
Hi @diehlpk,
I'm sorry, I'm on a tight schedule and I don't think I will be able to complete the review in due time.
Best wishes, Pasquale
Hi @acrlakshman do you have time to review this paper?
Hi @NoujoudNader do you have time to review this paper?
Sure @diehlpk
@diehlpk Sure!
@editorialbot add @acrlakshman as reviewer
@acrlakshman added to the reviewers list!
@editorialbot add @NoujoudNader as reviewer
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@editorialbot commands
@editorialbot add @NoujoudNader as reviewer
@NoujoudNader added to the reviewers list!
@editorialbot start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/5291.
Submitting author: !--author-handle-->@robcaulk<!--end-author-handle-- (Robert Caulk) Repository: https://gitlab.inria.fr/melissa/melissa Branch with paper.md (empty if default branch): JOSS-paper Version: V1.0.0 Editor: !--editor-->@diehlpk<!--end-editor-- Reviewers: @acrlakshman, @NoujoudNader Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @robcaulk. Currently, there isn't a JOSS editor assigned to your paper.
@robcaulk 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: