|
Notes |
|
|
(0022175)
|
|
thorenz
|
|
2010-09-10 02:40
|
|
|
The same is true for Paraview 3.8 |
|
|
|
(0022271)
|
|
thorenz
|
|
2010-09-20 03:48
|
|
|
The situation can be "cured" by applying the "Clean to Grid"-Filter on the dataset first. |
|
|
|
(0022348)
|
|
Takuya OSHIMA
|
|
2010-09-26 02:19
|
|
|
Can you share a dataset that causes the problem and give the exact procedure to replicate? |
|
|
|
(0022358)
|
|
thorenz
|
|
2010-09-27 03:31
|
|
Hello Takuya,
I uploaded a testcase to our ftp:
ftp://ftp.baw.de/incoming/test.zip [^]
Sorry, it is 800MB. Currently, I don't have a smaller one that shows the
problem.
The procedure is the following:
- load "result.foam"
- select "Decomposed case"
- Apply
- filter "Contour" with alpha1=0.5
I hope you can reproduce it :)
Carsten
P.S: Many thanks for vtkPOpenFOAMReader. It helps a lot :) I'm using it on our cluster and it gave me ~10x speed improve because of parallel data reading. |
|
|
|
(0022359)
|
|
Takuya OSHIMA
|
|
2010-09-27 06:09
|
|
A 96 processor case. Cool :)
Yes it did reproduce, however only when I selected cell-alpha1 (alpha1 with a cube on its left) from the Contour By combo box. There should be another alpha1 (point-alpha1, alpha1 with a dot on its left), and when I selected it the contour filter ran fine (I attached arraySelectionScreenshot.png to show which array to choose).
If my understanding is right the contour filter only works with the point-arrays, so the cell-arrays should not be in the selection list. I'm not sure which (the reader or the contour filter) is causing the problem but anyhow, please try the point-alpha1.
Takuya |
|
|
|
(0022360)
|
|
thorenz
|
|
2010-09-27 08:49
|
|
Hi Takuya,
the "point-alpha1" is not in the data set, it is generated by the OpenFOAM reader. Alpha1 is a cell centered quantity in OpenFOAM. You are right, using it without interpolating to the nodes causes the problem.
So, is this a bug in the reader or in the filter? I don't know, but I got a workaround now: Use the point data :) |
|
|
|
(0022362)
|
|
thorenz
|
|
2010-09-27 09:08
|
|
|
Update: I just tried to read another unstructured dataset written from another code in Ensight format. It shows the same behaviour: The regarded quantity is cell centered, "Contour" filter gives garbage. Applying "Cell to point" first and "Contour" on the point data afterwards gives correct result. So, it seems to be a problem in the Contour filter. |
|
|
|
(0022531)
|
|
Takuya OSHIMA
|
|
2010-10-19 05:15
|
|
I can confirm in the git master that the cell-arrays are no longer listed in the array selection of the contour panel, probably thanks to the following commit. Could someone please mark this bug as resolved?
commit a844b9eb4ca130b344da40435ec50764897d4b57
Merge: e98c0a7 2036cc1
Author: Robert Maynard <robert.maynard@kitware.com>
Date: Mon Oct 18 13:22:58 2010 -0400
Merge topic 'AutomaticPropertyConversion'
2036cc1 BUG: Corrected an issue with the contour filter supporting cell prop |
|
|
|
(0023727)
|
|
thorenz
|
|
2010-12-06 04:31
|
|
Checked out Paraview-3.9 on 2010-12-06
Now it works o.k.
|
|
|
|
(0023732)
|
|
Robert Maynard
|
|
2010-12-06 09:26
|
|
|
Corrected an issue with the contour filter supporting cell properties when it should only support point properties by default. |
|
|
|
(0023780)
|
|
Alan Scott
|
|
2010-12-07 17:29
|
|
|
As per reporter, and tested local server, windows client, trunk. |
|
pics.zip (88,714) 2010-09-07 04:23
arraySelectionScreenshot.png (23,153) 2010-09-27 06:08