On Thu, Jun 22, 2017 at 5:19 PM, Vikram Garg <vikram.v.g...@gmail.com> wrote:
> Hello Laura, > IIRC, the exact solution class is to enable comparisons > of a numerical solution with an analytic solution. Since you are seeking to > The meshdiff.C app is intended for exactly the purpose it's being used for here. However, when the L2 and H1 errors are printed on screen, they are the very > same as the norm of the solution on the fine mesh. This definitely sounds like a bug, but I'm not sure what it might be off the top of my head. Some questions: 1. Does the meshdiff.C program work for your case as-is? Does it give the same (wrong) result? 2. Are you sure about the system and variable names in the exact_sol.compute_error() call? 3. Are you sure about the variable indexes for both systems? It looks like they are hard-coded to 0 in the calculate_norm() calls... 4. Would it be possible for you to share the data files somehow so we can try to reproduce the issue? -- John ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
