Skip to main content

reversed flow (backflow)

1 Reverse flow   reversed_flow

It is common to encounter the regions of reversed flow at the initial stages of the simulation – This is normal.

However, if the “reversed flow” warnings do not disappear as the simulation progresses, then one needs to address the issue and move the outlet boundaries to a location where the inflow is no longer encountered.

Normally, it has to do with the outlet boundary condition.

if you were to use the "pressure outlet" boundary condition at the outlet, your outlet must be set far away from the object of interest.

In Fluent, I normally use the " outflow" boundary condition at the outlet and it does not give me reverse flow.

1.1 reasons

It is virtually impossible to prescribe correct values for varying turbulence characteristics, temperature and species concentrations in those cells where the backflow occurs.

  • The number of such “backflow” cells might vary from one iteration to another,

and any discontinuity in calculated turbulence, species and temperature values for the neighbouring “outflow” and “inflow” cells is very likely to have an adverse effect on convergence.

  • The accuracy of the solution can also be affected, especially if the area of interest is located close to the outlet with the “backflow”.

reversed_flow.png

1.2 solutions

> if vortex formation/recirculation of flow near an outlet boundary, 1.2.

> check the mesh quality, improve it.

> use higher order scheme

> At last reduce the relaxation factor if necessary.

Calculation steps:

  • Set up the model and calculate a solution on the initial mesh
  • Please write the interpolation file first.
  • Close the existing Fluent session.
  • Open a new Fluent session and read the case file only.
  • Perform 1.2
  • Check the new zones and ensure that the prescribed outlet boundary conditions are set and named consistently.
  • Initialise the flow.
  • Read in the interpolation file.
  • Continue simulation.

  • The original data file cannot be read onto the new mesh.
  • The new case file need to be initialised.
  • Old data can still be recycled and used again by interpolation:
 file interpolate read-data original_ip_file_name.ip

Mesh/modify-zones/extrude-face-zone-delta 
#specify the face zone id/name i.e. inlet boundary name or zone ID 
distance delta 1 0.2[1]
#first extrusion layer edge length
distance delta 2 0.25 
distance delta 3 0.3 
distance delta 4 
#press “Enter” once a sufficient outlet section has been built[2]***. 

[1] − The offset value does not need to be 0.2 and should be equal to the typical cell edge length close to the original outlet [2] – total extrude layers, 3 cells. To minimise the amount of cells an expansion ratio of 1.2 can be used

  1. Reference
    • 5.9.8. Extruding Face Zones, user guide
    • File “prevent backflow at outlet.fss”
  2. Note:
    • This text command is not available in the parallel version of ANSYS Fluent.

    extrusion is not possible from boundary face zones that have hanging nodes.

    • Extruding face zones is not allowed on polygonal face zones.
    • Extruding face zones is only allowed in the 3D version of ANSYS Fluent.
  3. outlet Extrusion error

    Problem description:

    • mesh/modify-zones/extrude-face-zone-delta
    • Face zone id/name [] 27 #outlet face zone
    • Distance delta(1) [()] 0.1
    • Distance delta(2) [()]
    • Extrude face zone? [yes]
    • Warning: the base thread has multiple adjacent threads!
    • Please separate the extruded side threads manually, and set the boundary condition accordingly.
    • Error: received a fatal signal (Segmentation fault).

Created: 2018-06-24 Sun 15:55

Validate

Comments

Popular posts from this blog

TUI Fluent

‎ Table of Contents 1. TUI 1.1. Examples 1.1.1. Steady 1.1.2. Unsteady 1.2. discretization schemes 1.3. Turbulence model 1.4. Reference 1.5. Save residual 1.6. Journal 1.6.1. record journal GUI 1.6.2. The interactive TUI inside Fluent helps: 1.7. define 1.7.1. boundary-conditions 1.8. change rotational velocity of moving reference frame 1.8.1. batch model 1.8.2. interactive console TUI 1.9. set background color 1.9.1. invalid command [background] 1.10. syntax 1.11. Batch model 1.12. Boundary condition 1.12.1. Inlet BC 1.13. Animation/residual/monitor on cluster 1.14. Solver 1.15. Change pressure-velocity-coupling model in batch mode 1.16. time step size 1.17. Modifying the View 1.18. initialization 1.19. discretization schemes 1.20. Set under relaxation 1.21. log of execute makefile 1 TUI keywords: Background Execution on Linux Systems, journal file Programming language : Scheme , as a Lisp dial

Fluent Error FAQ

  Process 1928: Received signal SIGSEGV. Running on windows Mesh size, 12M serial     Error:  received a fatal signal (Segmentation fault).     Error Object: #f parallel     select 4 processors         error information     Node 0: Process 1928: Received signal SIGSEGV.         Node 5: Process 2824: Received signal SIGSEGV.     MPI Application rank 0 exited before MPI_Finalize() with status 2      The fl process could not be started.         Reason         This is primarily a Windows issue.                 If running Fluent with -t1 or higher number of processes and leave the session for an extended period of time (2-20 hours), it receives the following message in the console:                 The fl process could not be started.                 No other information about what timed out is provided, and only the cortex process is left running. This issue becomes more significant in light of the switch from serial to -t1.         IP interfaces on the machine

Turbulent viscosity limited to viscosity ratio of 1e+05

** Turbulent viscosity limited to viscosity ratio of 1e+05 *** reason The possible *causes* for large turbulent viscosity ratio include: - Bad initial conditions for the turbulence quantities (k and e) - Improper turbulent boundary conditions - Skewed cells *** solution If the problem is not caused by *bad mesh*, then *the beginning of the phenomena* can usually be avoided by: -Turn off solving *turbulence equations* for the first 100-200 iterations -Turn on turbulence and continue iterations If the problem occurs *in the middle of the iteration process*, then use the following procedure: - Stop the iteration - Turn *off* all equations except the *turbulence equations* - Increase turbulence under relaxation factors (URFs) (k and e) to 1 and iterate for 20-50 iterations - *Turn back all equations* and reduce the turbulence URFs to 0.5-0.8 and then continue iterations - Repeat the above steps for several times For *faster convergence*, it might be useful to obtain an initial solution wit