> From: fried...@gmail.com
> Date: Sun, 21 Aug 2016 16:29:33 +
> Subject: Re: [Libmesh-users] what is the deal with TypeVector size()?
> To: marchy...@hotmail.com; royst...@ices.utexas.edu
> CC: libmesh-users@lists.sourceforge.net
&g
--
> > Date: Sun, 21 Aug 2016 10:17:41 -0500
> > From: royst...@ices.utexas.edu
> > To: marchy...@hotmail.com
> > CC: libmesh-users@lists.sourceforge.net
> > Subject: Re: [Libmesh-users] what is the deal with TypeVector size()?
> >
> >
>
> Date: Sun, 21 Aug 2016 10:17:41 -0500
> From: royst...@ices.utexas.edu
> To: marchy...@hotmail.com
> CC: libmesh-users@lists.sourceforge.net
> Subject: Re: [Libmesh-users] what is the deal with TypeVector size()?
>
>
> O
On Sun, 21 Aug 2016, Mike Marchywka wrote:
It apparently is a deprecated way to get a norm which would seem at odds
with both math and programming conventions.
That is in fact why it's deprecated, yes. It's been deprecated long
enough that we should probably remove it entirely in the next
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
