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

[Surendra Nadh Somala]

Josimar,

>From your zipped figure, I see that there are nodes on the strike slip
fault that also belong to the thrust fault.

After creating the nodeset for thrust_fault in Cubit/Trelis, add a line in
your .jou file (immediately before creating a label for thrust fault
nodeset) to remove all nodes that belong to the strike slip (assuming your
strike-slip fault is the main fault).
Export the new .exo file after making these changes to your boundary
condition journal file of Cubit and try to run pylith with the update
Exodus mesh.

-Surendra


___________
*Surendra Nadh Somala*
Assistant Professor
Department of Civil Engineering (Block-E, 208)
Indian Institute of Technology (IIT) Hyderabad
Kandi, Sangareddy
Telangana, India - 502285
Phone : +91 (0)40 2301-8457
http://civil.iith.ac.in/surendra/

On Tue, Feb 13, 2018 at 10:42 PM, 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
>
>
>
> _______________________________________________
> CIG-SHORT mailing list
> CIG-SHORT at geodynamics.org
> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-short/attachments/20180214/29639285/attachment-0001.html>