|
[Sponsors] |
![]() |
![]() |
#1 |
Senior Member
Alan w
Join Date: Feb 2021
Posts: 278
Rep Power: 6 ![]() |
Having shifted my efforts to validate the Meredith effect from chtMultiRegion to buoyantSimpleFoam, I am encountering behavior of topoSet that I don't understand.
Starting with a mesh from an outside meshing tool, initially I used topoSet to find the mesh cells corresponding to my heat exchanger, and then assign them to a porous zone. In the process of doing this, the output says, "Create mesh for time = 0.25". Apparently, this time comes from the controlDict deltaT of 0.25. Why does topoSet need to create a mesh at a following time? It could just create a new polyMesh, with no associated time. Anyway, a folder is created, named '0.25'. Then, if I clean the case, deleting the 0.25 folder and re-run it, it fails, saying "Cannot find patchField entry" for one of the boundary conditions. So now, I am compelled to keep the 0.25 folder forever, for the case not to fail. This doesn't seem right. What am I missing here? |
|
![]() |
![]() |
![]() |
![]() |
#2 |
Senior Member
|
Hi,
This is what happens if you do not use the -overwrite option when running topoSet. It will create a new polyMesh folder inside a time step folder (in your case 0.25). You can just move this polyMesh folder into constant overwriting the mesh there and then remove the 0.25 folder. Of course if you prefer to keep the original mesh you can rename constant/polyMesh to constant/polyMesh.org before moving the 0.25/polyMesh folder into constant. Regards, Tom |
|
![]() |
![]() |
![]() |
![]() |
#3 |
Senior Member
Alan w
Join Date: Feb 2021
Posts: 278
Rep Power: 6 ![]() |
your reply makes perfect sense. While I feel a bit stupid, you've helped me to never make that mistake again.
Alan |
|
![]() |
![]() |
![]() |
|
|