Re: [Libmesh-users] size limit for exodus?

[John P. <jwp...@gm...>]

On Thu, Jun 7, 2012 at 8:47 AM, Paul T. Bauman <ptb...@gm...> wrote:
> On Thu, Jun 7, 2012 at 9:42 AM, robert <rob...@un...> wrote:
>
>> is there a size limit for writing exodus files and reading them with
>> paraview?
>>
>
> To my knowledge, you are only limited by the memory on your computer. I've
> used ParaView to visualize solutions with 20+ variables and several million
> elements on my laptop no problem.
>
> TetGenIO TG(mesh);
>> TG.read ("main_ldio.1.ele");
>> mesh.write("tryfunwrite.e");
>>
>
> The code is incomplete, but you're writing the mesh (which I'm assuming is
> a Mesh object) and that will be written in ``libMesh" format. If you want
> Exodus, you need to use an ExodusII object.

No, actually what he's done here is fine for producing an Exodus file.
 The mesh.write function tries to be smart like that...

I vaguely remember a "big" or "large" option being available for
ExodusII files, at least when writing from cubit?

I'm having a hard time finding the ExodusII documentation at the
moment, but it may be possible you are bumping up against this limit?

Depending on how old your paraview is, you might also just try getting
the latest version and see if that helps...

-- 
John