[pici]

Hi to everybody.
I did a long session, that should have terminated with grouping together all patches like "pareti.*" and rename the resulting single patch simply "pareti"
(in Italian, pareti means walls).
Anything goes well, but patches are not grouped and not renamed.
There is an utility able to do this job AFTER meshing process?
I ask this because the whole meshing process take more then a couple of hours . . .
Thank you in advance

Piero

[pici]

Originally Posted by pici

Hi to everybody.
I did a long session, that should have terminated with grouping together all patches like "pareti.*" and rename the resulting single patch simply "pareti"
(in Italian, pareti means walls).
Anything goes well, but patches are not grouped and not renamed.
There is an utility able to do this job AFTER meshing process?
I ask this because the whole meshing process take more then a couple of hours . . .
Thank you in advance

Piero

Just now I noted that, in meshDict, there was an extra "}" just before the renameBoundary sub-dictionary. Obviously, this should be the error reason. But my question could be still valid, because it is easy to make this kind of typing mistake.
Many thanks

Piero

[franjo_j]

Hi,

I hope that your problems are resolved by removing an extra }.
Currently, it is not possible to rename boundary patches because it is not implemented as a separate utility. It is not difficult to do, all you need is to create a new utility and copy the code for renaming boundaries from cartesianMeshGenerator.C.
How many cells are there in the case lasting a couple of hours and how many cores were available for the meshing job?

Ciao,

Franjo

[pici]

Originally Posted by franjo_j

Hi,

I hope that your problems are resolved by removing an extra }.

Yes, at all.

Currently, it is not possible to rename boundary patches because it is not implemented as a separate utility. It is not difficult to do, all you need is to create a new utility and copy the code for renaming boundaries from cartesianMeshGenerator.C.
How many cells are there in the case lasting a couple of hours and how many cores were available for the meshing job?

Ciao,

Franjo

About the possibility to do the utility by myself, I don't like to do this kind of job, because I'm not a good programmer.
About the size of the problem, the final mesh has about 7.5 Million Cells; the hardware is a little obsolete: 2xAMD Opteron 2222 (totale 4 cores), 16 GB memory, but only DDR2 at 666 MHz.

Actually I see a decisive increment in performances: only 12 minutes to calculate about 10 Million Cells. Perhaps I'm now more experienced (the hw is still the same) . . . .
Ciao e grazie

Piero