Roy, This works for me. Maybe it's because I start with an Exodus file in the beginning that has sidesets declared on it. But if I go through the following with meshtool... everything works fine:
meshtool -d 3 -i input.e -o out.xda meshtool -d 3 -i out.xda -o out.e After all of this out.e is essentially identical to input.e... including having sidesets defined on it that I can see in Ensight. Can you send me a small xda file that fails for you? Derek On Mon, Dec 8, 2008 at 11:14 AM, Derek Gaston <[EMAIL PROTECTED]> wrote: > Weird we have many people using this stuff all day long. I'll take a look > at meshtool this afternoon. > > Derek > > Sent from my iPhone > > > On Dec 8, 2008, at 11:04 AM, Roy Stogner <[EMAIL PROTECTED]> wrote: > > >> On Mon, 8 Dec 2008, Derek Gaston wrote: >> >> You could also use Exodus... I modified the Exodus writer to correctly >>> write out the boundary ids >>> >> >> For some definition of "correctly", anyway. ;-) With the SVN head, >> my attempt to run "meshtool -d 2 -i one_tri.xda -o one_tri.exd" dies >> in ExodusII_IO_Helper::write_sidesets() with an "Error writing sideset >> parameters". >> --- >> Roy >> > ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
