Lagrangian particle tracking cannot be run in parallel for the cases with AMI patches
 

Hi everybody,

I'm going to run a lagrangian particle tracking for a case with cyclicAMI patches with OpenFOAM-dev. In OpenFOAM there is currently a limitation, that the particle tracking cannot be run in parallel for the cases with AMI patches and if you try it, you will get the following error:


[3] --> FOAM FATAL ERROR:
[3] Particle tracking across AMI patches is only currently supported for cases where the AMI patches reside on a single processor
[3]
[3] From function void Foam::Cloud<ParticleType>::checkPatches() const [with ParticleType = Foam::CollidingParcel<Foam::KinematicParcel<Foam:: particle> >]
[3] in file /home/armin/OpenFOAM/OpenFOAM-dev/src/lagrangian/basic/lnInclude/Cloud.C at line 59.
[3]
FOAM parallel run aborting


As you can see, it says, that the AMI patches must reside on a single processor in order to run the case in parallel. For this purpose I used then the "singleProcessorFaceSets" setting in decomposeParDict and the AMI patches reside now only on one processor, but the problem is, that it leads again to the same error:


[6] --> FOAM FATAL ERROR:
[6] Particle tracking across AMI patches is only currently supported for cases where the AMI patches reside on a single processor
[6]
[6] From function void Foam::Cloud<ParticleType>::checkPatches() const [with ParticleType = Foam::CollidingParcel<Foam::KinematicParcel<Foam:: particle> >]
[6] in file /home/armin/OpenFOAM/OpenFOAM-dev/src/lagrangian/basic/lnInclude/Cloud.C at line 59.
[6]
FOAM parallel run aborting


I'd like to know if somebody knows, how to overcome this issue.

Thanks in advance!
Armin

Dear Foamers,

I found the solution.

Regards,
Armin

How did you solve it?

I would like to know the solution too please!

I encountered the same error in a case ... without Lagrangian. Turns out I had a function object for extracting variables along a line intersecting an AMI patch. This was causing the bug.

To get the case working, I had to comment out the function object. And I had to extract two lines: one on each side of the AMI.

Hi Bruno,

That is exactly the same error that I am getting except even when my start and end points don't touch the boundaries I am getting the same issue. How did you ensure there were no intersections?

Thanks

Sorry for the late reply. It's been a while since I logged in.

I am not sure how you can ensure that there is no intersection using some OpenFOAM function. I just know where the AMI surface is located in my geometry and take care not to cross it with a line extract function object.

Incidentally, line extraction seems to work when using postProcess -func "function" instead.

Could you please share your solution? I am meeting the same problem recently.

Thanks and Regards