[Paraview] Paraview 3.1.0 - ensight gold problem

[Adrian Magda]

Hi Amy,

Thanks a lot for your answer.

1 - The hexa8 cells are in the part1 and quad4 in the part2 so they do 
not belong to the same part.

2 - Of course as the quad4 cells are the boundary conditions they will 
share a common face with the hexa8 cells. Assuming that this is wrong 
than a similar behavior should be seen for all other walls (instead we 
see this only for ONE single wall ). More how it is possible that this 
boundary quad4 elements will affect the inner flow? I mean I observed 
very different flow pattern for the full geometry and the part1 geometry 
(separated applying the "Extract Datasets" filter)? Have you also 
noticed that ? There should be whatsoever no difference between them, no?

Also in ensight there is no problem observed when i postprocessing this 
case.

Best regards
Adi

Amy Squillacote wrote:
> Hi Adrian,
>
> I was able to download the data from the link you sent. I do see the 
> same results as you show in the link you included in the email 
> conversation. I have a few questions for you.
>
> * Are the hex8 and quad4 cells in the same part?
> * Are the hex8 and quad4 cells supposed to share a common surface 
> plane? It looks like you have exactly the same exterior surface 
> regardless of which part you choose, which would explain the 
> flickering you see.
>
> - Amy
>
> Adrian Magda wrote:
>> Hi Samuel
>>
>> Thanks a lot for your answer.
>>
>> Both hex8 and quad4 store temperature as cell data. You are right the 
>> quad4 elements
>> are overlaying the hex8 surface.
>>
>> If there is only a visual competition between the display from each 
>> part I think that should not effect the inner flow far from the wall 
>> no ?
>>
>> For you all this works without problem ?
>>
>> All the best
>> Adrian
>>
>> On 9/30/07, *SamuelKey* <samuelkey at comcast.net 
>> <mailto:samuelkey at comcast.net>> wrote:
>>
>>     Greetings Adrian,
>>
>>     I use an EnSight Gold format with "parts," unstructured grids,
>>     multiple
>>     element types.
>>
>>     Is Temperature point or cell data for the hex8 elements?
>>
>>     Is Temperature point or cell data for the quad4 elements?
>>
>>     In my experience, each "part" is a separate displayable object. 
>> While
>>     the nodal points appear "unique" to each "part" in the ParaView data
>>     set, the nodal points have the exact same coordinates since the 
>> quad4
>>     are overlaying the hex8 surface (at least, in my data sets they
>>     would).
>>
>>     With quad4's overlaying the hex8 surface being coincident, I 
>> think you
>>     may seeing a visual competition between the display from each part?
>>
>>     Regards,
>>
>>     Sam Key
>>
>>     Adrian Magda wrote:
>>     > Hi all Paraview users,
>>     >
>>     > I am using Paraview to plot my cfd results. I am using ensight 
>> gold
>>     > binary format. I can write and read the data with no problem, 
>> but it
>>     > seems paraview interprets the things wrong.
>>     >
>>     > The geometry file is divided in two part one containing the 
>> internal
>>     > flow (hexa8, unstructured)  and a part containing the boundary 
>> file
>>     > (quad4 unstructured elements).
>>     >
>>     > The problem is that always the temperature on the North wall of my
>>     > geometry seems to mixed with data from both hexa8 (first
>>     elementh near)
>>     > the wall and quad4 element (placed on the hexa8 wall). More if i
>>     do a
>>     > cut trough the geometry and display the temperature the 
>> temperature
>>     > profile is completely wrong
>>     > On the other hand if i use "Extract Datasets" option i can see the
>>     > correct Temperature profile on the inner flow and on the
>>     boundary area
>>     > for each part separately.
>>     > In order to check out more the encounterdproblem i decided to
>>     export a
>>     > simple OpenFOAM 3d case (20*20*20) (the 2d (in one direction 
>> only 1
>>     > cell) works with no probblem) and also i noticed strange things.
>>     For
>>     > exporting i used the included foamToEnsight module.
>>     >
>>     > Last and final try was to check the .case file in ensight8 and
>>     none of
>>     > the problems mentioned above were noted.
>>     >
>>     >
>>     > Did anybody else have had such problems ? There is any way
>>     around this?
>>     >
>>     >
>>     > Adrian
>>     >
>>     >
>>     >
>>     >
>>     >
>>     
>> ------------------------------------------------------------------------
>>     >
>>     > _______________________________________________
>>     > ParaView mailing list
>>     > ParaView at paraview.org <mailto:ParaView at paraview.org>
>>     > http://www.paraview.org/mailman/listinfo/paraview
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
>>   
>