This "const FEMContext &context" idea would involve a little work, but
not a huge inconvenience. I don't understand the big picture, but
something like this will be quite confusing if the corresponding class
data still exists, that is, if FEMSystem.elem still exists many mistakes
will be made
Nasser Mohieddin Abukhdeir wrote:
> This "const FEMContext &context" idea would involve a little work, but
> not a huge inconvenience. I don't understand the big picture, but
> something like this will be quite confusing if the corresponding class
> data still exists, that is, if FEMSystem.elem
On Sun, 28 Sep 2008, Nasser Mohieddin Abukhdeir wrote:
> This "const FEMContext &context" idea would involve a little work, but not a
> huge inconvenience. I don't understand the big picture,
Primarily: multithreading.
I'd like to make FEMSystem automatically use Ben's TBB threading code,
bu
On Sun, 28 Sep 2008, Nasser Mohieddin Abukhdeir wrote:
> I was thinking about one of those approaches, but it seems like the path of
> least resistance is to run postprocessing code afterwards that just uses FEM
> to solve N stationary problems, where N is the number of timesteps from the
> ma
I was thinking about one of those approaches, but it seems like the path
of least resistance is to run postprocessing code afterwards that just
uses FEM to solve N stationary problems, where N is the number of
timesteps from the main simulation. I am already tight on resources
(during the main
On Sat, 27 Sep 2008, Derek Gaston wrote:
> Now, for C1 continuous elements (such as Clough-Toucher's,
> Hermite's, etc.) you should be able to get the value of the gradient
> at the nodes pretty easily: it should be in your solution vector.
> Obviously, I've never used these elements or I would k
I found a few references on gradient recovery, seems a bit expensive to
do concurrently in my simulations (both directly or through some
Galerkin method), so I'll just do it a posteriori as a separate FEM
run. I found a decent paper describing direct and Galerkin methods.
Switching to Hermite
David's right
On Sep 27, 2008, at 11:26 AM, David Knezevic wrote:
> Well, the problem I think is that the gradients are not well-defined
> at
> node points, since finite element solutions are piecewise polynomials.
Yep.. for your normal Lagrange elements the gradient is undefined on
the
Well, the problem I think is that the gradients are not well-defined at
node points, since finite element solutions are piecewise polynomials.
One way to get an answer (John suggested this to me once) is to compute
the gradients at quadrature points and then do an L2 projection of that
solution
Hi:
For some post-processing tasks I need to get access to gradients of
variables not at the interior quadrature points, but on the nodes
themselves. It seems like a simple enough thing to do, but I cannot
find any existing functionality in Libmesh to do it. I trying to look
through the s
10 matches
Mail list logo
