Improving tidal turbine performance through multi-rotor fence configurations

Constructive interference between tidal stream turbines in multi-rotor fence configurations arrayed normally to the flow has been shown analytically, computationally, and experimentally to enhance turbine performance. The increased resistance to bypass flow due to the presence of neighbouring turbines allows a static pressure difference to develop in the channel and entrains a greater flow rate through the rotor swept area. Exploiting the potential improvement in turbine performance requires that turbines either be operated at higher tip speed ratios or that turbines are redesigned in order to increase thrust. Recent studies have demonstrated that multi-scale flow dynamics, in which a distinction is made between device-scale and fence-scale flow events, have an important role in the physics of flow past tidal turbine fences partially spanning larger channels. Although the reduction in flow rate through the fence as the turbine thrust level increases has been previously demonstrated, the within-fence variation in turbine performance, and the consequences for overall farm performance, is less well understood. The impact of turbine design and operating conditions, on the performance of a multi-rotor tidal fence is investigated using Reynolds-Averaged Navier-Stokes embedded blade element actuator disk simulations. Fences consisting of four, six, and eight turbines are simulated, and it is demonstrated that the combination of device- and fence-scale flow effects gives rise to cross-fence thrust and power variation. These cross-fence variations are also a function of turbine thrust, and hence design conditions, although it is shown simple turbine control strategies can be adopted in order to reduce the cross-fence variations and improve overall fence performance. As the number of turbines in the fence, and hence fence length, increases, it is shown that the turbines may be designed or operated to achieve higher thrust levels than if the turbines were not deployed in a fence configuration