Why do MRF or sliding-mesh rotor-stator interfaces give unstable or suspicious results?

Problem: the rotor-stator solution is unstable, discontinuous or physically wrong

Common symptoms include pressure or velocity discontinuities across the interface, torque that changes strongly with interface mesh, mass imbalance between rotating and stationary regions, unexpected swirl direction, periodic oscillations in a supposedly steady MRF case, or transient blade loads that change when timestep is reduced.

Because rotating simulations combine reference-frame physics, interpolation and often periodicity, diagnostics must separate these mechanisms.

First decide whether MRF or sliding mesh matches the engineering question

A steady method can be an efficient initialization or design-screening tool, but its limitation should be treated as model-form uncertainty rather than a convergence problem.

Likely cause groups

• Wrong rotation axis, origin, sign convention or angular speed.
• Boundary conditions specified in the wrong absolute/relative frame.
• Interface surfaces that do not geometrically overlap as intended.
• Large cell-size mismatch across the interpolation interface.
• Insufficient circumferential resolution of wakes or blade-passing structures.
• Timestep too large for angular displacement or convective transport through the interface.
• Incorrect periodic-sector pitch, blade-count ratio or phase relationship.
• Domain interfaces placed too close to blades where gradients are extreme.

How to diagnose rotating-interface problems

1. Verify axis, origin, speed and rotation direction visually.

   Use velocity vectors or a simple point-motion check. A sign error can create plausible-looking but reversed swirl.

2. Confirm absolute and relative velocity interpretation.

   Compare quantities in the correct frame when crossing rotating/stationary regions.

3. Check mass and momentum continuity across the interface.

   Integral fluxes should be consistent even though local interpolation creates different cell-to-cell patterns.

4. Inspect cell size and face density on both sides.

   Extreme mismatch can diffuse wakes or produce interpolation noise.

5. Move the interface away from the strongest blade gradients if possible.

   Interpolation is generally more robust where the flow has had some distance to develop.

6. For sliding mesh, reduce timestep and compare torque/pressure phase.

   Angular movement per step must resolve the transient interaction you are trying to measure.

7. Check periodicity independently.

   A sector model is valid only when the geometry and operating condition truly satisfy the assumed repetition.

Fix order

1. Correct rotation/frame definitions.

   Do this before any mesh or solver tuning.

2. Validate interface geometry and region connectivity.

   Ensure the intended surfaces pair correctly and no unintended leakage paths exist.

3. Improve mesh compatibility near the interface.

   Resolve wakes and avoid unnecessarily abrupt cell-size jumps.

4. Choose the correct physical method.

   Use sliding mesh when time-resolved interaction is decision-critical.

5. Perform timestep or rotor-position sensitivity.

   Demonstrate that torque, pressure ratio, flow rate or blade loads are stable enough for the intended conclusion.

Common mistakes

• Using MRF and interpreting its steady field as a true time-averaged sliding-mesh solution without checking.
• Specifying rotational speed with the wrong unit or sign.
• Comparing relative velocity inside the rotor directly with absolute velocity in the stator.
• Placing a very coarse stator mesh opposite a finely resolved rotor wake.
• Using too few timesteps per blade-passing period.
• Assuming a periodic sector is valid when inlet distortion or asymmetric geometry breaks periodicity.