|
[Sponsors] |
July 17, 2012, 07:25 |
Visualization problem on ParaFoam
|
#1 |
Member
Join Date: Apr 2012
Location: France
Posts: 72
Rep Power: 14 |
Hi FOAMers,
I have different problems with the use of paraFoam. At the beginning I thought that the problem was in my snappyHexMeshDict file, but some people told me that the problem was a bug of paraFoam. I try to solve this problem with the polyHedral option, but paraFoam crash when the number of cells is too important. The picture 1 is without polyHedral option and the picture 2 is with this option.. Currently, I try to use the foamToVTK converter. I use this command ligne : "foamToVTK -latestTime" and I have the picture 3. I research the results of the picture 4 (without parts of cut cells), can you explain me how to obtain it ? Thanks for your help, Rider. |
|
July 17, 2012, 17:00 |
|
#2 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Greetings Rider,
Have you tried the option "-poly" with foamToVTK? Additionally, for inspecting a section cut of a mesh, use the "Extract Cells" feature instead, which will not trim your cells... although it's a bit buggy with polyhedral meshes. Furthermore, try this instead as well: Code:
paraFoam -builtin At the bottom of the "Object Inspector", you'll find the option for the polyhedral mesh as well. Best regards, Bruno
__________________
|
|
July 18, 2012, 04:37 |
|
#3 |
Member
Join Date: Apr 2012
Location: France
Posts: 72
Rep Power: 14 |
Greetings Bruno,
Thank you for your answer. I tried your propositions but it don't works (or it's me ...) If I upload my files, can you try ? Best regards, Rider |
|
July 18, 2012, 17:08 |
|
#4 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Hi Rider,
I suppose I can try figuring out what the problem is if you upload the case, as well as indicating where I should look at . If the data of the case is sensitive, send me the link via private message. By the way, was does checkMesh tell you about the mesh? Very skew faces is a good reason for even ParaView to have problems representing the mesh! Best regards, Bruno
__________________
|
|
July 19, 2012, 06:51 |
|
#5 |
Member
Join Date: Apr 2012
Location: France
Posts: 72
Rep Power: 14 |
Greetings Bruno,
I sent you a private message. If we can find a solution I'll post it here for everybody. Best regards, Rider |
|
July 20, 2012, 11:02 |
|
#6 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Hi Rider,
Yep, using polyhedral mesh with section cut crashes ParaView with this error message: Code:
Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted By the way, I also tested using the internal reader by running: Code:
paraFoam -builtin Best regards, Bruno
__________________
|
|
July 23, 2012, 03:53 |
|
#7 |
Member
Join Date: Apr 2012
Location: France
Posts: 72
Rep Power: 14 |
Thank you very much Bruno!
This is the result that I was looking for Best regards, Rider. |
|
January 8, 2013, 16:00 |
|
#8 |
Member
Suranga Dharmarathne
Join Date: Jan 2011
Location: TX, USA
Posts: 39
Rep Power: 15 |
Hi Bruno and Foamers,
I have a problem in visualization my mesh in paraview with openFoam. I have attached two snap shots of the same case with different cell numbers. When I use 3.1 millon cell case paraview fails to show me the geometry (openFoam1.jpg). The other one shows with around 400000 cell case which doesn't have any probelm. I ran two cases with the same conditions. But couldn't see results for the 3.1 million case. Please help me if you have encountered a similar type of thing. Best, Suranga. |
|
January 8, 2013, 16:23 |
|
#9 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Greetings Suranga,
Looks can be deceiving Even if it looks like it didn't load, there was no error message! What happened is that ParaView will display by default a heavier mesh in "Outline" mode, to avoid locking the user out. If your mesh had 1000 million surface cells - and assuming you had enough RAM - it could take a few good 5-10 minutes just to load the surface mesh. If you compare the two snapshots, you'll see that in one it says "Surface" and in the other "Outline". Don't see where it is yet? OK, see the Help menu? Then on the second line of tool-bar buttons below it, a bit to the right! There, one says "Surface" and in the other "Outline". My apologies if this description seems a bit patronizing, but when I saw the two snapshots you attached, in a simple comparison with back-and-forth the solution can be seen! Best regards, Bruno
__________________
|
|
January 8, 2013, 16:53 |
|
#10 |
Member
Suranga Dharmarathne
Join Date: Jan 2011
Location: TX, USA
Posts: 39
Rep Power: 15 |
Thank you very much for the prompt reply. I need to pay more attention in the future.
BR, Suranga. |
|
June 27, 2016, 11:19 |
|
#11 | |
New Member
Marco
Join Date: May 2016
Posts: 6
Rep Power: 10 |
Quote:
what is the difference or the advantage of opening paraFoam with the internal reader with the -builtin command? Thank you Marco |
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[OpenFOAM] problem with parafoam: "Read float past end of buffer" | Osman | ParaView | 2 | March 1, 2019 08:16 |
[OpenFOAM.org] OpenFOAM v5 on ubuntu 14.04 - Problem with ParaFoam | giorgos | OpenFOAM Installation | 2 | October 31, 2017 08:55 |
problem with visualization of iso-surface | blek | STAR-CCM+ | 9 | October 9, 2013 08:23 |
paraFoam touch problem | DiegoNaval | OpenFOAM | 0 | August 4, 2011 06:05 |
[OpenFOAM] Weird Problem with ParaFoam via SSH | cwang5 | ParaView | 2 | July 19, 2010 10:00 |