Dear all, I think there is a small bug in reading Nemesis mesh files: Nemesis_IO::read and Nemesis_IO::write use Nemesis_IO::construct_nemesis_filename for constructing the name of the file on a certain processor but if you want to use Meshbase::read which uses Unstructuredmesh::read (line 482 on oxygen docs) the Unstructuredmesh::read looks for a different file name format.
For example Nemesis_IO::read will look for mesh.nem.10.00 while UnstructuredMesh::read will generate an error on the get go because it looks for mesh.nem.10.0 . Best, Ata ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
