Block Indices vanish???
I load multiple .encas data files from Fluent then I Filter\Extract Block for each case in order to be able to choose which zone of the geometry I want to plot.
I don't know why at some point the list of Block Indices disappear in the Properties tab of Extract Block. See Fig.1, the Block Indices are all there, everything is ok. Then see Fig.2, they vanished!
I typically load 2 or 3 .encas. Sometimes this strange behavior happens for 1 or 2 Extract Block, sometimes everything stays flawless, sometimes it happens for every dataset. It's pretty random and very annoying. I get nervous never knowing when I'm going to loose the Block Indices. Reset button and Zoom To Data don't help.
After a really quick search, I couldn't find any examples of this specific file format.
Can you share a really small example file and/or folder, so that I or anyone else can try this out?
Because without being able to test this myself, my guesses are:
.encas is the file format outputed by Fluent when you choose to export data to Ensight Case Gold. It's the most convenient file format for transient results from Fluent to Paraview.
In Paraview, I use the Ensight Files reader. There is no option for choosing which blocks are imported, you only get to click which variables you want to import. All the blocks (the zones in Fluent) are 'hidden' in the data. Then with the Extract Block filter you get to choose which block (zones) are extracted.
The weird behavior happens when I do a lot of manipulations such as legend modifications, calculators, programmable filters, multiple views, etc. It's like Paraview loses track a little bit at some point...
I don't have access to Fluent nor EnSight, so there isn't much I can do there :)
Mmm... from your description, it does seem more like a bug, possibly due to one or more memory leaks. ParaView is a bit known having those kinds of problems (edit: but they do gradually fix each problem with each new release). To top it off, this looks like a Heisenbug: http://en.wikipedia.org/wiki/Heisenbug
A couple of test files and two or three lists of steps on how to possibly trigger this issue would be helpful for placing a bug report at ParaView's bug tracker: http://paraview.org/Bug/
There is another hypothesis: the meshes+data being stored in the ".encas" format might be relying on ghost cells or some other feature that ParaView does not fully support. This would easily lead to there being unexpected memory leaks, causing this issue.
To solve this scenario, you would need to be able to assess what specific feature might be being used in the datasets. Using EnSight to load the files and checking the features being used, would help estimate which feature is making ParaView have problems.
|All times are GMT -4. The time now is 12:16.|