search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Divide et impera


The Roman maxim Divide and Conquer also dictates any successful solution of the Navier-Stokes equation – the root of computational fluid dynamics and one of the few design methodologies common to all four America’s Cup teams racing in New Zealand. So a good moment to revisit the basics with Manuel Fluck


The elevator pitch Computational Fluid Dynamics (CFD) is a very powerful asset in the engineering tool- box for modern sailboat design. Actually, today CFD is so powerful that it has often replaced physical wind tunnel or tank testing. But how can something as compli- cated as the wind flow around two sails be even computed? How does CFD work and what are its limitations? I have tried here to deliver the basic introduction but with- out the maths!


A little more depth When dealing with boat performance analysis or boat rating, one will probably have come across CFD. Some may well have read further about RANS simulations, VLM or other such incarnations of CFD


50 SEAHORSE


which we will look at soon. For some CFD might just be an obscure term the engineers throw around. Either way, Computational Fluid Dynamics is at the core of much work conducted for our sport. For example, when analysing sail forces and optimising sail shape, or assessing hull drag and the efficiency of a foil, CFD now lets us (engi- neers) calculate the forces air and/or water exert on the boat with great accuracy. While CFD is usually much quicker


than any physical (wind tunnel or tank) experiment, it also lets us analyse the com- plicated flow around all parts of the boat such as sails, rig, hull… at a level of detail that is hardly achievable in any physical experiment. One reason is that it is rela- tively easy to zoom into a computer simu- lation to investigate details, whereas a close-up look at a physical experiment is often limited. Think only of the measure- ment instruments used and their interac- tion with the flow – even in the most sophisticated wind tunnel. Thus CFD gives us a superb opportunity to understand in great detail what is going on and to improve our designs relatively quickly. On the other hand, physical experi-


ments are intuitive: if you put two sails into a wind tunnel it is pretty obvious what is going on. You trim the sails, you measure forces and maybe the pressure. Executing a wind tunnel experiment accu- rately is surely not easy, but the process is transparent and seems easy to follow.


CFD, on the other hand, is a bit of a


magical black box. One throws in some model and magically gets out a lot of data. But what is happening in between? How does CFD generate data that can replace wind tunnel experiments? CFD is indeed a powerful tool. How-


ever, with power comes responsibility: the responsibility of the CFD engineer to choose the appropriate tools, and the responsibility of the CFD consumer (project manager, boat owner, or simply interested sailor) to have at least some basic understanding of the amount of truth contained in the pretty pictures generated by the CFD tool. Now let us scratch the surface of this black CFD box and try to get some insight into what is going on behind the scenes…


Some history Already in the early 1800s a French engi- neer and physicist, Claude-Louis Navier, and an Anglo-Irish physicist and mathe- matician, George Gabriel Stokes, indepen- dently developed the famous Navier- Stokes equation. This equation describes the motion of any fluid – which for our purposes is anything that is not solid. The solution of the Navier-Stokes equa-


tion provides everything we are interested in when talking about fluid dynamics: flow velocity, density and pressure at any point in space and any instance in time. However, I promised no maths. And I will


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110