This patch is committed - Exodus_IO_helper and Nemesis_IO_helper will now write
"zero" IDs to their respective output files.
I also committed a utility "src/apps/meshid.C" that will allow users to remap
IDs in their solution files as needed. I have not tested this extensively but
it appears to
This patch is committed - Exodus_IO_helper and Nemesis_IO_helper will now write
"zero" IDs to their respective output files.
I also committed a utility "src/apps/meshid.C" that will allow users to remap
IDs in their solution files as needed. I have not tested this extensively but
it appears to
Actually I may have spoken too soon. This is actually a fair amount of work to
do correctly. One has to take care to read in not only the mesh, but the
solutions(s), scalar values and other metadata in the mesh. Some of this
handled well in libMesh, some not so much. I might explore "hacking
Yeah - I can do that. I was going to write a script that did the inverse of
that anyway to fix our own tests. I'll make it work both directions.
Cody
On Aug 8, 2011, at 2:05 PM, Roy Stogner wrote:
>
> On Mon, 8 Aug 2011, Cody Permann wrote:
>
>> Libmesh has been distributing and running wit
On Mon, 8 Aug 2011, Cody Permann wrote:
Libmesh has been distributing and running with the new ExodusII library for
over a month now and I haven't seen any issues on
the mailing list regarding the new version so I'm preparing the next patch in
this set.
IMPORTANT:
This change could potentia
Libmesh has been distributing and running with the new ExodusII library for
over a month now and I haven't seen any issues on the mailing list regarding
the new version so I'm preparing the next patch in this set.
IMPORTANT:
This change could potentially break users doing regression testing wi
