On Thu, Jun 21, 2012 at 5:38 PM, Paul T. Bauman wrote:
> The FEInterface::is_vector_type() return type of bool is too
>> restrictive - we ought to be returning a type enum (TYPE_REAL or
>> TYPE_REAL_GRADIENT for now) to make it easier to extend later.
>>
>
> Will do. How does everyone feel about
Thanks for the feedback.
On Thu, Jun 21, 2012 at 3:04 PM, Roy Stogner wrote:
>
> Looking over this, only two gripes:
>
> The new FEInterface::shape should be a templated method to make it
> trivial to extend to RealTensor etc. This should be easy to fix after
> the fact; commit as-is.
>
Went ah
Looking over this, only two gripes:
The new FEInterface::shape should be a templated method to make it
trivial to extend to RealTensor etc. This should be easy to fix after
the fact; commit as-is.
The FEInterface::is_vector_type() return type of bool is too
restrictive - we ought to be returnin
On Thu, Jun 21, 2012 at 2:39 AM, Robert wrote:
>
> At least VTK supports also vector-valued solutions of arbitrary size.
>
It looks like the current VTKIO bypasses the build_solution_vector paradigm
and does its own thing. Which means the splitting of variables won't apply
to VTKIO. On the other
On Wed, Jun 20, 2012 at 05:17:59PM -0500, Paul T. Bauman wrote:
> 4. The main thing I wanted to make sure didn't ruffle feathers: vis formats
> don't seem to understand vector-valued quantities, so we have to write them
> out
> component wise. I've updated build_solution_names and build_solution_v
I've got a compiling version of a vector Lagrange finite element; the
vector part is entirely untested at this point. Patch can be found at:
http://users.ices.utexas.edu/~pbauman/fe_lagrange/lagrange_vec.patch and
new fe_lagrange_vec.C (to be dropped in src/fe) can be found at:
http://users.ices.ut
