[romant]

Hej,

I installed OpenFOAM 2.3 and paraview 4.10 that comes with the new openfoam. I then ran one of my cases which is a multiregion case in decomposed state with chtMultiRegionSimpleFoam. Then I start paraview through

paraFoam -region WATER

it starts all fine, however the option for decomposed case is missing. When I start

paraFoam -region WATER -builtin

it also starts, the option for decomposed case is present, however, then paraview does not look into the processor1/constant/WATER/polymesh but into processor1/constant/polymesh

The question is, does anybody know how to use multiregion with a decomposed case without having to recompose it? I also tried using the paraview 4.01 (which comes with ubuntu 13.10) in connection with just calling the foam file case{WATER}.foam , there the option for decomposed is also present, however, it also has the same error that it wants to look for the polymesh not in the region file, but in the folder one level up.

[wyldckat]

Hi Roman,

The built-in plugin does not rely in special names like the official plugin. As shown in the attached image, you have direct control access to the multiple regions, by simply using:

paraFoam -builtin

Best regards,
Bruno

[romant]

Originally Posted by wyldckat

Hi Roman,

The built-in plugin does not rely in special names like the official plugin. As shown in the attached image, you have direct control access to the multiple regions, by simply using:

paraFoam -builtin

Best regards,
Bruno

Hej Bruno,

I saw that as well, however, I always get an error message

 p, li { white-space: pre-wrap; }  /home/roman/Desktop/Gallego/SteadyState_RomanMod_kEpsilon_Ferlin/processor39/constant/polyMesh/faces.gz: Can't open. If you are trying to read a parallel decomposed case, set Case Type to Decomposed Case.
 

 

 ERROR: In /home/opencfd/OpenFOAM/ParaView-4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754
 vtkCompositeDataPipeline (0x6d348a0): Algorithm vtkOpenFOAMReader(0x2595ca80) returned failure for request: vtkInformation (0xfd77170)
   Debug: Off
   Modified Time: 455183
   Reference Count: 1
   Registered Events: (none)
   Request: REQUEST_DATA
   ALGORITHM_AFTER_FORWARD: 1
   FROM_OUTPUT_PORT: 0
   FORWARD_DIRECTION: 0

and it seems that paraview still does not look into the right folders in order to find the mesh. I tried using only internalMesh, only WATER/internalMesh, and also only the solid part as a mesh in the mesh region selection. The part that I highlighted does of course not exist. However, instead of constant/polymesh, I of course have the different mesh regions there like constant/WATER/polymesh.

Edit:

found the error. In the non-decomposed version, there was a polymesh and boundary data, which of course shouldn't be there. Because it was in the non-decomposed one, it was also looking for them in the decomposed version.

[wyldckat]

Hi Roman,

Originally Posted by romant

Edit:

found the error. In the non-decomposed version, there was a polymesh and boundary data, which of course shouldn't be there. Because it was in the non-decomposed one, it was also looking for them in the decomposed version.

Many thanks for sharing this information!

Best regards,
Bruno