On 03/06/2014 11:30 PM, John Peterson wrote:
On Thu, Mar 6, 2014 at 9:12 PM, David Knezevic
<dkneze...@seas.harvard.edu <mailto:dkneze...@seas.harvard.edu>> wrote:
I'd like to write out element-based data to an exodus file (again
related to discontinuous visualization). There is a function
ExodusII_IO::write_element_data in ExodusII_IO, but it's not clear
to me
how to use it?
I'd like to use it in the same way as
ExodusII_IO::write_nodal_data, but
it doesn't seem to work that way. ExodusII_IO::write_element_data
doesn't even take a filename, so I'm confused about what it's role is
supposed to be.
You can use it to write out constant monomial variables, right?
Did you need to write out some higher-order elemental data?
Yeah, I just want to write out monomial variables. I can use
write_discontinuous_exodusII for that too, but that generates a "broken
mesh", since it duplicates all the nodes to allow a discontinuous
solution. I want a discontinuous plot of monomial variables on a
non-broken mesh, so I figured ExodusII_IO::write_element_data might the
right function for that job?
Do you have a code snippet for using it to plot monomials? If I try to
call it directly, I just get an error due to the
!exio_helper->opened_for_writing assertion...
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
