[Nek5000-users] genmap error: infinite loop, not connected, in rec_bisect

nek5000-users at lists.mcs.anl.gov nek5000-users at lists.mcs.anl.gov
Thu Jul 1 22:17:20 CDT 2010


First question is whether genmap sees the bcs the  way
you expect it to do so ?

Paul


On Thu, 1 Jul 2010, nek5000-users at lists.mcs.anl.gov wrote:

>
>
> Hi Paul,
>
>
>
> Could you provide some insight into this problem with the periodic bondary condition as described below?  This error occurs when running genmap.
>
>
>
> Thanks,
>
> Michael
>
>
> ----- Original Message -----
> From: nek5000-users at lists.mcs.anl.gov
> To: nek5000-users at lists.mcs.anl.gov
> Sent: Tuesday, June 29, 2010 1:59:13 PM GMT -06:00 US/Canada Central
> Subject: Re: [Nek5000-users] Periodic Mismatch 1
>
>
> Hi,
>
> I was able to solve this by removing the element face count column.
>
> I now run into the following issue shown below.  I was able to find the subroutine spec_bis_conn where this error occurs.
> I believe this has to do with the periodic faces I have set up. My question is whether the periodic faces need to be continuous:
>
> For example, the geometry is similar to fluid flow over a flat plate on both sides. The fluid is periodic, but separated by the solid
> thickness (this is a Conj HT problem). Essentially there is a "gap" in the periodic fluid portion if you can imagine.  I saw a note in
>   the routine that says something like "ensure that all graphs are connected", not sure if this is what it means.  I tried making the fluid
> periodic on only one side of the plate and it worked, however when I make the other side (bottom of the plate) periodic with itself
> I get the following error. Any thoughts?  Thanks - Michael M.
>
> start rec_bisect:        2006
>  done:    0.0%
>  done:    1.0%
>  done:    2.0%
>  done:    3.0%
>  infinite loop
>  not connected           1          63           1           0
>  not connected           1          32           2           0
>  not connected           1          16           3           0
>  not connected           1           8           4           0
>  not connected           1           4           5           0
>  done:    4.0%
>  not connected          13          31           6           0
> Segmentation fault (core dumped)
>
>


More information about the Nek5000-users mailing list