snappyHexMesh - parallel processing problems
 

When I run snappy regularly everything is fine. As soon as I use decomposePar, the resulting mesh is the same as that of blockMesh. Is this a simple fix?

You first need to copy the mesh in the last time directory created by snappy to the constant/polyMesh folder. Or alternatively run snappy with the '-overwrite' option.

Cheers,

L

after running reconstructPar -latestTime, no new folders are being made? All I have is 8 processor folders and the 0, constant, and systems folder. I feel like a new time folder should be created correct?

Dear B,
if you use -overwrite, no new folders (1,2,3) are created. Instead 0 is overwritten.

Best regards
Julian

when I run snappy with -overwrite I cannot get recontructPar to work?

blockMesh
decontructPar -force
foamJob -parallel -screen snappyHexMesh -overwrite
reconstructPar -zeroTime ---> gives error: Size of maps does not correspont to size of mesh for processor 0
reconstructPar -latestTime ---> gives error: No times selected

when I run without overwrite, two new times folders are created within each processor (one for mesh, one for snap), but reconstructPar does not create new times folders in the directory.

when I run with overwrite, no new times folders are created within each processor, and I cannot use reconstructPar.

again, if I just use snappyHexMesh, everything works out perfectly. Could this have to do with the way decomposePar is splitting up the mesh? the piece I am adding is not evenly distributed.

Try

This works for me with snappy in parallel.

Best regards
Julian

RULI you're the best! Worked like a charm.