Investigates flame flashback over rough walls, revealing key insights into combustion dynamics.
Rough walls are commonly encountered in engineering applications. However, existing understanding of combustion in the turbulent boundary layer over rough walls is lacking. This study investigates turbulent boundary layer premixed flame flashback over rough walls using direct numerical simulations for the first time. The features of boundary layer flashback over walls with various roughness are explored in terms of flame morphology and flashback speed. It is found that the flame in rough-wall cases is more wrinkled compared with the smooth-wall case, particularly in the near-wall region, due to the presence of more small-scale vortical structures. Wall roughness reduces the flame flashback speed, which is attributed to the higher flow velocity at the leading edge of the flame front in rough-wall cases. The effects of wall roughness and combustion on boundary layer turbulence are revealed through two-point correlations of fluctuating velocity and wall resistance. The results show that, under non-reacting conditions, wall roughness reduces the streamwise and wall-normal extents of near-wall hairpin packets of boundary layer turbulence while increasing their inclination angles. Under reacting conditions, combustion further increases the inclination angle, with a more pronounced effect in rough-wall cases. Wall roughness influences wall resistance, primarily through its pressure component. Flame/wall interactions are also scrutinised, revealing higher wall heat loss in rough-wall cases, which is is mainly attributed to the increased wall surface area. A negative correlation between the quenching distance and the alignment of flame normal and wall normal is observed in rough-wall cases, which is weaker in smooth-wall cases.
No takes yet. Share an insight, caveat, or question.
Zhu et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: