[CIG-SHORT] Problem with fault intersection in 3D simulations

Tue Feb 13 18:22:08 PST 2018

Hi Charles,

Thanks for helping me with this problem. I meshed the subset of surfaces to
ensure certain element size on those surfaces, for example, at the fault.
There are perhaps better ways of doing it that I am not aware of. But I
hope this is not the source of problem.

It is possible that I may be making some fundamental mistake in the
definition of the fault edges for the fault  intersection.

thank you
Josimar

On Tue, Feb 13, 2018 at 8:12 PM, Charles Williams <willic3 at gmail.com> wrote:

> Hi Josimar,
>
> I’m working through things now.  One question I have is why do you just
> mesh a subset of the surfaces before smoothing them and then creating the
> volume mesh?
>
> Cheers,
> Charles
>
>
> On 14/02/2018, at 1:23 PM, Josimar Alves da Silva <jsilva.mit at gmail.com>
> wrote:
>
> Hi Charles,
>
> Yes I do have the files. I sent them to your e-mail.
>
> Let me know if you need any further details about the model.
>
> thank you in advance,
> Josimar
>
> On Tue, Feb 13, 2018 at 4:51 PM, Charles Williams <willic3 at gmail.com>
> wrote:
>
>> Dear Josimar,
>>
>> Do you have the journal files you used to create the mesh?  That might
>> allow us to see if any of the nodesets are set up incorrectly.
>>
>> Cheers,
>> Charles
>>
>> p.s.  Depending on the type of problem you’re trying to solve, having the
>> external boundaries so close to the faults is likely to cause problems,
>> since your boundary conditions will be interfering with your solution.
>>
>>
>> On 14/02/2018, at 10:37 AM, Josimar Alves da Silva <jsilva.mit at gmail.com>
>> wrote:
>>
>> Hi Charles,
>>
>> Thank you for your suggestions. Answering your questions:
>>
>> 1) Yes there is another layer on top of the faults (the overburden). See
>> attached figure for further details. The faults terminate inside the domain
>> before reaching the surface.
>> 2) There is no more mesh extending horizontally. The vertical edges are
>> not included because they belong to the boundary (please correct me if it
>> should be otherwise)
>>
>> let me know if you have any further suggestions.
>>
>> thank you,
>> Josimar
>>
>>
>> On Tue, Feb 13, 2018 at 4:15 PM, Charles Williams <willic3 at gmail.com>
>> wrote:
>>
>>> Dear Josimar,
>>>
>>> Is there another layer on top of the mesh shown in your second figure?
>>> Otherwise, it looks to me as though these faults do intersect the upper
>>> surface.  Also, is there more mesh extending horizontally from the block
>>> you’ve shown? If so, the vertical fault edges should also be marked as
>>> fault_edges.  If not, I would say your boundaries are too close to your
>>> sources of deformation (although this wouldn’t be causing your topology
>>> problem).  It might be helpful if you could send us the journal files you
>>> used to create your mesh.
>>>
>>> Cheers,
>>> Charles
>>>
>>>
>>> On 14/02/2018, at 6:12 AM, Josimar Alves da Silva <jsilva.mit at gmail.com>
>>> wrote:
>>>
>>> Hi Brad, Charles and Matt
>>>
>>> I am having trouble in running a 3D PyLith simulation with 2
>>> intersecting faults and I am wondering if you can help me. The problem
>>> occurs when I run the simulation with both faults on the domain. Note that
>>> I have already run the simulation with each fault independently and found
>>> no problems.
>>>
>>> The error message says the following (see also attached the full log
>>> containing the  error message ):
>>>
>>> RuntimeError: Error occurred while adjusting topology to create cohesive
>>> cells for fault 'Thrust_fault'.
>>> Error in topology of mesh associated with symmetry of adjacency
>>> information.
>>>
>>> See attached also figures for information regarding how I am defining
>>> the fault buried edges, specially regarding the intersection part. Note
>>> that neither  fault goes all the up to the surface and they terminated
>>> inside the domain.
>>>
>>> I know this problem was often discussed to be related to the mesh
>>> element quality. An histogram of the mesh quality for all elements on my
>>> domain show that the mesh quality is as required for PyLith (< 3 ).
>>>
>>> If it helps, I am attaching also the configuration file (.cfg)
>>> containing the information regarding my simulation set up. Note  the that I
>>> am constrained to use pylith version 2.1.3, however using version 2.2  did
>>> not give a different error message.
>>>
>>> Please let me know if you have any suggestions on how to solve this
>>> problem.
>>>
>>> thank you
>>> Josimar
>>>
>>> <Erro_Fault_Intersection.cfg><Error_Message_Fault_Intersection.out>
>>> <PyLith_Problem.zip>_______________________________________________
>>> CIG-SHORT mailing list
>>> CIG-SHORT at geodynamics.org
>>> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>>>
>>>
>>>
>>> *Charles Williams I Geodynamic ModelerGNS Science **I** Te Pῡ Ao*
>>> 1 Fairway Drive
>>> <https://maps.google.com/?q=1+Fairway+Drive&entry=gmail&source=g>,
>>> Avalon 5010, PO Box 30368, Lower Hutt 5040, New Zealand
>>> *Ph* 0064-4-570-4566 I *Mob* 0064-22-350-7326 I *Fax* 0064-4-570-4600
>>> *http://www.gns.cri.nz/* <http://www.gns.cri.nz/> *I* *Email: *
>>> *C.Williams at gns.cri.nz* <your.email at gns.cri.nz>
>>>
>>>
>> <PyLith_Problem_v02.001.jpeg>
>>
>>
>>
>> *Charles Williams I Geodynamic ModelerGNS Science **I** Te Pῡ Ao*
>> 1 Fairway Drive
>> <https://maps.google.com/?q=1+Fairway+Drive&entry=gmail&source=g>,
>> Avalon 5010, PO Box 30368, Lower Hutt 5040, New Zealand
>> *Ph* 0064-4-570-4566 I *Mob* 0064-22-350-7326 I *Fax* 0064-4-570-4600
>> *http://www.gns.cri.nz/* <http://www.gns.cri.nz/> *I* *Email: *
>> *C.Williams at gns.cri.nz* <your.email at gns.cri.nz>
>>
>>
>
>
> *Charles Williams I Geodynamic ModelerGNS Science **I** Te Pῡ Ao*
> 1 Fairway Drive
> <https://maps.google.com/?q=1+Fairway+Drive&entry=gmail&source=g>, Avalon
> 5010, PO Box 30368, Lower Hutt 5040, New Zealand
> *Ph* 0064-4-570-4566 I *Mob* 0064-22-350-7326 I *Fax* 0064-4-570-4600
> *http://www.gns.cri.nz/* <http://www.gns.cri.nz/> *I* *Email: *
> *C.Williams at gns.cri.nz* <your.email at gns.cri.nz>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-short/attachments/20180213/55d46719/attachment.html>