View Issue Details

IDProjectCategoryView StatusLast Update
0003817OpenFOAMBugpublic2022-05-19 08:57
Reportermichael.mueller-wrdAssigned Towill 
PrioritynormalSeverityminorReproducibilityrandom
Status resolvedResolutionfixed 
PlatformGNU/LinuxOScentOSOS Version(please specify)
Product Version9 
Fixed in Versiondev 
Summary0003817: 3D parallel simulation using cyclicAMI, decomposed using scotch; randomly runs or gives fatal error
DescriptionWhen using cyclicAMI patches in a rotational symmetric 3D case, it may happen that
(a) the case runs fine in parallel (e.g. np=128, np=256), and
(b) the case fails to run with "FOAM FATAL ERROR: Unable to set sources and target faces" (e.g. np=32, np=192)
depending on the number of processors.
Serial simulation always runs fine, thus, there is not an error related to the cyclicAMI specification in polyMesh/boundary.

For decomposition, scotch method was used and no constraints are defined in order to avoid imbalanced mesh distribution over processors.
Case geometry is rather complex with sth. like 10-100M cells and a high number of cells connected to cyclicAMI patches. (The case should run on some 100s of processors.)

I don't know if that is an actual bug or if there is a workaround to avoid the random behaviour.
Anyway, the random behaviour in terms of at which no. of processors it still works and at which it throws an fatal error appears to be quite strange.
TagsNo tags attached.

Activities

will

2022-05-19 08:57

manager   ~0012596

This issue should be resolved by the new Non-Conformal Coupled (NCC) development. The advancing front algorithm for generating the coupled geometry has been completely rewritten and bears no relation to the one used by AMI. So, I would assume that the failure mode that you have experienced is not present with NCC.

https://github.com/OpenFOAM/OpenFOAM-dev/commit/569fa31d09f98e29d1aaf84d40bb16043f104ec6

I do not have access to the case, however (I assume it is large and problematic to share), so I cannot verify that it now runs with NCC. I am sure though that any issues with NCC will be sufficiently different from the issues with AMI that this bug report will not be of relevance. So, I'm considering it resolved.

If you encounter any problems running this case with NCC, please contact us, or file a new bug report, as appropriate.

Issue History

Date Modified Username Field Change
2022-03-15 14:50 michael.mueller-wrd New Issue
2022-05-19 08:57 will Assigned To => will
2022-05-19 08:57 will Status new => resolved
2022-05-19 08:57 will Resolution open => fixed
2022-05-19 08:57 will Fixed in Version => dev
2022-05-19 08:57 will Note Added: 0012596