On Tue, Jun 24, 2014 at 12:08 PM, John Peterson wrote:
> On Tue, Jun 24, 2014 at 11:51 AM, Sahai, Amal wrote:
>> I think I've been able to solve the problem by reading the external mesh by
>> directly using the mesh object through mesh.read(string) instead of using
>> the ExodusII_IO object.
>
On Tue, Jun 24, 2014 at 11:51 AM, Sahai, Amal wrote:
> I think I've been able to solve the problem by reading the external mesh by
> directly using the mesh object through mesh.read(string) instead of using the
> ExodusII_IO object.
There's no difference between these two ways of reading the Me
John Peterson
Cc: [email protected]
Subject: RE: [Libmesh-users] Libmesh Gridgen import
I have uploaded the mesh on:
https://docs.google.com/file/d/0BzY4xZs53VOLMWUzT0Y2d0NHSUk/edit
Also, I was using the following code to check the mesh by accessing the
different properties:
:cout << "Side : " << side << "belongs to the interior." <<
std::endl;
}
}
The strange thing is, this loop never gets entered.
Regards
Amal
________
From: John Peterson [[email protected]]
Sent:
On Tue, Jun 24, 2014 at 10:40 AM, Sahai, Amal wrote:
> I have a few questions regarding importing ExodusII meshes created in Gridgen
> to Libmesh. I have created a simple structured mesh in Gridgen with the .exo
> format. Also, I made sure that the boundary conditions were defined as side
> set
I have a few questions regarding importing ExodusII meshes created in Gridgen
to Libmesh. I have created a simple structured mesh in Gridgen with the .exo
format. Also, I made sure that the boundary conditions were defined as side
sets. I face no problems reading the mesh using the ExodusII_IO o
