[PRE REVIEW]: Simulation of fracture and damage with Peridynamics.jl

[editorialbot]

Submitting author: !--author-handle-->@kaipartmann<!--end-author-handle-- (Kai Partmann) Repository: https://github.com/kaipartmann/Peridynamics.jl Branch with paper.md (empty if default branch): paper_juliacon_2023 Version: v0.2.0 Editor: !--editor-->@luraess<!--end-editor-- Reviewers: @ranocha, @HaoZeke Managing EiC: Mathieu Besançon

Status

Status badge code:

HTML: <a href="https://proceedings.juliacon.org/papers/b5f2635daed8de1734d967149f046ee4"><img src="https://proceedings.juliacon.org/papers/b5f2635daed8de1734d967149f046ee4/status.svg"></a>
Markdown: [![status](https://proceedings.juliacon.org/papers/b5f2635daed8de1734d967149f046ee4/status.svg)](https://proceedings.juliacon.org/papers/b5f2635daed8de1734d967149f046ee4)

Author instructions

Thanks for submitting your paper to JCON @kaipartmann. Currently, there isn't a JCON editor assigned to your paper.

The AEiC suggestion for the handling editor is @luraess.

@kaipartmann if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.

Editor instructions

The JCON 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:

@editorialbot commands

[editorialbot]

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 source files, type:

@editorialbot generate pdf

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.90  T=0.01 s (815.7 files/s, 226326.3 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
TeX                              8            251            194           2471
Ruby                             1              8              4             45
Markdown                         1             20              0             37
YAML                             1              0              0             22
-------------------------------------------------------------------------------
SUM:                            11            279            198           2575
-------------------------------------------------------------------------------

Commit count by author:

   291  Kai Partmann
   126  kfrb
    36  kaipartmann
    27  Manuel Dienst
     4  =
     2  CompatHelper Julia
     2  K. Weinberg
     1  Kerstin Weinberg
     1  dependabot[bot]

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1137/141000671 is OK
- 10.1007/s42102-018-0004-x is OK
- 10.3934/matersci.2022049 is OK
- 10.1002/pamm.202200217 is OK
- 10.1016/j.jmps.2019.06.016 is OK
- 10.1177/1081286518803411 is OK
- 10.21105/joss.03020 is OK
- 10.1007/978-1-4614-8465-3 is OK
- 10.1007/s10704-023-00726-7 is OK
- 10.1007/s42102-023-00100-0 is OK
- 10.1016/j.cma.2021.114085 is OK
- 10.1007/s10659-007-9125-1 is OK
- 10.1002/pamm.202200249 is OK
- 10.1007/s42102-019-00021-x is OK

MISSING DOIs

- No DOI given, and none found for title: Peridynamic computations of wave propagation and r...
- No DOI given, and none found for title: Peridynamic computations for thin elastic rods

INVALID DOIs

- https://doi.org/10.1016/j.tafmec.2010.08.001 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1016/S0022-5096(99)00029-0 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1016/j.softx.2023.101322 is INVALID because of 'https://doi.org/' prefix

[editorialbot]

Paper file info:

📄 Wordcount for paper.tex is 927

🔴 Failed to discover a Statement of need section in paper

[editorialbot]

License info:

✅ License found: MIT License (Valid open source OSI approved license)

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[luraess]

@editorialbot assign @me as editor

[editorialbot]

Assigned! @me is now the editor

[luraess]

@kaipartmann Thanks for submitting your draft to the JuliaCon Proceedings! I will be the managing editor of your paper. Could you please suggest me a succinct list of relevant reviewers and while we are working on getting them on for revision, please take some time fixing the reference issues listed here https://github.com/JuliaCon/proceedings-review/issues/150#issuecomment-2165819842 . To trigger PDF generation, use @editorialbot generate pdf command in here.

[kaipartmann]

@luraess Thanks for your informations. We would like to suggest ranocha, simonbyrne, and ma-sadeghi as reviewers. I just corrected the invalid DOIs. However, the two missing DOIs do not yet exist, as the papers are still in the review process. Is it necessary for all references to have a DOI?

[kaipartmann]

@editorialbot generate pdf

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[luraess]

@luraess Thanks for your informations. We would like to suggest ranocha, simonbyrne, and ma-sadeghi as reviewers. I just corrected the invalid DOIs. However, the two missing DOIs do not yet exist, as the papers are still in the review process. Is it necessary for all references to have a DOI?

@kaipartmann thanks for the update. For now let's keep these non resolving DOIs as such and we can fix things towards the end of the process, or see how to circumvent things if needed.

@ranocha @simonbyrne @ma-sadeghi - would you be willing to serve as reviewers for this 2 page contribution? Please 👍 or 👎 . Thanks.

[luraess]

@editorialbot commands

[editorialbot]

Hello @luraess, here are the things you can ask me to do:

# List all available commands
@editorialbot commands

# Add to this issue's reviewers list
@editorialbot add @username as reviewer

# Remove from this issue's reviewers list
@editorialbot remove @username from reviewers

# Get a list of all editors's GitHub handles
@editorialbot list editors

# Assign a user as the editor of this submission
@editorialbot assign @username as editor

# Remove the editor assigned to this submission
@editorialbot remove editor

# Remind an author, a reviewer or the editor to return to a review after a 
# certain period of time (supported units days and weeks)
@editorialbot remind @reviewer in 2 weeks

# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist

# Set a value for version
@editorialbot set v1.0.0 as version

# Set a value for branch
@editorialbot set juliacon-paper as branch

# Set a value for repository
@editorialbot set https://github.com/organization/repo as repository

# Set a value for the archive DOI
@editorialbot set 10.5281/zenodo.6861996 as archive

# Mention the EiCs for the correct track
@editorialbot ping track-eic

# Reject paper
@editorialbot reject

# Withdraw paper
@editorialbot withdraw

# Invite an editor to edit a submission (sending them an email)
@editorialbot invite @(.*) as editor

# Run checks and provide information on the repository and the paper file
@editorialbot check repository

# Check the references of the paper for missing DOIs
@editorialbot check references

# Generates the pdf paper
@editorialbot generate pdf

# Recommends the submission for acceptance
@editorialbot recommend-accept

# Accept and publish the paper
@editorialbot accept

# Update data on an accepted/published paper
@editorialbot reaccept

# Generates a LaTeX preprint file
@editorialbot generate preprint

# Flag submission with questionable scope
@editorialbot query scope

# Get a link to the complete list of reviewers
@editorialbot list reviewers

# Creates a post-review checklist with editor and authors tasks
@editorialbot create post-review checklist

# Open the review issue
@editorialbot start review

[luraess]

@editorialbot add @ranocha as reviewer

[editorialbot]

@ranocha added to the reviewers list!

[luraess]

@simonbyrne @ma-sadeghi would one of you would like to serve as reviewer ?

[luraess]

Pinging once more here @simonbyrne and @ma-sadeghi - would you be willing to serve as reviewer for this JuliaCon proceeding paper? Else, feel free to provide further suggestions 🙏

[kaipartmann]

@luraess, thank you for your support! Further suggestions: mauro3, sajavicius, HaoZeke

[simonbyrne]

Unfortunately, I am unable to review at this time.

[luraess]

@HaoZeke, @sajavicius 👋 Would you be interested in and available to review this JuliaCon Proceeding submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://juliacon.github.io/proceedings-guide/reviewer/

[HaoZeke]

@luraess thanks for the invite, I can review this submission :)

[luraess]

@luraess thanks for the invite, I can review this submission :)

Thanks!

[luraess]

@editorialbot add @HaoZeke as reviewer

[editorialbot]

@HaoZeke added to the reviewers list!

[luraess]

@editorialbot start review

[ma-sadeghi]

@luraess Sorry for the super late reply. Unfortunately, I can't review the submission at the time.

[luraess]

@editorialbot start review

[luraess]

@luraess Sorry for the super late reply. Unfortunately, I can't review the submission at the time.

Thanks for letting me know!

[luraess]

@editorialbot remove editor

[editorialbot]

Editor removed!

[luraess]

@editorialbot assign @luraess as editor

[editorialbot]

Assigned! @luraess is now the editor

[luraess]

@editorialbot start review

[editorialbot]

OK, I've started the review over in https://github.com/JuliaCon/proceedings-review/issues/165.