paraFoam problem
1 Attachment(s)
Has anybody else met the following problem of paraFoam. Here is a picture to show the problem.
http://www.cfd-online.com/Forums/att...1&d=1253861482 Data can't be showed correctly. Is there any method to fix this? Thanks. |
Hi Xinyuan,
I got the same problem with you. I am using OpenFOAM-1.6.x with ParaView 3.6.1. There are some unwanted spots when viewing results with paraFoam, just as you list above. Have you resolved it yet? Best Regards, Jitao |
Hallo,
I had also very small spots on the surface of the volume. Try this: on display --> style --> interpolation --> standard is Gouraud switch to flat I hope it help's Preibie |
2 Attachment(s)
Quote:
Thanks for your reply. The spots are still there by switching Gouraud to flat. The picture is ok when viewing in Z or -Z direction: Attachment 1209 Once the view is not along the axis direction, the spots will appear: Attachment 1210 Regards, Jitao |
Hallo,
do you check the numerical values of the cells? When there are OK it must be an interpolation mistake. Also it seems that your grid is very poor, isn't it? |
Hello, Preibie!
Thanks for your reply. I've checked that my numerical values have no problems. When I changing interpolation mode from Gouraud to flat, there is no change in picture of paraFoam. But when I using foamToVTK and paraview to see the results, there is no problems. Awacs, try foamToVTK paraview Then open the corresponding .vtk files to see if the spots are still there. |
Since I use paraview I have problems with the foamReader to open foam files directly. I changed my QT version (from 4.4 --> 4.3.5) all was fine. After the installation of the new version 1.6 I don't want to change Qt again (it was very complicated). Now I take the same way like you transform all in vtk!
I find some more problems with paraview and qt. On Windows you can't use the glyph filter! The error message said qt is wrong!! |
Possible solution
2 Attachment(s)
Hi,
Have you got the same geometry displayed twice in the 'pipeline browser', cause that seems to cause spots, because paraview is trying to show coinciding geometries and the spots are probably the surface of the other geometry. So just make sure that only one instance of the geometry is being viewed at a time i.e. click the 'eye symbol' off beside one of the geometries in the pipeline browser in the top left of the GUI. I have attached pictures of one of my cases, with more than one display on (spots) and just one display on (no_spots). See the way two 'eye symbols' are on in 'spots' and only one is on in 'no_spots'. Hopefully this was the source of your problem, if not maybe at least it might help someone else. Philip EDIT: I just realised that I use foamToVTK and then paraview, so maybe my comment doesn't help paraFoam users... |
1 Attachment(s)
Quote:
Thanks for your reply. The result is ok now. Best wishes, Jitao |
Dear OF users,
I use OpenFOAM-1.6.x and paraview3.6.1. I have problems when using paraFoam or foamToVtk and then paraview. The 'Rescale to Data Range' button does not work ! Values remain fixed between 0 and 1, except for the velocity. To modify the scale I have to play with the 2 buttons : Edit Color Map and Rescale Range Has somebody experienced the same problem ? Regards, Stephane. |
Nobody has encountered this kind of problem ?
Stephane. |
Hi,
Sometimes if I find that paraview is showing the wrong values, it is because my values are wrong. Are the values you are interested in actually varying more than 0 - 1, ie if you check the values in the time directories with emacs(or any text editor). Philip |
Hi, Stephane
I met this preoblem when I use paraFoam, but not in foamToVTK and then paraview. Make sure that "Time" and "builtin" are chosen right, sometimes wrong operation causes these problems. Or as Philip said, check your data file with any editor. Fan |
Dear Philip,
dear Fan, Only the velocities fields (x, y and z) works fine. Other fields, like p, nut, k, epsilon and omega do not work. The scale range remain fixed between 0 and 1. I have to change it manually with the following 2 steps : Edit Color Map and rescale Range. But so I can not find min and max values ! I have also checked the results directories /1000 /2000 ... /5000. They are OK ! paraFoam or paraview with foamToVTK do not change anything ! I will try to run a tutorial with MRFSimpleFoam. Regards, Stephane |
I just computed the mixerVessel2D tutorial and I have the same problem.
Only the velocity field works well. All other fields are fixed between 0 and 1 Need advices, Stephane. |
Stephane,
hmmnn... maybe there is just something wrong with your paraview, you could try download paraview again and reinstall it, from http://www.paraview.org/paraview/res.../software.html. The binarys there seems to work fine for me (I use the linux, mac and windows versions). Then just use foamToVTK. Philip |
Hi,
my problem is still unsolved ! The autoscale works well only with the velocities values (X, Y and Z). For all other values (pressure, omega, k, ...) the scale remains blocked between 0 and 1. Any advices ? Stephane. |
Hello Stephane,
Wait, after almost a month, you haven't solved it yet? Have you tried using the Paraview binaries available online? Try using this plugin instead of the original version, in case you've already tried. Also, try checking the limits of the data, in the information tab in Paraview. Are you sure there aren't any infinite ou undefined values? Best regards, Bruno |
Hi,
I have discovered an interesting thing. My problem disappears only if I use paraview version 3.4 : autoscale works fine. When I use paraview version 3.6 the autoscale does not work proprely ! It remains blocked between 0 and 1. Has someone already experienced this ? I still want (and need) to solve this strange problem ! Regards, Stephane. |
Hi,
No, you aren't the only one... there is a similar report here. But it was with version 3.5.0, and there is no reference on that thread, to it being fixed. It seems to be a problem with Paraview itself, and not the plugins. And to top it off, it is hard to replicate the problem! This bug report to the Paraview mail list starts here. If you can post a small test case where you get the same problem, that would help a lot! edit: just saw that you've already mentioned that the mixerVessel2D tutorial shows up the same bug. Can you try building your Paraview version in another machine or virtual machine and another version of the OS you are using? There is also the slight possibility that the downloaded ThirdParty package was damaged! Best Regards, Bruno |
All times are GMT -4. The time now is 23:39. |