[Paraview] Ensight and FLUENT

[Bastil2001 at yahoo.de]

Nathanael Inkson schrieb:
> Hi,
>  Actually I never got the Ensight writer to work. Is it functional?#
>   
What do you mean with "Ensight writer"? I export results in FLUENT to
Ensight so I use the FLUENT Ensight writer. This works e.g. for FLUENT
Tutorial 1. Afterwards you can read this into Paraview using the
Paraview Ensight reader... Sometimes Paraview crashes wile reading the
data (but not the mesh), eg. FLUENT Tutorial 6.

Regards
> I'll have a look at the tutorial sometime later.
> Maybe we could work to solve the problem.
> To be honest I kind of gave up on paraview. 
> I extracted the code I needed from it and developed some of my own code,
> because for me the behaviour of the surfaces and boundaries was what I
> really needed. But I should be able to work backwards and put what I
> have done back into paraview, but it will never be as functional as I
> would have wanted because of the way paraview is constructed.
> I'd be keen to sort out the problems with paraview and fluent files
> though as it is useful and free!
>
> Best Regards
>  
> Dr. Nathanael Inkson,
>  
> Computational Fluid Dynamics Developer,
> Digital Flow Solutions,
>
>   
>
>    
>
>  mob:  +  44 7872010167
>
> web:   wirthresearch.com
>
>  
> -----Original Message-----
> From: Bastil2001 at yahoo.de [mailto:Bastil2001 at yahoo.de] 
> Sent: 27 October 2008 18:35
> To: Nathanael Inkson
> Subject: Re: [Paraview] Ensight and FLUENT
>
> I too have the problem of crashes though. If I load a multiblock fluent
> file, merge the blocks and then use a filter. The problem is the
> datasets are too large to replicate the problem simply.
>
> I have much "simpler" crashes. Nathanael, can you export the FLUENT
> Tutorial No. 6 as an Ensight file and load that into Paraview? I always
> get a segfault as soon as I load more than the pure mesh but one or more
> additional result variable, e.g. static pressure.... This happens for
> all the four FLUENT export formats cell/node ascii and binary. Can you
> reproduce this?
>
> Regards
>
> Nathanael Inkson schrieb:
>   
>> Hi, 
>>   I have used the fluent reader quite a bit. Basically the face zone
>> information is completely ignored. The way that the Ensight reader
>> handles fluid zones is to treat them as extra cell blocks. This could
>> also been done with the Fluent reader with a small amount of extra
>>     
> code.
>   
>> I might do this sometime in the future, given enough time. However,
>>     
> I'm
>   
>> very busy at the moment! I have partially done it though. So I will
>> follow up on this soon.
>>
>> I too have the problem of crashes though. If I load a multiblock
>>     
> fluent
>   
>> file, merge the blocks and then use a filter. The problem is the
>> datasets are too large to replicate the problem simply.
>>
>> Best Regards
>>  
>> Dr. Nathanael Inkson,
>>  
>> Computational Fluid Dynamics Developer,
>> Digital Flow Solutions,
>>
>>   
>>
>>    
>>
>>  mob:  +  44 7872010167
>>
>> web:   wirthresearch.com
>>
>>  
>> -----Original Message-----
>> From: paraview-bounces at paraview.org
>> [mailto:paraview-bounces at paraview.org] On Behalf Of Berk Geveci
>> Sent: 27 October 2008 01:40
>> To: Bastil2001 at yahoo.de
>> Cc: paraview at paraview.org
>> Subject: Re: [Paraview] Ensight and FLUENT
>>
>> I don't know the Fluent format well so excuse my ignorance. Does the
>> Fluent format specify surfaces as separate parts/zones? It sounds like
>> the reader does not allow you to import them, correct?
>>
>> As for the Ensight crash problems. Please send us example files that
>> demonstrate the crashes so that we can track them down.
>>
>> -berk
>>
>> On Fri, Oct 24, 2008 at 11:22 AM, Bastil2001 at yahoo.de
>> <Bastil2001 at yahoo.de> wrote:
>>   
>>     
>>> Hi All,
>>>
>>> I have spent some more time to use paraview for FLUENT now with the
>>> latest 3.4.0 I still have problems with import:
>>>
>>>    * direct import works fine mostly. However, I am unable to extract
>>>      surface zones. There is no way to do postporcessing for external
>>>      flows that way. Is there any way to split the surface?
>>>    * Using Ensight imports surface parts. This allows postprocessing.
>>>      However, I get sementation faults quite often with that. E.g.
>>>      FLUENT tutorial 6 exported as Ensight (node based, binary or
>>>      ascii) gives a segfault for me. Am I the only one with this
>>>     
>>>       
>> problem?
>>   
>>     
>>> Maybe someone out there has some tips? Thanks.
>>>
>>> BastiL
>>> _______________________________________________
>>> ParaView mailing list
>>> 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
>>
>>   
>>     
>
>
>