[CIG-SHORT] How does Pylith number vertices on fault

[Matthew Knepley]

On Thu, Oct 4, 2012 at 10:51 AM, Hongfeng Yang <hyang at whoi.edu> wrote:

>  On 10/04/2012 10:41 AM, Matthew Knepley wrote:
>
> On Thu, Oct 4, 2012 at 10:39 AM, Hongfeng Yang <hyang at whoi.edu> wrote:
>
>> Hi Developers,
>>
>> I am tracking time history of variables on particular vertices on the
>> fault. However, I found the vertex ID in Pylith (v_fault) is larger than
>> the total number of vertices on the fault. How can I convert the value
>> of v_fault back to the vertex location on the fault surface?
>>
>> For example, I got the following fault opening error message
>> WARNING! Fault opening with nonzero traction., v_fault: 4154, opening:
>> 1.03716e-10, normal traction: -0.0042952
>> mpinemesis: faults/FaultCohesiveDyn.cc:382: virtual void
>> pylith::faults::FaultCohesiveDyn::integrateResidual(const
>> pylith::topology::Field<pylith::topology::Mesh>&, PylithScalar,
>> pylith::topology::SolutionFields*): Assertion `fabs(tractionNormal) <
>> _zeroTolerance' failed.
>> [0]0:Return code = 0, signaled with Aborted
>>
>> v_fault points to vertex ID 4154. The total number of vertices on the
>> fault is 1472, however.
>>
>
>  The fault vertices are just vertices in the mesh, so this refers to the
> full
> mesh vertex numbering.
>
> Hi Matt,
>
> Do you mean the v_fault not only represents the ID of vertices on the
> fault, but any vertex in the volume/full mesh?
>

Yes. That is the way it is currently setup.

  Thanks,

     Matt


> If that is the case, I know where I go wrong.
>
> Hongfeng
>



-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://geodynamics.org/pipermail/cig-short/attachments/20121004/b3a73b40/attachment-0001.htm