On Mon, 5 Oct 2009, Petry Stefan wrote:
> I recompiled libmesh with the compiler flags "-DDEBUG
> -D_GLIBCXX_DEBUG_PEDANTIC" and linked it to our program.
> Unfortunately, I had to skip the flag "-D_GLIBCXX_DEBUG", because
> linker errors occured, when I tried to link a libmesh dll compiled
> wit
On Fri, 2 Oct 2009, Petry Stefan wrote:
> Unfortunately, I am not able to use configure, because I am working
> with libmesh on Windows. A student created an eclipse workspace for
> the compilation of libmesh,
Interesting. What are you guys doing about the POSIX dependencies
that libMesh has?
On Thu, Oct 1, 2009 at 1:46 AM, Petry Stefan wrote:
> Thank you for your help.
>
> The function Compute_Quadrature_Points evaluates the maximum number of
> quadrature points over all elements. This is done because there might be
> different types of elements within the mesh. In this example the
On Thu, 1 Oct 2009, Petry Stefan wrote:
> node 0: x=-0.0100975 ; y=0.0100975
> node 1: x=-0.010009 ; y=0.0101852
> node 2: x=-0.010081 ; y=0.0102585
> node 3: x=-0.0101701 ; y=0.0101701
This appears to be an inverted element by libMesh ordering. Have you
run in debug or devel mode? Try recompi
On Wed, Sep 30, 2009 at 9:23 AM, Petry Stefan wrote:
> unsigned int quadrature_points = 0;
> double **Mx_on_qpoints, **My_on_qpoints;
> double rVal = 0., phiVal = 0., MrTmp = 0., MphiTmp = 0.;
>
> MeshBase::const_element_iterator el =
> mes
I don't think John or Ben has hit on the problem yet; I likewise
haven't had a chance to do more than skim your code, but it did look
like you're correctly setting up a non-exterior quadrature rule and
pulling xyz coordinates.
On Wed, 30 Sep 2009, Petry Stefan wrote:
> -0.0101701 .0100975 Quadra
>> I encountered a strange problem with the use of quadrature points. In a
>> function I interpolate values of a given variable onto the quadrature points.
>> The following code worked fine for elements of type TRI:
>
> [code snipped]
>
> Here is a sample output
>>
>> -0.0101701> .0100975> Quadr
On Wed, Sep 30, 2009 at 9:23 AM, Petry Stefan wrote:
> Hello,
>
> I encountered a strange problem with the use of quadrature points. In a
> function I interpolate values of a given variable onto the quadrature points.
> The following code worked fine for elements of type TRI:
[code snipped]
He
Hello,
I encountered a strange problem with the use of quadrature points. In a
function I interpolate values of a given variable onto the quadrature points.
The following code worked fine for elements of type TRI:
unsigned int quadrature_points = 0;
double **Mx_o