Initialization failure due to non-matching surfaces

Official adapters and tutorials
1

Hello， preCICE official team,
I have been trying to write my own FLUENT adapter in order to achieve the coupling of three FLUENT instances. However, I have encountered some issues during the process. For simple cases with well-matched coupling interfaces, I am able to successfully invoke the preCICE initialization API and achieve initialization. However, for more complex cases where the coupling interfaces seem to differ significantly, I am unable to initialize due to mapping issues. Therefore, I would like to inquire if you could provide some guidance or suggestions for resolving this problem. Your assistance would be greatly appreciated. Thank you so much.
Here is the configuration file I am using for the coupling。
precice-config (2).xml (3.5 KB)
This is the console output information from Coupling Participant 1.

IMG_9916
IMG_99161920×534 206 KB

This is the console output information from Coupling Participant 2.

IMG_9917
IMG_99171920×466 168 KB

This is the console output information from Coupling Participant 3.

IMG_9918
IMG_99181920×696 307 KB

2

Hi,
This is a very common symptom of stale connection files.
Try deleting all precice-run folders in your project and run again.

3

Hi, I have a question. If preCICE filters out vertices that have no impact on the mapping, is there an API to determine which vertices are filtered and which vertices are retained?

4

Please open a new topic for a new question.

5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.