[Nek5000-users] Element mesh mismatch with mesh in re2 file

[nek5000-users at lists.mcs.anl.gov]

Hi All,

Just wanted to let you all know that I have a resolution to this. Instead
of applying the boundary conditions in ICEM I applied the boundary
conditions in Cubit and this seemed to fix it. The strange thing is that I
have run a similar case where the boundary conditions were applied in ICEM
and the simulation ran just fine. Anyways, if you run in to this error
consider applying boundary conditions in Cubit instead of ICEM to solve an
element mesh mismatch error.

Cheers,

Tommy

On Fri, Aug 25, 2017 at 6:46 AM, <nek5000-users at lists.mcs.anl.gov> wrote:

> Hello Neks,
>
>
> I am trying to confirm a methodology of using icem to create an extruded
> hex20 mesh, converting it to hex27 in cubit, and then using exo2nek to
> create an re2 file. I am recreating the 3d annulus example problem for this
> test. I copied the rea, SIZE, and usr files from the example directory. I
> have also updated the usr file to convert the generic boundary conditions
> from the exo2nek conversion to the correct boundary conditions using the
> side set info. The files compile, but when I try and run the simulation I
> get an element mesh mismatch error. I have attached the log file of the run
> for reference. Any suggestions on how to fix this would be great.
>
>
> Thanks,
>
>
> Tommy​
>
> _______________________________________________
> Nek5000-users mailing list
> Nek5000-users at lists.mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/nek5000-users/attachments/20170825/802a3aa0/attachment.html>