[PRE REVIEW]: DFM Generator v2.2: a new method for simulating the growth of natural fracture networks

[editorialbot]

Submitting author: !--author-handle-->@JointFlow<!--end-author-handle-- (Michael Welch) Repository: https://github.com/JointFlow/DFMGenerator Branch with paper.md (empty if default branch): Version: v2.2.2 Editor: !--editor-->@diehlpk<!--end-editor-- Reviewers: @CBenghi, @mohd-afeef-badri, @iammix, @DaveHealy-github Managing EiC: Kristen Thyng

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/32db13931bcebe707f05aeb1b394dfb0"><img src="https://joss.theoj.org/papers/32db13931bcebe707f05aeb1b394dfb0/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/32db13931bcebe707f05aeb1b394dfb0/status.svg)](https://joss.theoj.org/papers/32db13931bcebe707f05aeb1b394dfb0)

Author instructions

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

@JointFlow 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 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:

@editorialbot commands

[JointFlow]

Hi, sorry for the delay in replying. I'm not quite sure how this process works - do you need anything more from me right now? I cannot think of other potential reviewers at the moment but I could contact some of the reviewers I previously suggested to ask if they received the invitation to review, and if they are unable to review it themselves, if they could suggest other reviewers. With regard to making any required corrections, should I wait until the reviews are completed for this? I noticed that the auto-check picked up a broken DOI link - this should be very straightforward to fix.

[diehlpk]

@JointFlow Yes, please start working on things now. We do a rolling review and do not do rebuttal letters.

[flohorovicic]

Hi @flohorovicic do you have time to review this paper?

Hi all,

Sorry, I can not commit to another review, at the moment (already have several on my desk...).

Kind regards, Florian

[diehlpk]

Hi @CBenghi how is your review going?

[diehlpk]

Hi, sorry for the delay in replying. I'm not quite sure how this process works - do you need anything more from me right now? I cannot think of other potential reviewers at the moment but I could contact some of the reviewers I previously suggested to ask if they received the invitation to review, and if they are unable to review it themselves, if they could suggest other reviewers. With regard to making any required corrections, should I wait until the reviews are completed for this? I noticed that the auto-check picked up a broken DOI link - this should be very straightforward to fix.

No, I am still looking for a second reviewer. If you could mention potential reviewers that would be good.

[diehlpk]

Hi @CBenghi how is your review going?

[diehlpk]

Hi @JointFlow could you please help identifying a second reviewer?

[diehlpk]

Hi @JointFlow could you please help identifying a second reviewer?

[diehlpk]

Hi @sthavishtha do you have time to review this paper?

[diehlpk]

Hi @mohd-afeef-badri do you have time to review this paper?

[diehlpk]

Hi @iammix do you have time to review this paper?

[sthavishtha]

@diehlpk sorry i am unavailable for review.

[JointFlow]

Hi, I have contacted Dave Healy directly to ask him again whether he would be able to review the paper (I had suggested him previously but I don't think he replied to the invitation). I will let you know as soon as he replies.

I have also updated the .bib file on the Github server to fix the broken doi link identified above. However I am not sure how to regenerate the pdf file and update it - are them some instructions on how to do this?

[mohd-afeef-badri]

@diehlpk Hi,

sure I would be happy to review this. You can add me as a reviewer.

[diehlpk]

@editorialbot add @mohd-afeef-badri as reviewer

[editorialbot]

@mohd-afeef-badri added to the reviewers list!

[iammix]

@diehlpk yes, I will be available to review this.

[diehlpk]

@editorialbot add @iammix as reviewer

[editorialbot]

@iammix added to the reviewers list!

[diehlpk]

@iammix how is your review going?

[diehlpk]

Hi, I have contacted Dave Healy directly to ask him again whether he would be able to review the paper (I had suggested him previously but I don't think he replied to the invitation). I will let you know as soon as he replies.

I have also updated the .bib file on the Github server to fix the broken doi link identified above. However I am not sure how to regenerate the pdf file and update it - are them some instructions on how to do this?

You can run @editorialbot generate pdf to update the pdf.

[JointFlow]

Hi, I have spoken to Dave Healy again and he said that he would be happy to review the paper. His Github address is DaveHealy-github. Will you contact him to request a review?

[diehlpk]

@editorialbot add @DaveHealy-github as reviewer

[editorialbot]

@DaveHealy-github added to the reviewers list!

[diehlpk]

Hi, I have spoken to Dave Healy again and he said that he would be happy to review the paper. His Github address is DaveHealy-github. Will you contact him to request a review?

I invited him.

[DaveHealy-github]

Hello How do I:

1. View the ms
2. Review the ms In this system?

Thanks Dave

Prof. Dave Healy [he/him/his] Director of Geosolutionshttp://www.geosolutions.leeds.ac.uk/ Professor of Geomechanics Staff profile pagehttps://environment.leeds.ac.uk/staff/12746/dave-healy

Leading the energy transition through interdisciplinary subsurface research

My working day may not be your working day. Please do not feel obliged to reply to this e-mail outside of your normal working hours.

Room 8.107 Earth and Environment Building School of Earth and Environment University of Leeds Leeds LS2 9JT

From: Patrick Diehl @.> Sent: Wednesday, August 14, 2024 11:19 PM To: openjournals/joss-reviews @.> Cc: David Healy @.>; Mention @.> Subject: Re: [openjournals/joss-reviews] [PRE REVIEW]: DFM Generator v2.2: a new method for simulating the growth of natural fracture networks (Issue #6178)

CAUTION: External Message. Use caution opening links and attachments.

Hi, I have spoken to Dave Healy again and he said that he would be happy to review the paper. His Github address is DaveHealy-github. Will you contact him to request a review?

I invited him.

- Reply to this email directly, view it on GitHubhttps://github.com/openjournals/joss-reviews/issues/6178#issuecomment-2290016168, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AESJKRVYJIYDDE5MUOE73KLZRPJVJAVCNFSM6AAAAABBKNAIR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJQGAYTMMJWHA. You are receiving this because you were mentioned.Message ID: @.***>

[diehlpk]

Hello How do I: 1. View the ms 2. Review the ms In this system? Thanks Dave Prof. Dave Healy [he/him/his] Director of Geosolutionshttp://www.geosolutions.leeds.ac.uk/ Professor of Geomechanics Staff profile pagehttps://environment.leeds.ac.uk/staff/12746/dave-healy Leading the energy transition through interdisciplinary subsurface research My working day may not be your working day. Please do not feel obliged to reply to this e-mail outside of your normal working hours. Room 8.107 Earth and Environment Building School of Earth and Environment University of Leeds Leeds LS2 9JT From: Patrick Diehl @.> Sent: Wednesday, August 14, 2024 11:19 PM To: openjournals/joss-reviews @.> Cc: David Healy @.>; Mention @.> Subject: Re: [openjournals/joss-reviews] [PRE REVIEW]: DFM Generator v2.2: a new method for simulating the growth of natural fracture networks (Issue #6178) CAUTION: External Message. Use caution opening links and attachments. Hi, I have spoken to Dave Healy again and he said that he would be happy to review the paper. His Github address is DaveHealy-github. Will you contact him to request a review? I invited him. - Reply to this email directly, view it on GitHub<#6178 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AESJKRVYJIYDDE5MUOE73KLZRPJVJAVCNFSM6AAAAABBKNAIR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJQGAYTMMJWHA. You are receiving this because you were mentioned.Message ID: @.***>

You can run here in a comment

• @editorialbot generate pdf to generate the ms
• @editorialbot generate my checklist to generate your checklist
• You can post your review in a comment here as well.