Re: [Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-16 Thread Derek Gaston
Might want to make this a real error and not an assert…. this isn't in a performance critical section…. Derek On May 16, 2012, at 11:00 AM, Roy Stogner wrote: > > On Wed, 16 May 2012, Roy Stogner wrote: > >> Hmm... indeed, it looks like all_second_order() is only implemented >> for "flat" mes

Re: [Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-16 Thread Roy Stogner
On Wed, 16 May 2012, Roy Stogner wrote: > Hmm... indeed, it looks like all_second_order() is only implemented > for "flat" meshes but doesn't even contain a libmesh_assert() testing > for refinement. I don't have time to implement a > refinement-compatible all_second_order() right now, but I can

Re: [Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-16 Thread Roy Stogner
On Wed, 16 May 2012, Yusuke Sakamoto wrote: > I looked for the source of the error, and found that it is due to the > fact that I call Mesh::all_second_order() after refining the mesh by, > MeshRefinement::uniformly_refine (n_refinements). It corrupts the > internal data structure or something in

Re: [Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-16 Thread Yusuke Sakamoto
I looked for the source of the error, and found that it is due to the fact that I call Mesh::all_second_order() after refining the mesh by, MeshRefinement::uniformly_refine (n_refinements). It corrupts the internal data structure or something in EquationSystems object. It doesn't even save the

Re: [Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-16 Thread Derek Gaston
Quadrature rule should really have nothing to do with it. If you are really passing in the _exact_ same solution as the one you are computing it should compute zero error (to within machine precision). Can you create a small example solving something simple that demonstrates the problem? Dere

Re: [Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-15 Thread Yusuke Sakamoto
Just reply to myself, I realized that as long as vr, vz, and p values are the same for two different equation systems, the error should be zero, whether the domain is normal 2D or axisymmetric 2D. The source of the error is that the quadrature order used in ExactSolution to compute the referenc

[Libmesh-users] Error Estimates in Axisymmetric Domain

2012-05-14 Thread Yusuke Sakamoto
Dear all, I am trying to carry out the convergence analysis on the 2D axisymmetric mesh. The problem is a simple Stokes flow. Before comparing the result to the reference mesh, I compared the solution to itself. // Compare the computed solution to the reference solution ExactSolution ExSo