On Tue, 16 Sep 2008, Franz Rammerstorfer wrote:
> Maybe its just a comparison fault:
>
> line 512: if(error_vals[4] < norm) { error_vals[4] = norm; }
> variable-types: norm = Real, error_vals = std::vector<Number>
Yes; we accepted a patch a little while ago to add new error
calculation norms to ExactSolution, but I guess nobody remembered to
check the patch for --enable-complex compatibility.
Hmm... does anyone see why error_vals needs to be a vector of Number
at all? It looks to me like if any of its entries end up with
imaginary parts, that's a bug.
---
Roy
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
