-n specifies the number of nodes.
-np specifies the number of processes.

I cannot comment on your inquiry but I guess it should not matter which one (-n or -np) you use as long as you specify the same number of processes/nodes.

reconstructParMesh returns "no mesh" message.
 

Hi all,

I've been using blockMeshDict and thereafter snappyHexMeshDict for a given case to run in parallel.

In the blockMeshDict, when my base hex resolution is (40 40 40), mesh decomposition works fine. However, when I increase this base resolution to (128 128 128), and run the case, blockMesh and snappyHexMesh create the mesh, decomposePar runs without returning any error messages, and the simulation starts. But when I run "reconstructParMesh", it gives me a "no mesh" error at EACH timestep.

Has anyone encountered this odd error and if so, how is it to be navigated?

Hi Praktiki,

there are many possible error sources in such a long process chain. ;) Is there a specific reason why you are using reconstructParMesh? I've stopped using it because I also encountered problems with it. Also also remember that it is still some beta version?!

For post processing in Paraview as far as I know you dont need it.

Marco