[CIG-SHORT] fault edge motion

[Surendra Nadh Somala]

Dear Huihui,
I'm guessing you want simulate an earthquake cycle by a combination of
quasi-static and dynamic rupture which may have to be manually done
separately in pylith as of now.
Anyhow, if you need more help on this please feel free to let me know and I
can setup the corresponding .cfg files as you need.  As Brad suggested, it
is recommended to have at least one node offset between the kinematic edge
and dynamic edge (instead of both being the same) to have converging
results, unless that is what you really intend to be so.
Best,
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 Thu, Oct 26, 2017 at 8:16 AM, Huihui Weng <qfkq7850 at mail.ustc.edu.cn>
wrote:

> Hi Brad,
>
> The two faults are parallel and adjacent as the attached png file shows.
> The overlap of the two faults is the fault edge (one line buried inside the
> domain), which I set as fault edge in the cfg file. Other boundaries of the
> two faults are intersecting with the domain boundaries, thus they are not
> buried fault edges. Part of the scripts are as fellow:
>
> [pylithapp.timedependent]
> interfaces = [fault_up,fault_down]
> [pylithapp.timedependent.interfaces]
> fault_up = pylith.faults.FaultCohesiveDyn
> fault_down = pylith.faults.FaultCohesiveKin
>
> [pylithapp.timedependent.interfaces.fault_up]
> label = fault_up
> edge = fault_edge
> [pylithapp.timedependent.interfaces.fault_down]
> label = fault_down
> edge = fault_edge
>
>
> The nodes of the fault edge (the white line) don’t slip, causing a slip
> “gap” between the two faults. If I comment either of the lines of "edge =
> fault_edge” in the script, it fails to run.
>
> In addition, how about the case if the two faults bend, such as one kink
> at the fault edge?  In fact, this case is similar with the example in the
> PyLith manual, i.e., ~/examples/2d/subduction/step03.cfg, except that I
> change it to 3D and change one kinematic fault to a dynamic fault. Thanks.
>
> Best regards,
> Huihui
>
> On 25 Oct 2017, at 11:26 PM, Brad Aagaard <baagaard at usgs.gov> wrote:
>
> Huihui,
>
> I do not know what you mean by "two adjacent planar faults". Are the
> faults parallel? perpendicular? Do they intersect? Please send a diagram of
> your fault geometry and indicate which edges you marked as buried fault
> edges.
>
> Thanks,
> Brad
>
>
> On 10/25/2017 02:25 AM, Huihui Weng wrote:
>
> Dear all,
> I tried to build a model with two adjacent planar faults, one is kinematic
> fault and the other is dynamic fault. The PyLith of new version requires me
> to provide the fault edge, i.e., the group of nodes in the line that
> connects the two faults. But I find the fault edge always keep fixed. How
> can I set up the model to make the fault edge move to fill the “gap” of
> slip between these two faults? It does seem it is OK for 2D models of older
> Pylith versions. Thanks.
> Best regards,
> Huihui
> _______________________________________________
> CIG-SHORT mailing list
> CIG-SHORT at geodynamics.org
> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>
>
> _______________________________________________
> CIG-SHORT mailing list
> CIG-SHORT at geodynamics.org
> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>
>
>
> _______________________________________________
> 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/20171027/cca1a772/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Adjacent_faults.png
Type: image/png
Size: 54692 bytes
Desc: not available
URL: <http://lists.geodynamics.org/pipermail/cig-short/attachments/20171027/cca1a772/attachment-0001.png>