|
[Sponsors] |
[snappyHexMesh] Problems after snappyHexMesh with paraview |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
February 2, 2015, 14:19 |
Problems after snappyHexMesh with paraview
|
#1 |
New Member
Andreas V.
Join Date: Jul 2014
Posts: 15
Rep Power: 12 |
Hi
I have a problem with my simulation case and I am still unexperienced enough to solve the problem. Hope you can help... In my case I have a geometry which exist of different 5 stl files. I have tested all my setting with a very coarse background mesh and only one single stl file (out of these 5). Everything went (from my point of view) ok and the geometry looks quite ok after using snappyHexMesh. Now I have excess to a supercomputer facility and prepared the case with a much finer mesh and all geometries. For the simulations I've used 80 processors for a parallel application (depomposePar). After the snappyHexMesh step I've looked into the log file of the meshing process the meshing report says that the mesh is ok. And here is my problem. If I try to open the meshed geometry in paraview (by using paraFoam in the case directory), paraview shows only the block mesh with the different patch names. I also tried to reconstruct the case (with reconstructParMesh), but with the same result. What is wrong here. Any help is very much appreciated! Thanks in advance Andreas |
|
February 2, 2015, 16:47 |
|
#2 |
Senior Member
Matthew Denno
Join Date: Feb 2010
Posts: 138
Rep Power: 16 |
Just one quick thought, did you chose the option (dropdown) to view the decomposed case in paraview?
|
|
February 2, 2015, 17:11 |
|
#3 |
New Member
Andreas V.
Join Date: Jul 2014
Posts: 15
Rep Power: 12 |
That was one of the problems. There was no option bottom (decompose/reconstruct).
|
|
February 2, 2015, 17:14 |
|
#4 |
Senior Member
Matthew Denno
Join Date: Feb 2010
Posts: 138
Rep Power: 16 |
I am not at my computer but you might need to launch paraFoam -builtin to get that option.
|
|
February 3, 2015, 04:13 |
|
#5 |
New Member
Andreas V.
Join Date: Jul 2014
Posts: 15
Rep Power: 12 |
Hi Matthew
thank you for the hint, but I have still the same problem. I have attached the log file of this job (I needed to shrink it a bit...). It looks to me that everything is ok and I would expect that I am able to see the meshed parts in paraview. But I don't. I am a bit helpless. Does that mean that the meshing process failed or that there is only a visualisation problem? File/case information: In the log file there are all information from the blockMesh, decomposePar and snappyHexMesh step. I deletetd most of the snappy-output because of the file size limitation here. But there were not error/warnings or something. After this process it worked not on paraview. Then I tried to run: reconstructParMesh, but with the same problem. Thanks. Andreas |
|
February 3, 2015, 04:23 |
|
#6 |
Senior Member
|
Hi,
Take a look at your log: Code:
... 6 5084040 Writing mesh to time 3 Wrote mesh in = 1288.72 s. ... |
|
February 5, 2015, 03:30 |
|
#7 |
New Member
Andreas V.
Join Date: Jul 2014
Posts: 15
Rep Power: 12 |
Thanks.
This was really helpful. I understood what happened but still. The meshed stl file is not visible. What I did now: 1. blockMesh 2. decomposed with "hierarchical" 3. snappyHexMesh -overwrite 4. reconstructParMesh If I look into the logfile I cannot see any error warnings, problems, etc. I am now completely hopeless. |
|
February 5, 2015, 03:39 |
|
#8 |
Senior Member
|
If the sequence of commands you've posted is exact, then
1. You create mesh with blockMesh (let's call it (1)) 2. Decompose mesh (1) 3. Run 'snappyHexMesh -overwrite', so it runs in serial regime and creates mesh in constant folder (let's call it (2)). 4. Run reconstructParMesh, so the mesh (1) is reconstructed over newly created (2). Or step 3 was definitely run in parallel regime? |
|
February 5, 2015, 11:35 |
|
#9 |
New Member
Andreas V.
Join Date: Jul 2014
Posts: 15
Rep Power: 12 |
Yes this is correct.
Is it a problem that I use first blockMesh and then decomposePar and the rest? Or is it important to decompose first and then doing blockMesh, snappyHexMesh? And yes I am sure that I have run this case in parallel! |
|
February 5, 2015, 11:47 |
|
#10 |
Senior Member
|
Everything became rather complicated
1. You say that you run commands exactly as it was written 'snappyHexMesh -overwrite'. This command runs snappyHexMesh in serial mode, to run it in parallel you should do 'snappyHexMesh -overwrite -parallel' 2. You're definitely sure about running the case in parallel. In the log you have attached to the previous message it was clear that snappyHexMesh was run in parallel regime. But I don't see the log this time, it's difficult to say what has been happened. |
|
February 23, 2015, 12:00 |
Problem solved
|
#11 |
New Member
Andreas V.
Join Date: Jul 2014
Posts: 15
Rep Power: 12 |
Hi alexeym
thank you again for kicking my a.. I finally solved the problem with you help. I used either -overwrite or -parallel but not -overwrite -parallel. I used the following commands: blockMesh > log.block surfaceFeatureExtract topoSet decomposePar -force mpiexec_mpt snappyHexMesh -overwrite -parallel Thanks again. Andreas |
|
Tags |
openfoam 2.3.1, parafoam, snappyhexmesh 3d |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] Problems with scaling meshes when meshing with SnappyHexmesh | Bnitter | OpenFOAM Meshing & Mesh Conversion | 1 | November 15, 2018 09:26 |
[snappyHexMesh] Problems meshing an impeller with snappyHexMesh | kandelabr | OpenFOAM Meshing & Mesh Conversion | 13 | June 9, 2017 07:18 |
[OpenFOAM.org] Problems to install openfoam-2.4.0 on Ubuntu 16.04.01LTS | matheusmonjon | OpenFOAM Installation | 3 | February 25, 2017 15:46 |
[snappyHexMesh] Problems with snappyHexMesh | Sbaleman | OpenFOAM Meshing & Mesh Conversion | 3 | January 9, 2017 17:15 |
[OpenFOAM.org] Problems with Paraview (OpenFOAM 2.4.0 from source code in Ubuntu 14.04) | Gerrit | OpenFOAM Installation | 4 | August 15, 2015 12:05 |