Thank you John for looking at it! I have been reading abaqus_io.C and think I found out why.
There are two ways for ABAQUS to define the surface and only #1 is supported by libMesh now: 1) By specifying elem_id, side_id. This is the currently supported one, for example "391, S2" 2) By specifying elemset_name, side_id. This is NOT currently supported, and looks like "Elset_1, S3". This will probably be internally expanded to the format like #1: it will find all the elem_ids in the element set of Elset_1, and use S3 for all of them. We added a few lines and this now works with the #2 as well. Should I create a ticket and a pull request? Best, Shawn On Wed, Oct 30, 2019 at 6:07 AM John Peterson <jwpeter...@gmail.com> wrote: > Hi Yuxiang, > > I will try and take a look at this when I get a chance... it's likely that > there is a bug in our Abaqus reader. There is a certain amount of variation > allowed in the formatting of Abaqus files, and we may not support exactly > the format you are using. > > -- > John > > > On Tue, Oct 29, 2019 at 3:26 PM Yuxiang Wang <yw...@virginia.edu> wrote: > >> Dear all, >> >> I noticed that whenever I have *Surface in the ABAQUS .inp file, libmesh >> cannot read it. I thought this was implemented according to here: >> >> https://libmesh.github.io/doxygen/classlibMesh_1_1AbaqusIO.html#a2a125c1845edc4c3a6fad266fc76cbfd >> >> >> I have a very short dummy mesh (9 nodes in a unit cube) and a short >> libmesh >> C++ codethat I tested with (attached). whenever I run this with the >> example >> file, it says: >> >> Stream is bad! Perhaps the file: testcube.inp does not exist? >> >> Could anyone please help comment? >> >> Best, >> Shawn >> > > -- Yuxiang "Shawn" Wang, PhD yw...@virginia.edu +1 (434) 284-0836 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
