Sorry that I just realized that I wasn't clear in the boundary conditions:
I fixed the MIN_X side of the model, and applied -Z traction on the surface
of MAX_X. The resultant displacement on the MAX_X surface is about -3e-3 in
ABAQUS, but only -2.2e-3 in the libmesh model. The other directions and
Dear all,
When I use `MeshTools::Generation::build_square`, I obtain a mesh with:
enum BOUNDARY_ID {
BOUNDARY_ID_MIN_Y = 0,
BOUNDARY_ID_MAX_X = 1,
BOUNDARY_ID_MAX_Y = 2,
BOUNDARY_ID_MIN_X = 3,
};
However, I noticed that
MeshBase::const_node_iterator nodeit =
m
Hi Roy,
Thanks for your comments, I've replied below:
On Tue, Dec 4, 2018 at 5:01 PM Stogner, Roy H
wrote:
>
> On Tue, 4 Dec 2018, David Knezevic wrote:
>
> > I use NodeElems with GhostingFunctor to couple unconnected nodes (i.e. I
> > attach NodeElems to the nodes that I want to couple), and t
On Tue, 4 Dec 2018, David Knezevic wrote:
> I use NodeElems with GhostingFunctor to couple unconnected nodes (i.e. I
> attach NodeElems to the nodes that I want to couple), and this works well.
> However, I realized that this approach requires me to set the processor_id
> in the NodeElem to matc
I use NodeElems with GhostingFunctor to couple unconnected nodes (i.e. I
attach NodeElems to the nodes that I want to couple), and this works well.
However, I realized that this approach requires me to set the processor_id
in the NodeElem to match the processor_id of the Node that it points to, as
On Tue, Dec 4, 2018 at 1:15 PM Amneet Bhalla wrote:
> Ok, I just copied the original .msh file to a file with a different name
> and it works. Maybe it was a strange OS thing.
>
Yeah, the file you shared worked OK for me as well FWIW.
--
John
___
Li
Ok, I just copied the original .msh file to a file with a different name
and it works. Maybe it was a strange OS thing.
On Mon, Dec 3, 2018 at 10:29 PM Amneet Bhalla wrote:
> Hi Folks,
>
> I am trying to read a simple GMSH file with libMesh, but I get the
> following error:
>
> Assertion `in.goo
