On Thu, Oct 25, 2012 at 3:24 PM, Roy Stogner wrote:
>
> Assuming you've tested it, I don't see anything wrong.
>
Sorry, should've said I ran adaptivity_ex3 in dbg mode and verified the
files that are output open correctly in ParaView and the values jive with
what's actually in the ErrorVector.
r
On Thu, 25 Oct 2012, Paul T. Bauman wrote:
> Attached patch adds capability for ErrorVector::plot_error to write
> to ExodusII format. Includes adding example usage to adaptivity_ex3.
> OK for trunk?
Assuming you've tested it, I don't see anything wrong.
---
Roy
Seems fine to me and passes all my tests.
Derek
On Thu, Oct 25, 2012 at 2:14 PM, Paul T. Bauman wrote:
> Thanks all.
>
> Attached patch adds capability for ErrorVector::plot_error to write to
> ExodusII format. Includes adding example usage to adaptivity_ex3. OK for
> trunk?
>
> Best,
>
> Paul
Yes, you can do this with Exodus. Just store it in a CONSTANT MONOMIAL
field and call write_element_data(). It will come out as an element field
that Paraview (or anything else that reads Exodus) can view.
Derek
On Thu, Oct 25, 2012 at 12:18 PM, Paul T. Bauman wrote:
> Has anyone done any vis
> capability, but wanted to double check before I start up the discussion of
> implementing this capability (I have some suggestions). I'd prefer not to
> hack it up as a nodal quantity since most visualization tools can
> differentiate between nodal and element quantities.
FWIW, some of the
