[CIG-SHORT] Subduction + Thrust fault

[Christian Baillard]

Hi,

Thank you for the helpful advices, I agree that the third step is the more complicated. I'm reassured to see that the problem can be handled with pylith.

Best regards,

christian

Le 25 nov. 2013 à 19:04, Brad Aagaard a écrit :

> On 11/25/2013 09:56 AM, Christian Baillard wrote:
>> Hi Matthew,
>> 
>> Drawing a fault with a brutal end in the visco-elastic material won't cause any edge weird behavior?
>> 
>> Christian
> 
> There are really three issues:
> (1) Creating the finite-element model
> (2) Running the PyLith simulations
> (3) Getting a well-resolved result
> 
> As Matt indicated, for multiple non-intersection faults, (1) and (2) are just a matter of adding the additional surfaces in CUBIT, making the corresponding nodesets, and adding the additional fault parameters to the .cfg file. If the geometry is very complex, this can be tricky but the conceptual model is straightforward.
> 
> Your question here is in regards to (3). If the viscoelastic relaxation is resulting in localized deformation, you may need to increase the resolution in that region. This is true in many types of numerical models. One starts with some reasonable resolution based on past experience or rule of thumb, and then one should carefully examine the solution to see where it might be poorly resolved and increase the resolution in those areas to see if it affects the results.
> 
> Regards,
> Brad
> 
> 
> 
>> 
>> Le 25 nov. 2013 à 18:16, Matthew Knepley a écrit :
>> 
>>> On Mon, Nov 25, 2013 at 11:12 AM, Christian Baillard <christian_baillard at hotmail.com> wrote:
>>> Hi,
>>> 
>>> I'm working on the 2D subduction problem. The classical problem is now partially solved in my problem, indeed I would like to add a second thrust fault to my model (see figure attached).
>>> How can I add this geometry/problem to the classical 2D subduction problem? I'm solving the quasi static problem, I would like the second thrust to stop at the elastic/visco-elastic interface so what are the boundary conditions I should use? Is that even possible with pylith?
>>> 
>>> The first step is to mark the other boundary you want a fault on with Cubit (or your meshing program). Once
>>> you do that, you can create another fault in the .cfg file the same way as the first (with the new marker).
>>> 
>>>    Matt
>>> 
>>> Best regards,
>>> 
>>> Christian
>>> 
>>> _______________________________________________
>>> CIG-SHORT mailing list
>>> CIG-SHORT at geodynamics.org
>>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>>> 
>>> 
>>> 
>>> --
>>> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
>>> -- Norbert Wiener
>>> _______________________________________________
>>> CIG-SHORT mailing list
>>> CIG-SHORT at geodynamics.org
>>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>> 
>> 
>> 
>> 
>> _______________________________________________
>> CIG-SHORT mailing list
>> CIG-SHORT at geodynamics.org
>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>> 
> 
> _______________________________________________
> CIG-SHORT mailing list
> CIG-SHORT at geodynamics.org
> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>