Looks like for now you have to check out the source...
http://sourceforge.net/scm/?type=cvs&group_id=211609
(on a side note... I just used copy and paste on my iPhone for the
first time... And it was everything I thought it would be ;-)
Derek
Sent from my iPhone
On Jul 27, 2009, at 5:20 PM,
On Tue, Jul 28, 2009 at 9:12 AM, Derek Gaston wrote:
> No... I still haven't fixed the writer so that it doesn't blow up when
> trying to write a block 0 but I do have good Exodus related news:
> The full SEACAS set of tools has been open sourced:
> http://sourceforge.net/projects/seacas/
Tha
No... I still haven't fixed the writer so that it doesn't blow up when
trying to write a block 0 but I do have good Exodus related news:
The full SEACAS set of tools has been open sourced:
http://sourceforge.net/projects/seacas/
This includes nem_slice and nem_spread which can take a seri
That's another hack that works... glad you found one ;-)
If you are looking for a free visualizer that reads Exodus and handles
Quad9... use Paraview: http://www.paraview.org
Derek
On Jul 27, 2009, at 8:03 AM, Boyce Griffith wrote:
> Hi, Derek --
>
> Thanks for the explanation --- I hacked th
Hi, Derek --
Thanks for the explanation --- I hacked the Exodus II I/O to increment
all block numbers by 1 and it seems to work. (Next problem is that
VisIt doesn't seem to be able to handle QUAD9 elements, but that's a
problem for another mailing list...)
Thanks,
-- Boyce
Derek Gaston wrot
The issue is that Exodus blocks start numbering at 1 instead of
zero You can loop over the elements and set their subdomain ID to
one to fix that error... But unfortunately you will probably run into
the next problem which is that Exodus boundary IDs start at 1 as well...
The real fix i
Hi, Folks --
I am trying to get libMesh to output to an Exodus II file. I am using a
recent pull of the SVN version of libMesh so that I can use libMesh with
PETSc 3.0.0.
(By the way, I don't really care whether it is Exodus II or not --- I am
just trying to output data in a format which can
