Reply To: Non conformal interface with unwanted Matching

[Lucjan Nastalek]

 

 

Right on! 

I’m not sure if this is a bug, but it sure looks like a bug. 

In version 2023 R2, there are two ways for switching the one-to-one-pairing off:

 

 

1. by typing in /define/mesh-interfaces/one-to-one-pairing? no
2. by switching on the turbo model. This seems to automatically switch off the pairing, also.

 

 

Initially, I:

 1. loaded the model,

 2. switched on the Turbo models,

 3. created the Turbo interfaces (which switched off the one-to-one)

 4. proceeded to set up all other, Mapped, interfaces. This enforced Matching option to every other interface that I’d made, even though I hadn’t selected the option (I wanted Mapped+Coupled, but ended up with Mapped+Coupled+Matching instead).

Just 10 minutes ago I finished setting up the interfaces in a reversed order:

 1. I have first switched off the pairing,

 2. then created the general interfaces (Mapped+Coupled) – which now recorded the correct options w/o the enforced “Matching” option,

 3. after which I switched on the Turbo models

 4. and created the Turbo interfaces last.

This time, the other interfaces retained their options ( Matched+Coupled, no Matching “nonesense” added). 

 

Perhaps this behavior is intended. Perhaps even it is very well documented, and I simply glossed over it somehow. But it feels very counter-intuitive to me.

By the way, in the first option, I tried to edit the Matching interfaces to switch off the option, but it would do nothing at all: the Matching option remained switched on.

Of course, there’s no guarantee that this will have improved my case’s convergence, but at least I’ve learned something about setting up interfaces in Fluent 2023 R2. I am therefore putting it out there for anyone else interested. 

 

Any further comments and/or clarifications and/or corrections are welcome!

 

Thanks,

LN