On Mon, 3 Jan 2011, Cody Permann wrote:
> I have confirmed that there is indeed a problem with sidesets on 3D
> meshes when using AMR. Some of the sidesets are completely
> incorrect after a single refinement step. The problem can be
> reproduced using some of the 3D examples (ex14 or ex15).
I have confirmed that there is indeed a problem with sidesets on 3D meshes when
using AMR. Some of the sidesets are completely incorrect after a single
refinement step. The problem can be reproduced using some of the 3D examples
(ex14 or ex15). On a regular mesh some of the sidesets will form
I recently installed the release 0.7.0.3 (as well as the svn version). I
tried to run a code developed for previous releases and I had some
problems with boundary_id.
The code
if( elem->neighbor(s) == NULL )
{
short int side_id =
mesh.boundary_info->boundary_id(elem,s);
.
}
corr
