|
[Sponsors] |
[snappyHexMesh] Copying writeFlags after reconstructParMesh |
![]() |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
![]() |
![]() |
#1 |
Member
Join Date: Sep 2018
Location: France
Posts: 62
Rep Power: 7 ![]() |
Hello,
I am currently analysing how snappyHexMesh is working so I chose to start with the motorBike tutorials. When I am running the case in parallel by using decomposePar and mpirun, I set on the writeflags in the initial snappyHexMeshDict to see the different level of refinement in paraview. In parallel, in the folders processor.*, I have got the files in each time step "cellLevel" and "pointLevel" which allows me to see the volScalarfield in paraview. The problem is that when I do the command reconstructParMesh, it does not taking into account these two files in the reconstructed time step file (1/ and 2/) . Therefore I cannot use these fields in paraview. Do you know which option can take into account these two files after reconstruct the mesh ? Cheers |
|
![]() |
![]() |
![]() |
![]() |
#2 |
Member
Join Date: Sep 2018
Location: France
Posts: 62
Rep Power: 7 ![]() |
I just find how to read the writeflags in paraview without reconstruct the case.
You can either read without reconstructing the case by selecting case type "Decomposed Case" in paraview or do reconstructPar after reconstructParMesh. |
|
![]() |
![]() |
![]() |
![]() |
#3 |
Senior Member
anonymous
Join Date: Jan 2016
Posts: 416
Rep Power: 14 ![]() |
Hi!
Just if you need it in the future. reconstructParMesh reconstruct your MESH, and only the mesh. Then you can use reconstructPar, which will reconstruct your fields. |
|
![]() |
![]() |
![]() |
![]() |
#4 |
Senior Member
Giles Richardson
Join Date: Jun 2012
Location: Cambs UK
Posts: 102
Rep Power: 14 ![]() |
Thanks so much John for posting this solution - I was just really helpful to us!
|
|
![]() |
![]() |
![]() |
Tags |
parallel, snappyhexmeshdict, writeflags |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[ICEM] Problems after copying blocks | anand32 | ANSYS Meshing & Geometry | 1 | August 3, 2017 20:57 |
[Other] Using reconstructParMesh on a cluster, bottle neck and out of memory | KTG | OpenFOAM Meshing & Mesh Conversion | 2 | May 5, 2017 12:48 |
reconstructParMesh + GGI problem | jiejie | OpenFOAM Post-Processing | 0 | August 14, 2012 02:10 |
Copying tranfsinite volumes in gmsh | shangzung | Main CFD Forum | 0 | December 10, 2009 03:04 |
reconstructParMesh not working with an axisymetric case | francesco | OpenFOAM Bugs | 4 | May 8, 2009 05:49 |