foam-extend: different empty (2-D) directions

Michael@UW · August 28, 2019, 12:44

Does anybody have any idea how to deal with the following error?

I encounter the error when running foam-extend 4.1 in parallel "Some processors detect different empty (2-D) directions. Probably using empty patches on a bad parallel decomposition".

My empty direction is along x-axis. I tried different decomposing methods in decomposeParDict file and the domain is successfully decomposed as expected. , but it keeps giving the same error. The error pops up at the first time step most of the time, sometime after some iterations. By the way, I am using sixDoFRigidBodyDisplacement boundary condition (0/pointDisplacement) and the solver is interDyMFoam.

The case runs well in serial mode.

decomposeParDict:

numberOfSubdomains 2;
method simple;
//method scotch; //same error
//method metis; //same error
simpleCoeffs
{
n ( 1 2 1 );
delta 0.001;
}

Hgholami · November 4, 2019, 06:21

Dear Michael@UW
I have the same problem with cyclic boundary condition and dynamic mesh (fsiFoam). Do you resolve it?

Michael@UW · November 4, 2019, 12:25

No. I have not solved this issue. But I found the inconsistent empty direction is caused by the dynamic mesh motion; there is an unexpected rotation to make the mesh of the empty patch not on the same plane. I constrain the object but it still produces some motion along the direction which is not supposed to have.

Hgholami · November 8, 2019, 02:22

As your tip, I separate cyclic boundary condition to multi part and use "preservePatch" in decomposeDict to add each part to a processor. I think it works.

Michael@UW · November 24, 2019, 21:13

Quote:

Originally Posted by Hgholami

As your tip, I separate cyclic boundary condition to multi part and use "preservePatch" in decomposeDict to add each part to a processor. I think it works.

That's a good way! I may try that later. Recently I learned there is a tool name flattenMesh which can make the patch flat, but I haven’t tried it.

Hojjat · May 11, 2023, 01:52

I also get the same error in FE4.1. In the error description there is a mention of increasing 'emptyDirectionTolerance' in controlDict, which I couldn't make it work.
What I did to solve the issue was to reduce my number of processors in decomposeParDict by one. For example changing 6 to 5. I think dividing a number to 5 produces a rounder number so round-off error is increased and more manageable.

August 28, 2019, 12:44	foam-extend: different empty (2-D) directions	#1
Michael@UW Senior Member Join Date: Jan 2019 Posts: 125 Blog Entries: 1 Rep Power: 0	Does anybody have any idea how to deal with the following error? I encounter the error when running foam-extend 4.1 in parallel "Some processors detect different empty (2-D) directions. Probably using empty patches on a bad parallel decomposition". My empty direction is along x-axis. I tried different decomposing methods in decomposeParDict file and the domain is successfully decomposed as expected. , but it keeps giving the same error. The error pops up at the first time step most of the time, sometime after some iterations. By the way, I am using sixDoFRigidBodyDisplacement boundary condition (0/pointDisplacement) and the solver is interDyMFoam. The case runs well in serial mode. decomposeParDict: numberOfSubdomains 2; method simple; //method scotch; //same error //method metis; //same error simpleCoeffs { n ( 1 2 1 ); delta 0.001; }

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Other] mesh airfoil NACA0012	anand_30	OpenFOAM Meshing & Mesh Conversion	13	March 7, 2022 17:22
problem during mpi in server: expected Scalar, found on line 0 the word 'nan'	muth	OpenFOAM Running, Solving & CFD	3	August 27, 2018 04:18
error with reactingFoam	BakedAlmonds	OpenFOAM Running, Solving & CFD	4	June 22, 2016 02:21
decomposePar is missing a library	whk1992	OpenFOAM Pre-Processing	8	March 7, 2015 07:53
channelFoam for a 3D pipe	AlmostSurelyRob	OpenFOAM	3	June 24, 2011 13:06

November 4, 2019, 06:21		#2
Hgholami Senior Member Hojatollah Gholami Join Date: Jan 2019 Posts: 171 Rep Power: 7	Dear Michael@UW I have the same problem with cyclic boundary condition and dynamic mesh (fsiFoam). Do you resolve it?

November 4, 2019, 12:25		#3
Michael@UW Senior Member Join Date: Jan 2019 Posts: 125 Blog Entries: 1 Rep Power: 0	No. I have not solved this issue. But I found the inconsistent empty direction is caused by the dynamic mesh motion; there is an unexpected rotation to make the mesh of the empty patch not on the same plane. I constrain the object but it still produces some motion along the direction which is not supposed to have.

November 8, 2019, 02:22		#4
Hgholami Senior Member Hojatollah Gholami Join Date: Jan 2019 Posts: 171 Rep Power: 7	As your tip, I separate cyclic boundary condition to multi part and use "preservePatch" in decomposeDict to add each part to a processor. I think it works.

May 11, 2023, 01:52		#6
Hojjat New Member Join Date: Dec 2022 Posts: 2 Rep Power: 0	I also get the same error in FE4.1. In the error description there is a mention of increasing 'emptyDirectionTolerance' in controlDict, which I couldn't make it work. What I did to solve the issue was to reduce my number of processors in decomposeParDict by one. For example changing 6 to 5. I think dividing a number to 5 produces a rounder number so round-off error is increased and more manageable.