Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
517
datasets available to search
ShareScore release 0.9.0
Dataset results
517 results for “Turbulence”
Laboratory measurements of wind, waves, and turbulence in hurricane conditions in the ASIST wind-wave facility
<p>Laboratory measurements of wind, waves, and turbulence in hurricane conditions, collected in September and October of 2018 and January of 2019 in the ASIST wind-wave facility, in the SUSTAIN laboratory at the University of Miami.</p> <p>This dataset includes two experiments, one with fresh water ("fresh") and another with seawater ("salt"), each in 10-m winds from 0 to approximately 42 m/s. Data include:</p> <ul> <li>3-dimensional wind velocity at 20 Hz sampling frequency from Campbell Scientific IRGASON sonic anemometer (collected in 2018)</li> <li>2-dimensional (along-tank and vertical) wind velocity at 1000 Hz sampling frequency from TSI IFA-300 hot film anemometer (collected in 2018)</li> <li>1-dimensional (along-tank) wind velocity at 10 Hz sampling frequency from a pitot anemometer (collected in 2018 and 2019)</li> <li>3-dimensional water velocity in the bottom 5 cm of the tank at 100 Hz sampling velocity from Nortek Vectrino velocimeter. (collected in 2018)</li> <li>Water elevation at 20 Hz sampling frequency at 6 locations in the tank from Senix Toughsonic 30 ultrasonic distance meters (collected in 2019)</li> <li>Along-tank static air pressure difference at 10 Hz sampling frequency from Baratron MKS 226 differential pressure transducer (collected in 2019)</li> </ul> <p>All data is in NetCDF4 format.</p> <p>Experiment set up and positions of instruments are documented in more detail in Curcic and Haus (2020), Revised estimates of ocean surface drag in strong winds, <em>Geophysical Research Letters</em>, <a href="https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2020GL087647">https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2020GL087647</a>.</p> <p>Produced as part of the National Science Foundation Award #1745384, titled "Air-Sea Momentum Transfer in Extreme Wind Conditions"<strong>.</strong></p> <p>Contact: Milan Curcic <mcurcic@miami.edu></p>
Datasets for: Generalizing Monin-Obukhov Similarity Theory (1954) for Complex Atmospheric Turbulence, Stiperski and Calaf 2023, PRL
<p>Scaling variables for the generalized flux-variance scaling relations that include turbulence anisotropy. Dataset is a companion to the manuscript Stiperski, I., Calaf, M., 2023: Generalizing Monin-Obukhov similarity theory (1954) for complex atmospheric turbulence. Physical Review Letters, 130 (12), 124001, https://doi.org/10.1103/PhysRevLett.130.124001</p> <p>The dataset contains the turbulence statistics from 13 datasets: AHATS, Cabauw, CASES-99, METCRAX II campaign (NEAR and RIM towers), T-Rex campaign (Central tower - TRexC, West tower - TRexW) and i-Box measurement network (CCS-VF0 tower - i-Box0, CS-SF1 tower - i-Box1, CS-NF10 tower - i-Box10, CS-NF27 tower - i-Box27, CS-MT21 tower - i-BoxTop, im Hinteren Eis tower - imHint).</p> <p><br>Data are organized in csv files for each datasets and only contain high quality (for applied criteria see the Supplemental Material of the companion paper, https://journals.aps.org/prl/supplemental/10.1103/PhysRevLett.130.124001) data with 30 min averaging for unstable stratification and 1 min for stable stratification. Since the data were used for scaling, there is no reference to time, but the measurement height is provided as an additional variable. </p> <p>Meaning of variables:</p> <p>zeta - z/L where z is height above ground and L is the local Obukhov length</p> <p>SigmaU - $\overline{u'u'}/u_*$ scaled standard deviation of streamwise velocity, where $u_*$ is the local friction velocity</p> <p>SigmaU - $\overline{v'v'}/u_*$ scaled standard deviation of spanwise velocity</p> <p>SigmaU - $\overline{v'v'}/u_*$ scaled standard deviation of surface-normal velocity</p> <p>SigmaT - $\overline{T'T'}/T_*$ scaled standard deviation of sonic temperature, where $T_*$ is the local temperature scale</p> <p>SigmaEpsU - scaled dissipation rate of the streamwise velocity</p> <p>SigmaEpsW - scaled dissipation rate of the surface-normal velocity </p>
QuaLiKiz-v2.6.2 turbulent transport model evaluations based on JET experimental plasma profiles
<p>This dataset was used to train the QuaLiKiz-neural-network (QLKNN) model, QLKNN-jetexp-15D, described within the following published article: <a href="https://doi.org/10.1063/5.0038290">https://doi.org/10.1063/5.0038290</a>. It was generated with approximately 33 million standalone evaluations of QuaLiKiz-v2.6.2, each performed with a standard vector of 18 wavenumbers. Only approximately 21 million of these are kept for training due to various consistency checks applied to the code outputs. More information about the QuaLiKiz code can be found at <a href="https://www.qualikiz.com">www.qualikiz.com</a>.</p> <p>The data is saved under 3 keys in HDF5 format: "/input", "/output", and "/label". The inputs to the QuaLiKiz evaluations are provided under "/input", representing the local plasma parameters extracted from experimental measurements from the JET plasma device in Culham, UK, along with variations of select parameters according to propagated experimental uncertainties. Selected relevant outputs of the QuaLiKiz evaluations are provided under "/output", namely the local turbulent transport coefficients after applying a semi-empirical turbulent fluctuation saturation rule. Some useful metadata is provided under "/label", giving some degree of provenance tracking back to the JET experimental database, as well as describing the applied parameter variations and explaining why certain output rows were removed from the output structure.</p>
Flume Experiment Testing the Impact of Artificial Streambank Roots on Velocity, Reynold's Shear Stress, and Turbulent Kinetic Energy using an Acoustic Doppler Profiler
The data published here is expected to accompany one publicly available dissertation (Chapter 4 of dissertation) and one separate journal publication. Once published and available online, the metadata will be updated with the relevant article information. The journal article/dissertation will have additional information regarding the published datasets and the methods used to collect the data. All data collected from these studies, and the accompanying Acoustic Doppler Profiler MATLAB files, are presented here. Journal Article title: Impact of Flexible and Rigid Artificial Roots on Stream Hydrodynamics
Wind measurement data from the publication: "Development of a load model validation framework applied to synthetic turbulent wind field evaluation"
<h3>Dataset description:</h3> <p>This datasat represents supplementary material used in the contribution "Development of a load model validation framework applied to<br>synthetic turbulent wind field evaluation" by Meyer, Huhn and Gottschall.</p> <p>Wind measurements from the Testfeld BHV are made available. For installation details, see the mentioned reference.</p> <p> </p> <h3>File description:</h3> <ul> <li>Lidar_HWS.nc - Horizontal wind speed measurements (10 min averages) from a WindCube V2 vertical profiler for one day with a low-level jet occurrence ( <div> <div>2021-04-20)</div> </div> </li> <li>Cups_HWS.nc - Horizontal wind speed measurements (10 min averages) from cup anemometer installed on a met mast for the same day</li> <li>Ensemble_averaged_Spectra.nc - Ensemble averaged spectra for neutral and near neutral situations from a Gill Windmaster at 110m above ground level, used to fit the Mann and KSEC model parameters</li> </ul> <h3> </h3> <h3>Referencing:</h3> <p>When used, please cite like the following:</p> <p>Meyer, Paul J., Matthias L. Huhn, and Julia Gottschall. 2024. "Development of a Load Model Validation Framework Applied to Synthetic Turbulent Wind Field Evaluation" <em>Energies</em> 17, no. 4: 797. https://doi.org/10.3390/en17040797</p> <p> </p> <p> </p>
Vertical profiles of urban wind speed, wind direction and turbulence measured by LiDAR on campus of University College Cork, Ireland
<p><strong>Vertical Profiles of Urban wind speed, wind direction and turbulence measured by LiDAR on campus of University College Cork, Ireland</strong></p> <p>=================================</p> <p>README version 1.3, 21/07/2022</p> <p>==================================</p> <p>Contact info:</p> <p>Paul Leahy, University College Cork</p> <p>paul.leahy@ucc.ie | +353 21 4902017</p> <p>================================</p> <p> </p> <p><strong>Contents</strong></p> <p><strong>1. Measurement location and time period</strong></p> <p><strong>2. What is measured (brief description)</strong></p> <p><strong>3. Instrumentation</strong></p> <p><strong>4. CSV file detailed descriptions</strong></p> <p>================================</p> <p> </p> <p><strong>1. Measurement location and time period: </strong></p> <p>North roof of Kane Building, University College Cork (UCC), Ireland.</p> <p>Lat 51 d 53 m 34 s N.</p> <p>Long 8 d 29 m 39 s W.</p> <p>Roof is c. 39 m above sea level, and c. 26 m above ground level (ground level reference point is the car park West of the UCC Kane Building).</p> <p>The measurements were taken over a time period of several months in the years 2013 / 2014.</p> <p>=================================</p> <p><strong>2. What is measured (brief description):</strong></p> <p>* LiDAR Wind speed (horizontal and vertical), wind direction, turbulence intensity at 5 altitudes; reference point (0 m) for these altitudes is the top of the LiDAR instrument c. 1.2 m above roof level.</p> <p>* Air temperature, atmospheric pressure, relative humidity.</p> <p>* Wind speed and direction from an ultrasonic anemometer mounted on top of the instrument (c. 1.2 m above roof level).</p> <p>* 10-minute average values (2 files) and high-resolution (c. 23 sec) data (1 file) are provided.</p> <p>See 'CSV file detailed description' below for detailed information.</p> <p>* Diagnostic information.</p> <p>=================================</p> <p><strong>2.1 Surrounding terrain:</strong></p> <p>Surrounding area is urban/suburban. The aspect is northerly.</p> <p>To the West: 2-5 storey buildings, open spaces, suburban.</p> <p>To the South: 2-3 storey buildings, open spaces, trees, river.</p> <p>To the East: 2-3 storey buildings, open spaces.</p> <p>To the North: A higher section of the Kane Building roof (47 m asl), 1-3 storey buildings, suburban.</p> <p>=================================</p> <p><strong>3. Instrumentation:</strong></p> <p>ZephIR 175 continuous wave wind profiling LiDAR with integrated sonic anemometer, temperature, humidity, air temperature pressure sensors and GPS.</p> <p>=================================</p> <p><strong>4. CSV files detailed description:</strong></p> <p><strong>4.1 Data on 10-minute averages:</strong></p> <p>Filename 05092013-03122013_10min_res.csv contains:</p> <p>10 minute averaged data from 05/09/2013 to 03/12/2013.</p> <p>Measurement altitudes: 148 m, 90 m, 69 m, 44 m, 19m above instrument level.</p> <p> </p> <p>Filename 03122013-07082014_10min_res.csv contains:</p> <p>10 minute averaged data from: 03/12/2013 to 07/08/2014.</p> <p>Measurement altitudes: 148 m, 90 m, 50 m, 35 m, 15 m above instrument level.</p> <p>Note: from 19/06/2014 onwards, LiDAR data missing (MET data continues).</p> <p> </p> <p>The first two rows contain header information.</p> <p>Row 1 contains location information (GPS record)) and the measurement altitudes for wind speeds.</p> <p>Sample GPS record: N51535775W8296590 = 51 d 53.5775 m North; 8 d 29.6590 m West.</p> <p>Row 2 contains the data column headers including units.</p> <p> </p> <p>Wind speeds at each altitude are recorded:</p> <p>No of Packets (= number of scan units averaged over) []</p> <p>Wind direction (mean) [deg]</p> <p>Horizontal wind speed (mean) & standard deviation [m/s]</p> <p>Vertical wind speed (mean) & standard deviation [m/s]</p> <p>Horizontal variance [m^2/s^2] </p> <p>Horizontal min [m/s] </p> <p>Horizontal max [m/s] </p> <p>TI (turbulence intensity) []</p> <p> </p> <p>Other meteorological data:</p> <p>Air temperature [<sup>o</sup>C]</p> <p>Pressure [mbar]</p> <p>Rel. Humidity [%]</p> <p>Rain indicator [unitless] Higher values indicate more rain during the averaging interval.</p> <p>Wind Speed [m/s] (column 'MET Wind Speed' measured at the top of the instrument by the ultrasonic anemometer)</p> <p>Wind direction [deg] (column 'MET Direction' measured at the top of the instrument by the ultrasonic anemometer).</p> <p> </p> <p>Other housekeeping and diagnostic data:</p> <p>Instrument tilt [deg]</p> <p>Instrument bearing [deg]</p> <p>GPS data [degrees N, degrees W]</p> <p>Battery voltage [V] </p> <p>Optics, electronics and battery temperature [<sup>o</sup>C]</p> <p> </p> <p>=====================================================</p> <p> </p> <p><strong>4.2 Data with high time resolution (~23 s):</strong></p> <p> </p> <p>Filename 05092013-11112013_23s_res.csv contains:</p> <p>High resolution data from 05/09/2013 to 11/11/2013</p> <p>Measurement altitudes: 148 m, 90 m, 69 m, 44 m, 19m.</p> <p> </p> <p>Note on time resolution:</p> <p>The time resolution of processed wind measurements is c. 3 seconds per wind level, and around 8 seconds to reset to the first level. A full wind profile measurement at 5 altitudes therefore takes around (5 x 3) + 8 = 23 s to complete.</p> <p>The raw scanning resolution of the instrument is higher than this, as each wind measurement is an average of several values.</p> <p> </p> <p>Row 1 contains location information (lat, long) and the vertical measurement levels for wind speeds.</p> <p>Row 2 contains the data column headers including units.</p> <p> </p> <p>Wind speeds at each altitude are recorded:</p> <p>No of Packets (= scan units averaged over) []</p> <p>Wind direction (mean) [deg]</p> <p>Horizontal wind speed (mean) & standard deviation [m/s]</p> <p>Vertical wind speed (mean) & standard deviation [m/s]</p> <p>Horizontal variance [m^2/s^2] not defined as measurement interval is too short.</p> <p>Horizontal min [m/s] not defined as measurement interval is too short. </p> <p>Horizontal max [m/s] not defined as measurement interval is too short. </p> <p>TI (turbulence intensity) [] not defined as measurement interval is too short.</p> <p> </p> <p>Other meteorological data:</p> <p>Air temperature [<sup>o</sup>C]</p> <p>Pressure [mbar]</p> <p>Rel. Humidity [%]</p> <p>Rain indicator [unitless] Higher values indicate more rain during the scanning interval.</p> <p>Wind Speed [m/s] (column 'MET Wind Speed' measured at the top of the instrument by the ultrasonic anemometer)</p> <p>Wind direction [deg] (column 'MET Direction' measured at the top of the instrument by the ultrasonic anemometer.</p> <p> </p> <p>Other housekeeping and diagnostic data:</p> <p>Instrument tilt [deg]</p> <p>Instrument bearing [deg]</p> <p>GPS data [degrees N, degrees W]</p> <p>Battery voltage [V] </p> <p>Optics, electronics and battery temperature [<sup>o</sup>C]</p> <p> </p> <p>=====================================================</p> <p><strong>4.3 Quality control indicators:</strong></p> <p> </p> <p>9998 atmospheric conditions which adversely affect LiDAR wind speed measurements e.g. fog</p> <p>9999 high quality wind speed measurement not possible e.g. very low wind speed or obscuration of optical path</p> <p>Status Flag 'Green' => good</p> <p>=======================================================</p> <p> </p>
Costal operating wind farms: two datasets with concurrent SCADA, LiDAR and turbulent fluxes
<p>This data collection consists of two datasets from a micrometeorological experiment conducted in two distinct operating wind farms in a coastal area of the northeast region of Brazil, called Pedra do Sal Wind Farm (UEPS) and Beberibe Wind Farm (UEBB). These wind farms are located on the northeast coast of Brazil where meteorological conditions are strongly influenced by trade winds and sea breeze. Both datasets represent a full-year of measurements from August/2013 to July/2014.</p> <p>On both operating wind farms it was commissioned a fully instrumented IEC-compliant 100m met mast, with five levels of first-class calibrated cup anemometers and one level (100m) with 3D sonic anemometer. Additionally at UEPS there's an extra 3D sonic at 20m height on the met mast, as well as a VAISALA LEOSPHERE Windcube8 doppler wind lidar with a range up to 500m height and located 2.5D upwind of one of the wind turbines.</p> <p>The Pedra do Sal wind farm (UEPS) has an installed capacity of 18MW, with 20 Enercon E-44 installed at 55m a.g.l. At Beberibe wind farm (UEBB) there are 32 Enercon E-48 wind turbines installed at 75m a.g.l. The dataset includes 10min SCADA data for all wind turbines on both wind farms.</p> <p>This dataset has a high-quality combination of meteorological, SCADA and turbulent flux data of two operating wind farms in Brazil. During a full-year of measurements both datasets had a high data recovery rate (see attached tables). The dataset has already been used to assess the impact of atmospheric stability on the wind farm performance, as well as the effect of mesoscale patterns on the wind profile and wind farm power production. Recirculation of the sea breeze and the development of an internal boundary layer upwind the wind turbines were also characterized.</p> <p>For more details on the experimental layout, wind turbine locations, meso and microcale wind conditions and any other information not stated in the NetCDF4 files, please refer to the reference material or contact one of the authors.</p> <p> </p>
Segmenting magnetized plasma turbulence with aweSOM
<p>This dataset contains a snapshot of a fully kinetic particle-in-cell simulation of freely evolving plasma turbulence, as described in <a href="https://iopscience.iop.org/article/10.3847/1538-4357/ac1c76" target="_blank" rel="noopener">Nättilä & Beloborodov (2021)</a>.</p> <p>This dataset was used in the analysis of <a href="https://arxiv.org/abs/2410.01878" target="_blank" rel="noopener">Ha et al. (2024)</a> and partially to develop <a href="https://github.com/tvh0021/aweSOM"><strong>aweSOM</strong></a>.</p> <p>See the section: "Example : Intermittency detection in decaying plasma turbulence simulation" in the documentation of <strong>aweSOM</strong> for instructions on how to use these datasets.</p>
X-ray radiography 4D particle tracking of heavy spheres suspended in a turbulent jet
<p>This database report 3d trajectories of heavy spheres suspended in a turbulent upward jet. A cylindrical tank is filled with water and the jet nozzle is placed on its axis on the bottom wall, and a constant flowrate (Q) of water is fed through the nozzle. Conditions at 1700 and 2200 mL/min are considered, and the number of spheres is varied between 1 and 12 (Nsphere). The spheres are glass and are detected using X-ray radiography at 60Hz. The 4d kinematics are obtained with this setup using radioSphere (E. Ando et<br> al., Measurement Science and Technology, 32(9), 095405, 2021). Each condition has a series of files named based on the number of spheres in the tank Nsphere and the flowrate Q, with each sphere of index isphere having its own file. Each file is 3 columns of doubles representing the 3d coordinates x, y, and z of the sphere, in mm, where z is the axis of the cylinder and the points up, against gravity.</p> <p>Results from this database are published here: https://doi.org/10.1016/j.ijmultiphaseflow.2023.104406<br> O. Stamati, B. Marks, E. Ando, S. Roux, N. Machicoane, X-ray radiography 4D particle tracking of heavy spheres suspended in a turbulent jet, <em>International Journal of Multiphase Flow</em> 162, 104406, 2023.</p>
Experimental data for the manuscript titled Rotating quantum wave turbulence
<p>This submission contains the minimal dataset required to reproduce the experimental findings related to the manuscript titled <em>Rotating quantum wave turbulence</em>, associated with the DOI 10.1038/s41567-023-01966-z.</p>
Application of two-step clustering algorithm to QuaLiKiz-v2.6.2 turbulent transport simulation data
<p>QuaLiKiz simulation data in support of the two-step clustering algorithm, developed by Bart J. J. Kremers.</p> <p>The NETCDF file, generated via NETCDF4, contains the raw QuaLiKiz output for the 3-dimensional (2-input, 1-output) toy case used to develop the algorithm. Within the NETCDF file, the coordinates represent the code inputs and various vector indices and the data variables represent the code outputs.</p> <p>There are also 4 HDF5 files, containing the results from the two-step clustering reduction algorithm, where the data is saved under 2 keys: "/input" and "/flattened". The file names indicate the reduction algorithm settings used to produce the results within.</p> <p>The algorithm is available open-source at <a href="https://gitlab.com/BartKremers/two-step-clustering">https://gitlab.com/BartKremers/two-step-clustering</a>.</p>
Multi-fidelity Generative Deep Learning Turbulent Flows
<p>Data sets for the two numerical examples in the paper <a href="https://arxiv.org/abs/2006.04731">Multi-fidelity Generative Deep Learning Turbulent Flows</a> as well as two pre-trained models. In this work, a novel multi-fidelity deep generative model is introduced for the surrogate modeling of high-fidelity turbulent flow fields given the solution of a computationally inexpensive but inaccurate low-fidelity solver. The resulting surrogate is able to generate physically accurate turbulent realizations at a computational cost magnitudes lower than that of a high-fidelity simulation. The deep generative model developed is a conditional invertible neural network, built with normalizing flows, with recurrent LSTM connections that allow for stable training of transient systems with high predictive accuracy. Data is provided from OpenFOAM LES simulations for turbulent flow over backwards step and flow around an array of cylinders.</p> <p>Data-set Files:</p> <ul> <li><a href="https://zenodo.org/api/files/cf158661-2a30-4c8f-aa97-cd5c1600910c/backward_step_testing.tar.gz?versionId=320a523f-0015-4ba3-8c6e-66733ab5a1af">backward_step_testing.tar.gz</a> - Backward step testing data.</li> <li><a href="https://zenodo.org/api/files/cf158661-2a30-4c8f-aa97-cd5c1600910c/backward_step_training.tar.gz?versionId=ac34ac15-973d-4fb8-8881-faa17eced69f">backward_step_training.tar.gz</a> - Backward step training data.</li> <li><a href="https://zenodo.org/api/files/cf158661-2a30-4c8f-aa97-cd5c1600910c/cylinder_array_testing.tar.gz?versionId=ebbea725-c8b6-4338-978b-dc73f943552e">cylinder_array_testing.tar.gz</a> - Cylinder array testing data.</li> <li><a href="https://zenodo.org/api/files/cf158661-2a30-4c8f-aa97-cd5c1600910c/cylinder_array_training.tar.gz?versionId=b0409c34-fb19-45c4-bbba-6968fdcfc4d8">cylinder_array_training.tar.gz</a> - Cylinder array training data.</li> </ul> <p>Pre-trained Models:</p> <ul> <li><a href="https://zenodo.org/api/files/cf158661-2a30-4c8f-aa97-cd5c1600910c/bstepWorkspace400.zip">bstepWorkspace400.zip</a> - Backward step pre-trained model.</li> <li><a href="https://zenodo.org/api/files/cf158661-2a30-4c8f-aa97-cd5c1600910c/cylinderWorkspace400.zip">cylinderWorkspace400.zip</a> - Cylinder array pre-trained model.</li> </ul> <p> </p>
Three-dimensional magnetic reconnection in particle-in-cell simulations of anisotropic plasma turbulence (Simulation Data)
<p>This folder contains the output of the following simulation: </p> <p>We use the explicit Plasma Simulation Code (PSC, Germaschewski et al.2016) to simulate eight anisotropic counter-propagating Alfvén waves in an ion-electron plasma. The anisotropy of the initial fluctuation is set up according to the theory of critical balance by Sridhar & Goldreich (1994) and Goldreich & Sridhar (1995) at the small scale end of the inertial range: <span class="math-tex">\(k_{\parallel} d_{i} = C (|k_{\perp}|d_{i})^{2/3}\)</span>, where <span class="math-tex">\(C= 10^{-4/3}\)</span>. The normalization parameters are the speed of light <span class="math-tex">\(c = 1\)</span>, the vacuum permittivity <span class="math-tex">\(\epsilon_{0} = 1\)</span>, the magnetic permeability <span class="math-tex">\(\mu_{0} = 1\)</span>, the Boltzmann constant <span class="math-tex">\(k_{b}=1\)</span>, the elementary charge <span class="math-tex">\(q=1\)</span>, the ion mass <span class="math-tex">\(m_{i}=1\)</span>, the density of ions and electrons <span class="math-tex">\(n_{i}=n_{e}=1\)</span> and the ion inertial length <span class="math-tex">\(d_{i}=c/\omega_{pi}\)</span> where <span class="math-tex">\(\omega_{pi}=\sqrt{n_{i}q^{2}/m_{i}\epsilon_{0}}\)</span> is the ion plasma frequency. We set <span class="math-tex">\(\beta_{s,\parallel}=1\)</span> and <span class="math-tex">\(T_{s,\parallel}/T_{s,\perp}=1\)</span>, where <span class="math-tex">\(\beta_{s,\parallel}=2 n_s \mu_{0} k_{B}T_{s,\parallel}/B_{0}^{2}\)</span> is the ratio between the plasma pressure parallel to the background magnetic field <span class="math-tex">\(\mathbf{B}_{0}\)</span> and the magnetic pressure and $T_{s,\parallel}$ is the parallel temperature. The magnetic field is normalised to <span class="math-tex">\(B_{0}=V_{A}/c\)</span>, where <span class="math-tex">\(V_{A}=B_{0} / \sqrt{\mu_{0}n_{i}m_{i}}\)</span> is the ion Alfvén speed. We use 100 particles per cell (100 ions and 100 electrons), a mass ratio of <span class="math-tex">\(m_{i}/m_{e} = 100\)</span> so that <span class="math-tex">\(d_e = 0.1 d_{i}\)</span> where <span class="math-tex">\(m_{e}\)</span> is the electron mass and <span class="math-tex">\(d_{e}\)</span> is the electron inertial length. The simulation box size is <span class="math-tex">\(L_{x} \times L_{y} \times L_{z} = 24d_{i}\times24d_{i}\times125d_{i}\)</span> and the spatial resolution is <span class="math-tex">\(\Delta x =\Delta y = \Delta z = 0.06d_{i}\)</span>. We use a time step <span class="math-tex">\(\Delta t =0.06/ \omega_{pi}\)</span>. In our normalisation, the Debye length <span class="math-tex">\(\lambda_{D}=d_{i}\sqrt{\beta_{i}/2}V_{A}/c\)</span> defines the minimum spatial distance that needs to be resolve in the simulation and <span class="math-tex">\(\lambda_D=0.07d_i\)</span>.</p> <p>This output corresponds to <span class="math-tex">\(t=120 \omega_{pi}\)</span>. </p> <p>These data were produced using the Data Intensive at Leicester (DIaL) facility provided by the DiRAC project<br> dp126 "Identifying and Quantifying the Role of Magnetic Reconnection in Space Plasma Turbulence".</p>
Auralization of virtual microphone array sensors considering coherence loss by atmospheric turbulence for two moving monopole sources
Open the record for dataset details and reuse information.
Quasi-stationarity of scalar turbulent mixing statistics
<p>Dataset underlying the conclusions of the paper "Quasi-stationarity of scalar turbulent mixing statistics" to appear in Physics of Fluids.</p> <p>A copy of the article for exclusive personal use has been added. Any other use requires prior permission of author and AIP Publishing. The article appeared in <em>Physics of Fluids 33(5):055109 (2021) </em>and may be found at https://doi.org/10.1063/5.0044400</p>
Virtual RHI lidar scans retrieved in high-fidelity wake vortex simulations of landing aircraft under turbulent crosswind conditions - LES Lidar Simulator (LLS)
<p>This dataset contains two types of virtual measurements of multiple pulsed lidar integrated into high-fidelity hybrid RANS-LES wake vortex simulations of a landing Airbus A340 aircraft. Simulations have been performed for four different atmospheric conditions, varying in crosswind and therefore turbulence in the atmosphere.</p> <p>The two lidar simulator types are:</p> <ul> <li>LLS: LES Lidar Simulator (no noise, Signal to Noise Ratio >> 1). The analysis is based on the Range Gate Weighting function (RWF) [based on formulations in for example [1]]. Given the assumption of no instrument noise, no spectral analysis in the frequency domain is required.</li> <li>LLSn: LES Lidar Simulator with noise (realisitic Signal to Noise Ratio). Based on formulations in [2], where non-linear low-pass spatial filters accurately model real field measurements. Both background noise and aerosol noise contained in real lidar measurements are modeled. </li> </ul> <p>Provided are the raw lidar scans in RHI format, with the position and strength of the wake vortices within each lidar scan given by a pressure-vorticity tracking algorithm from the wake vortex simulation (simulation truth, ST). Misidentifications have been removed from the provided dataset. In addition to the labels for each wake vortex lidar scan, also wind background scans are provided for the crosswind simulation cases. These background scans give a better understanding of the prevailing atmospheric condition within which the aircraft lands. </p> <p>Furthermore the evaluation of the LLS scans using the Method of Radial Velocities (RV method) [3], a state-of-the-art wake vortex characterization method for lidar scans is provided for a subset of the LLS dataset. For analysing the impact of the RWF for LLS scans, selected lidar scans are also given in a 'naive' fashion (lidar scans assuming point measurements are possible).</p> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <h3><strong>Overview</strong></h3> <p><strong>In total each dataset (LLS and LLSn) contains 8 Aircraft landing simulation with associated </strong><strong>virtual lidar RHI scans:</strong></p> <ul> <li>2x no wind</li> <li>6x crosswind (specified at height b_0)</li> <li>0.5w_0 from port direction</li> <li>0.5w_0 from starboard direction</li> <li>1.0w_0 from port direction</li> <li>1.0w_0 from starboard direction</li> <li>2.0w_0 from port direction</li> <li>2.0w_0 from starboard direction</li> </ul> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <h3><strong>The dataset has 13 folders:</strong></h3> <div> <p><strong>POS1_POS2_POS8_scans = Individual scans of various simulations as well as background wind scans (no wake vortices). </strong></p> <p>POS1_POS2: 0_0, 0_5, 1_0, 2_0 corresponds to the wind, same as POS1_POS2 below</p> <p>POS8: LLS or LLSn, corresponding to the type of lidar simulator (without or with instrument noise, respectively)</p> </div> <div> </div> <div>Scan naming convention: POS1_POS2_POS3_POS4_POS5_POS6_POS7.csv</div> <div> </div> <div>Example: 0_5_D_248_8_161.2201878198302_168.4201878198237.csv</div> <div> </div> <div> <ul> <li>POS1_POS2: Together they form a factor which is multiplied with the initial descend speed of the wake vortex pair, w_0. The definition for w_0 can be found in [4]. It is common for the crosswind speed to be set according to the multiples of w_0. Due to the landing of the A340 aircraft, and the logarithmic nature of the wind simulation, we set the crosswind at the b_0 altitude of the simulation. For a definition of b_0, also see [4]. For the above example, 0.5w_0 is the crosswind speed. Note that every 26 lidar positions (POS4), the direction of the crosswind changes, if there is a crosswind.</li> </ul> </div> <div> - Crosswind approaches from port side: POS4: 0-25, 52-77, 104-129, 156-181, 208-233, 260-285</div> <div> - Crosswind approaches from starboard side: POS4: 26-51, 78-103, 130-155, 182-207, 234-259, 286-311</div> <div> <ul> <li>POS3: Label indicating which part of the numerical simulation this scan belongs to (a full landing simulation consists of A-D). A: Hybrid RANS-LES, B,C,D: temporal LES (in order). For the above example, D indicates that the lidar scan was recorded during the last part of the simulation. W: Prior to the wake vortex simulations with crosswind, a background wind scan for each lidar position is recorded.</li> </ul> </div> <div> <ul> <li>POS4: Specifies the number of the lidar, implications are the longitudinal position along the glide path of the aircraft. In the packs of lidar positions described in the description of POS1_POS2, the last lidar position is the closest to the touchdown point of the aircraft, smaller lidar positions within this pack are further away (in order) - also see the lid_plane_info directory. Note that the lidar position also adjusts the spectrum of the elevation angles used (and thus the size of the lidar scan). For that see the associated virtual lidar scan raw data. In the above example we have lidar position 248, thus crosswind approaching from starboard and rather mid-way of the longitudinal glide path direction.</li> </ul> </div> <div> <ul> <li>POS5: Specifies the number of the scan for this lidar position (POS4) and simulation (POS1__POS2). In the above example this is scan number 8.</li> </ul> </div> <div> <ul> <li>POS6_POS7: Specifies the simulation time within which the scan was measured during the aircraft landing simulation (POS1__POS2). In the above example this is 161.2201878198302 s to 168.4201878198237 s.</li> </ul> </div> <div>The scans purely with wind, an no wake vortices are stored in an additional directory within conv_scans. The case '0_0' (no wind) does not require wind scans. </div> <div> </div> <div>Within the scan files, we have a four (LLS) or five (LLSn) columns:</div> <div> <ul> <li>t: Simulation time</li> <li>ELE: Elevation angle [deg] of the lidar beam</li> <li>R: Range from lidar [m]</li> <li>v_r: LOS velocity (radial velocity) along lidar beam</li> <li>snr: Signal to Noise Ratio </li> </ul> <p> </p> <p><strong>wind_POS8_scans = Simulated lidar scans of the background wind for LLS and LLSn.</strong></p> <p>POS8: LLS or LLSn, corresponding to the type of lidar simulator (without or with instrument noise, respectively)</p> <p>Scans simulated here are in the same format as <em>POS1_POS2_POS8_scans</em>. Wind scans for point measurement scans are found in <em>naive_scan_subset </em>- the scans with POS4 = 0 should be used if more are available.</p> <p> </p> <p><strong>naive_scan_subset = Simulated lidar scans simulating velocity point measurements.</strong></p> </div> <div> <p>The format is the same as for <em>POS1_POS2_POS8_scans</em>, with the difference of being sorted first by wind subdirectories and then lidar number (LID).</p> <p> </p> <p><strong>labels = Labels of wake vortices for the above wake vortex scans. </strong></p> </div> <div>We have 4 main files, where each file represents the targets for one wind strength 0.0w_0, 0.5w_0, 1.0w_0, 2.0w_0.</div> <div>Within the labels files, we have a multitude of columns with different data:</div> <div> <ul> <li>#Time: Simulation (not scan) time.</li> <li>y_uw : lateral position in simulation domain of upwind (port) vortex.</li> <li>z_uw : height position in simulation domain of upwind (port) vortex.</li> <li>y_dw : lateral position in simulation domain of downwind (starboard) vortex.</li> <li>z_dw : height position in simulation domain of downwind (starboard) vortex.</li> <li>G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex [m^2/s].</li> <li>G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex [m^2/s].</li> <li>cr_uw: Core radius of upwind (port) vortex (in meters).</li> <li>cr_dw: Core radius of downwind (starboard) vortex (in meters).</li> <li>uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar.</li> <li>dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar.</li> <li>uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m).</li> <li>dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m).</li> <li>vortex age uw [s]: Age of upwind (port) vortex (after first generated by aircraft at respective measurement plane of lidar).</li> <li>vortex age dw [s]: Age of downwind (starboard) vortex (after first generated by aircraft at respective measurement plane of lidar).</li> <li>scan: Associated scan.</li> <li>LID: Associated lidar number.</li> </ul> <p>On top of the summarizing files for each simulation, in the subdirectory <em>individual</em>, the label for each scan is given in a separate file.</p> <p>The above gives information on the simulation truth, furthermore the file <em>labels_with_rv.csv</em> can be found here, where the following extra label columns are given for a subset of scans: [in the following Conv and Naive refer to LLS scans and point measurement scans, respectively]</p> <ul> <li>wind: Strength of crosswind, same as POS1_POS2 in <em>POS1_POS2_scans. </em>The sign corresponds to the wind direction. Negative is a crosswind from the port side of the aircraft, positive is a crosswind from the starboard side of the aircraft.</li> <li>Conv RV: 1 indicates the RV method has been evaluated for LLS scans, 0 if not.</li> <li>Naive RV: 1 indicates the RV method has been evaluated for point measurement scans, 0 if not.</li> <li>conv rv G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex computed using the RV method on LLS scans [m^2/s].</li> <li>conv rv G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex computed using the RV method on LLS scans [m^2/s].</li> <li>conv rv uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar using the RV method on LLS scans.</li> <li>conv rv dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar using the RV method on LLS scans.</li> <li>conv rv uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on LLS scans.</li> <li>conv rv dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on LLS scans.</li> <li>naive rv G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex computed using the RV method on point measurement scans [m^2/s].</li> <li>naive rv G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex computed using the RV method on point measurement scans [m^2/s].</li> <li>naive rv uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar using the RV method on point measurement scans.</li> <li>naive rv dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar using the RV method on point measurement scans.</li> <li>naive rv uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on point measurement scans.</li> <li>naive rv dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on point measurement scans.</li> <li>uw phi [deg]: Elevation angle to the center of the upwind (port) vortex from the simulation truth.</li> <li>uw range [m]: Range from the lidar to the center of the upwind (port) vortex from the simulation truth.</li> <li>dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex from the simulation truth.</li> <li>dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex from the simulation truth.</li> <li>conv rv uw phi [deg]: Elevation angle to the center of the upwind (port) vortex using the RV method on LLS scans.</li> <li>conv rv uw range [m]: Range from the lidar to the center of the upwind (port) vortex using the RV method on LLS scans.</li> <li>conv rv dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex using the RV method on LLS scans.</li> <li>conv rv dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex using the RV method on LLS scans.</li> <li>naive rv uw phi [deg]: Elevation angle to the center of the upwind (port) vortex using the RV method on point measurement scans.</li> <li>naive rv uw range [m]: Range from the lidar to the center of the upwind (port) vortex using the RV method on point measurement scans.</li> <li>naive rv dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex using the RV method on point measurement scans.</li> <li>naive rv dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex using the RV method on point measurement scans.</li> <li>y err conv uw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>y err conv dw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>z err conv uw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>z err conv dw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>y err naive uw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>y err naive dw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>z err naive uw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>z err naive dw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>D err conv uw [m]: Euclidean distance error for the Cartesian coordinates to the vortex center between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>D err conv dw [m]: Euclidean distance for the Cartesian coordinates to the vortex center between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>D err naive uw [m]: Euclidean distance error for the Cartesian coordinates to the vortex center between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>D err naive dw [m]: Euclidean distance for the Cartesian coordinates to the vortex center between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>plus_minus_phi: Indicates whether a RHI lidar scan features a positive lidar scanning rate (plus), or a negative one (negative).</li> <li>conv err G_515_uw: Circulation error (RV minus ST) between simulation truth and RV method of upwind (port) on LLS scans [m^2/s]. </li> <li>conv err G_515_dw: Circulation error (RV minus ST) between simulation truth and RV method of downwind (starboard) on LLS scans [m^2/s]. </li> <li>naive err G_515_uw: Circulation error (RV minus ST) between simulation truth and RV method of upwind (port) on point measurement scans [m^2/s]. </li> <li>naive err G_515_dw: Circulation error (RV minus ST) between simulation truth and RV method of downwind (starboard) on point measurement scans [m^2/s]. </li> <li>conv err uw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [deg].</li> <li>conv err dw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans [deg].</li> <li>naive err uw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [deg].</li> <li>naive err dw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans [deg].</li> <li>conv err uw range: Range from lidar error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [m].</li> <li>conv err dw range: Range from lidar error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans [m].</li> <li>naive err uw range: Range from lidar error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on point measurement scans [m].</li> <li>naive err dw range: Range from lidar error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans [m].</li> </ul> <p><em>0_0_movement.csv</em> gives insight on the vertical movement on selected vortices in selected lidar scans of the 0_0 wind case. </p> <p>The following data columns exist within the file (note csv file with ; separator):</p> <ul> <li>Str_dw: Vertical movement of the downwind (starboard) vortex, 0 is neutral, -1 is downward, and 1 is upward.</li> <li>Prt_uw: Vertical movement of the upwind (port) vortex, 0 is neutral, -1 is downward, and 1 is upward.</li> <li>scan_code: Identfies associated lidar scan with POS3_POS4_POS5 as in <em>POS1_POS2_scans.</em></li> </ul> <p> </p> <p><strong>lid_plane_info = Additional guidance on the simulated lidars.</strong></p> <p>Each simulation case has a separate file due to minimal ground speed changes of the aircraft. </p> <p>The following data columns exist within each file:</p> <ul> <li>Index: Gives the lidar number corresponding to POS4 and LID.</li> <li>Plane Pos [x]: Gives the longitudinal position of the lidar with respect to the glide path of the aircraft in meters.</li> <li>time plane passed [s]: Gives the simulation time when the aircraft first passes the measurement plane (related to the previous column.</li> <li>height plane passed [m]: Aircraft altitude at the respective lidar positon.</li> <li>lateral position lidar from GP [m]: Lateral position of the lidar from the glide path of the aircraft.</li> </ul> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> </div> <h3>Additional Notes: </h3> <div> <ul> <li>Gamma 515 circulation [4]: The Gamma 515 circulation is the averaged circulation of a vortex evaluated at radii 5-15m from the vortex center. </li> </ul> </div> <div> <div> <ul> <li>Lidar scans may contain 2 or 1 vortex. In the case of 1 vortex, the other has G_515_?? set to nan. Note that the position may still available in the labels data sets, but only vortices with available G_515_?? values should be used.</li> <li>The upwind and downwind definitions should purely be taken as names, rather than physical meaning. The names are derived from the simulation, due to mirroring and other post-processing these can be misleading however.</li> </ul> </div> </div> <div><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></div> <div> <p><strong>Funding</strong>: This dataset was generated within the mFUND <a href="https://bmdv.bund.de/SharedDocs/DE/Artikel/DG/mfund-projekte/kiwi.html">KIWI project</a> funded by the Federal Ministry for Digital and Transportation Germany and the DLR undertaking "Wetter und Disruptive Ereignisse".</p> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <p><strong>Acknowledgements:</strong></p> <p>The necessary RANS simulations were performed as part of the EU-funded AWIATOR by DLR's Institute of Aerodynamics and Flow Technology.</p> <p>We acknowledge Airbus for the allowance to use the RANS data.</p> <p>The LES was performed with the incompressible Navier-Stokes code MGLET [5] and kindly provided by the Technical University of Munich, Hydromechanics.</p> <p>The wake vortex simulations were computed on the high performance computer SuperMUC-NG by Leibniz-Rechenzentrum (LRZ).</p> </div> <div><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></div> <div> </div> <div><strong>References</strong>: </div> <div> </div> <div>[1] Robey, Rachel, and Julie K. Lundquist. "Behavior and mechanisms of Doppler wind lidar error in varying stability regimes." <em>Atmospheric Measurement Techniques</em> 15.15 (2022): 4585-4622.</div> <div> </div> <div>[2] Stephan, Anton, Norman Wildmann, and Igor Smalikho. "Effectiveness of the MFAS Method for Determining the Wind Velocity Vector from Windcube 200s Lidar Measurements." <em>Atmospheric and Oceanic Optics</em> 32.5 (2019): 555-563.</div> <div> </div> <div>[3] Smalikho, Igor., et al. "Method of radial velocities for the estimation of aircraft wake vortex parameters from data measured by coherent Doppler lidar." <em>Optics Express</em> 23.19 (2015): A1194-A1207.</div> <div> </div> <div>[4] Gerz, Thomas, Frank Holzäpfel, and Denis Darracq. "Commercial aircraft wake vortices." <em>Progress in Aerospace Sciences</em> 38.3 (2002): 181-208. </div> <div> </div> <div>[5] Manhart, Michael. "A zonal grid algorithm for DNS of turbulent boundary layers." <em>Computers & fluids</em> 33.3 (2004): 435-461.</div>
Lagrangian statistics in turbulent channel flow
<p>A set of Lagrangian statistics of passive tracers in a turbulent channel flow. The particle trajectories are obtained by means of integration of a simulated flow field, computed via Direct Numerical Simulation, at four different Reynolds numbers. The Reynolds numbers here employed are <span class="math-tex">\(\mathrm{Re}_{\tau} = \frac{u_{\tau}\delta}{\nu} = 180,\,395,\,590,\,950\)</span>, where <span class="math-tex">\(u_{\tau}\)</span>is the frictional velocity, <span class="math-tex">\(\delta\)</span> is the channel half height and <span class="math-tex">\(\nu\)</span> is the kinematic viscosity.</p> <p>Additional information about the database is provided in the included documentation.</p> <p>v1.0 -> Added statistics at ReT = 950</p> <p>v1.1 -> Added statistics at ReT = [180, 395, 590]</p> <p>v1.2 -> Added statistics at ReT = 265</p>
Data for "Schlieren and BOS velocimetry of a round turbulent helium jet in air"
<p>This is a subset of data used in our publication <a href="https://arxiv.org/abs/2202.04122">Schlieren and BOS velocimetry of a round turbulent helium jet in air</a> </p> <p> </p> <p>In the four helium-jet schlieren-image datasets given below, the nozzle diameter is 1.4 mm, the camera frame rate is 6000 fps and the individual image exposure is 0.0001667 s. 3000 images are provided for each dataset, or 1/2 s in real-time, which we determined to provide statistically-adequate data. Please see the <a href="https://arxiv.org/abs/2202.04122">paper</a> for more detail.</p> <p><strong>20210125-Run1</strong>: traditional mirror-schlieren, $Re_d = 5,890$, $U_j = 436$ m/s, and the scale is 0.29 mm/pixel.</p> <p><strong>20210206-Run1</strong>: traditional mirror-schlieren, $Re_d = 11,300$, $U_j = 682$ m/s, and the scale is 0.29 mm/pixel.</p> <p><strong>20210419-Run1</strong>: background-oriented schlieren (BOS), $Re_d = 5,890$, $U_j = 436$ m/s, and the scale is 0.26 mm/pixel. These are raw BOS images that must be processed with a reference image in order to yield pseudo-schlieren results. The reference (flow-off, tare) image is the first image in the sequence and is so named.</p> <p><strong>20210420-Run1</strong>: background-oriented schlieren (BOS), $Re_d = 11,300$, $U_j = 682$ m/s, and the scale is 0.26 mm/pixel. These are raw BOS images that must be processed with a reference image in order to yield pseudo-schlieren results. The reference (flow-off, tare) image is the first image in the sequence and is so named.</p>
Time seqUential theRmal inFrared - Turbulence campaign 1 - TURF-T1 Experiment data
<p>This dataset is a thermal infrared dataset collected alongside with sonic anemometer and thermocouple data. The experiment took place on the 12/01/2019 starting at 16:21:11 NZDT and ending at 16:31:11 NZDT. The collection of the infrared data was done via uncrewed aerial vehicle with an Optris PI 450 camera flying above a TURF Sportsground located at N -43.29186830137823, E 172.6008992376682.</p>
Assessing tropospheric turbulence impact on VGOS telescope placement in the Indian subcontinent for the estimation of Earth Orientation Parameters
<p>The dataset accompanying this study is composed of three distinct files, each integral to the research conducted. The file, named 'Simulated Data', includes the results derived from the simulations performed within this investigation. This file serves as a repository of the computed outcomes. The file, named 'Data and Code', includes the MATLAB scripts utilized to compute the Cn value from the Zenith Wet Delay (ZWD). Additionally, this file encompasses the relevant datasets for both wind speed and ZWD at various station locations. The third file contains the geographical coordinates of the Indian stations that were used in the study. Together, these files constitute a complete dataset that supports the study’s objectives and verification of the findings. </p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.