It apparently is a deprecated way to get a norm which would seem at odds
with both math and programming conventions. Further, AFAICT, it is always
3D forcing an anyone wanting to use it would have to know otherwise how many
matter or just loop over wasted zeroes.
I ran into this with dphi and trying to take the size of dphi[][] although this
did
appear to evaluate to a vector.
So far however everything else is working much better than I had hoped.
I have a grid with holes in it for electrodes and a simple drift diffusion model
with kluged expressions for things I did not want to think about while learning
the method and the code I don't
have a model good enough to check quantitatively yet but it looks like I
may be able to get that far :)
By far the most confusing thing was iterating over dphi grad components.
Almost all of the spurious ones were denormals with a few confusing spikes that
messed up the results but AFAICT never a segfault. The way I finally found out
about it was invoking with -fp_trap which threw instantly even though results
would have looked ok. Then it was easy to find the denormals stepping through
the first iteration.
Any idea why the junk near dphi vector would be denormal? Haven't thought
about memory map much and IIRC the binary dump did not suggest they were any
memory init pattern to flag that problem.
Thanks.
note new address
Mike Marchywka 306 Charles Cox Drive Canton, GA 30115
2295 Collinworth Drive Marietta GA 30062. formerly 487 Salem Woods Drive
Marietta GA 30067 404-788-1216 (C)<- leave message 989-348-4796 (P)<- emergency
------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
