[Nek5000-users] Connectivety

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

Hi Paul,
Yes, it makes perfect sense.
Cheers,
Antonios

nek5000-users at lists.mcs.anl.gov wrote:
> 
> Hi Antonios,
> 
> Aleks is correct.  The "E-E" connectivity in the .rea BC info
> is ignored by nek.
> 
> Connectivity is determined strictly from the mesh topology
> inferred from the data in the .map file.
> 
> The same is not true, however for periodic bcs -- this information
> must come from the "P-P" pairing in the .rea bc info.
> 
> Does this make sense?
> 
> Cheers,
> 
> Paul
> 
> 
> On Thu, 9 Dec 2010, nek5000-users at lists.mcs.anl.gov wrote:
> 
>> Hi Antonios,
>>
>> I could be wrong but I think that the only connectivity information
>> that Nek5000 need comes from global vertexi element numbering
>> genereated by .map file which is in turn produced by running genmap on
>> .rea file
>>
>> Best,
>> Aleks
>>
>>
>> On Thu, 9 Dec 2010, nek5000-users at lists.mcs.anl.gov wrote:
>>
>>> Hello Paul,
>>> I have a question about the connectivity of the elements.
>>> In the old rea file format (which we convert to the new binary with
>>> reatore2) we have listed the Element geometrical date and after that the
>>> Boundary conditions and connectivity data.
>>> My question is whether the connectivity of the elements stated there is
>>> actually used or it is somehow re-computed while the code runs based on
>>> the node coordinates. I am talking specifically about the connectivity
>>> between the elements, not the boundary conditions with the "outside
>>> world".
>>> Best regards,
>>> Antonios
>>>
>>> -- 
>>>
>>> ---------------------------------------------------------------------------------------------
>>>