DOI: 10.17028/rd.lboro.13161284.v1
title: Windsor Body Experimental Aerodynamic Dataset

description: This is the dataset for the 25% scale Windsor model, collated by Max Varney (https://www.linkedin.com/in/max-varney/) on 2020/10/27. More information can be found in the following publications:- "Base Drag Reduction for Squareback Road Vehicles", Varney, M., PhD Thesis, Loughborough University, https://doi.org/10.26174/thesis.lboro.11823759.v1- G. Pavia, M. A. Passmore, M. Varney, and G. Hodgson, “Salient three-dimensional features of the turbulent wake of a simplified square-back vehicle,” Journal of Fluid Mechanics, vol. 888, p. A33, 2020. https://hdl.handle.net/2134/11669679.v1<br>Data was collected in the Large Wind Tunnel at Loughborough University, a 2.5m^2, closed working section, fixed ground open return tunnel. Details of the tunnel can be found in: https://hdl.handle.net/2134/6674<br>The CAD geometry for the Windsor model with and without wheels, the mounting hardware and the wind tunnel are all included in the dataset as ASCII .stl files, with the units in m.<br>In all experiments included in this dataset, prior to the start of testing the zero degree yaw condition was found by yawing the model in 0.1 degree increments until a symmetric base pressure was achieved. The yawed data is relative to this aerodynamic 0 yaw.<br>No corrections (for example blockage) have been applied to the data. All the data is presented in SI units and all measurements are from the origin (mid-track, mid-wheelbase on the tunnel floor) with x positive downstream and z positive up, using the right hand rule to find positive y. Positive yaw is then defined as nose towards positive y.<br>The data is presented in two sets:(Set A) relates to the Square back Windsor model with and without wheels at aerodynamic 0 degree yaw. It contains data collected using tomographic PIV plus additional planes of PIV data that provide higher spatial resolution.NOTE: The stereo crossplane data (X=*m) with wheels, uses a different wheel mounting system than that provided in the .stl files. To avoid complication we have not included this geometry in the data set because it is assumed not to have a large effect on the wake structure. The wheels were stationary for the acquisition of these additional planes, and further details of this experiment can be found in the following paper:- Pavia, G. and Passmore, M., “Characterisation of Wake Bi-stability for a Square-Back Geometry with Rotating Wheels,” in: Wiedemann, J., ed., Progress in Vehicle Aerodynamics and Thermal Management, Springer International Publishing, Cham, ISBN 978-3-319-67822-1: 93–109, 2018. also available at https://hdl.handle.net/2134/35518<br>(Set B) Provides additional data for the square back Windsor model at 2.5, 5 and 10 degrees yaw. For zero yaw data researchers are referred to Set A. <br>The data within both set A and B is split into '_Mean' and '_Instantaneous' for the Pressure and Flow Field data, with only '_Mean' data supplied for the Forces. The Force and Pressure data has been captured over a total sample time of 300 seconds. These acquisitions were performed during the same test run, but are not correlated in time. The Force measurements were sampled at 300Hz, whereas the Pressure data was sampled at 260Hz. The PIV measurements were performed during a different test campaign, with individual nominal velocities, sample lengths, and frequencies shown in the README file. The data presented in the '_Mean' folders is the arithmetic mean of that presented in the '_Instantaneous' folders.<br>The tomographic testing uses a lower freestream velocity to ensure that there was sufficient seeding (helium filled soap bubbles) in the region of interest. For more detail on the PIV set ups, please refer to the publications.<br><br>All the '_Mean' and '_Instantaneous' folders contain Comma Separated Variable (csv) files for each configuration and for ease of parsing with your desired programming language. Example MATLAB code has been provided (tested in 2019b) that reads both the '_Mean' and '_Instantaneous' csv files for the Pressure and Flow Field measurements, plotting them accordingly.<br>The 'Force_Mean' folder contains a .csv file for each configuration, with the mean taken over the 300 second acquisition. This file includes the velocity, ambient temperature, ambient pressure, calculated air density, yaw angle, the 3 force and 3 moments (taken about mid-wheelbase mid-track and on the tunnel floor), the model frontal area, model wheelbase, the calculated force and moment coefficients.<br>The 'Pressure_Mean' folder contains two sets of .csv files. '_Tapping_Map', presents the x, y and z positions of the Pressure tappings, the group that they belong to (1 - Vertical Centerline, 2 - Upper Glasshouse, 3 - Front Bumper, 4 - Base) and the associated Pressure tapping number. '_Averages', contains the mean, '_MeanCp', and RMS of the deviation, '_RMSCp'.<br>The 'Pressure_Instantaneous' folder contains a .csv file for each configuration. It also contains the same '_Tapping_Map' csv files provide with the mean Pressures to prevent the need to download both datasets. In this instance each column is a Pressure tapping location and each row is a time instance. Two separate pressure scanners were used during these experiments that cannot be accurately synchronised. As a result if any cross correlation is performed by the user this should ONLY be performed on tapping numbers 1-64 OR 65-128, correlations performed between these groups will result in significant errors.<br>The 'FlowField_Mean' folder contains a .csv file for each configuration and plane. Each .csv file includes the x, y and z coordinate of every vector, the mean and rms of the u, v and w components and the velocity magnitude. Invalid vectors are marked in the dataset with a value of -9999 at the XYZ location (Invalid vectors arise in experimental data due to seeding, image quality or processing problems). The FlowField_Example_Code hides the invalid vectors during plotting.<br>The 'FlowField_Instantaneous' folder contains the same file structure as 'FlowField_Mean' but with the columns representing time steps, indicated by the column header. A simple way to read this is demonstrated in FlowField_Example_Code.