Correlations for aerodynamic force coefficients of non-spherical particles in compressible flows
Bibliographic record
Abstract
# Data repository for the paper # _Correlations for aerodynamic force coefficients of non-spherical particles in compressible flows_ Corresponding author: Berend.van.Wachem@multiflow.org This repository consists of the data and exemplary python scripts for the paper "Correlations for aerodynamic force coefficients of non-spherical particles in compressible flows" by Christian Gorges, Victor Chéron, Anjali Chopra, Fabian Denner and Berend van Wachem. The data stored in this repository have the following data format: - .csv files consisting the raw data of the simulations used for the coefficient plots in the results' chapter of the paper - .py files containing python scripts serving as examples on how to use and plot the raw data of the .csv files and the correlations The main folders of this repository are named as the non-spherical particle shapes (Oblate, Prolate, Rod-like) and a folder with the data on which the correlations are based. The folders named after the non-spherical particle shapes contain the raw simulation data. For instance, the Oblate folder contains the individual .csv files of all simulations of the oblate spheroid for all Reynolds numbers, Mach numbers, and angles of attack. The folder Correlations/ consists of the temporally averaged drag, lift and torque coefficients, which are written in .csv files and stored in the folder ResultsCoefficients/, as well as Python scripts for plotting the correlations. The naming style of the raw data files and the subfolders for each section is explained in the following: The file names of the .csv files within the particle shape folders consist of the Reynolds number, followed by the Mach number and the angle of attack. For example "log_Re100M2_0_alpha_90.csv" consists of the data for a Reynolds number of 100, a Mach number of 2.0 and an angle of attack of 90 degrees. The content in the .csv files is given as: "%f,%f,%f,%f\n" which corresponds to "Physical time, drag coefficient, lift coefficient, torque coefficient". The first row in each file gives the headers of each column. The .csv files in the folder Correlations/ResultsCoefficients/ are split per coefficient, shape, and particle Reynolds numbers, which can be identified by the name of the .csv file. For instance, the results obtained for the lift coefficient of the prolate spheroid particle for at a particle Reynolds numbers 100 for all orientation angles and Mach numbers are given in the file: "Prolate_100_CL.csv". In these files, the results are ordered per orientation angle (rows) and Mach number (column). The python scripts have been tested with Python 3.11.5. PlotCoefficients.py is an example python script to read the .csv files and plot the aerodynamic force coefficients as it is done in the results section of the paper. The python scripts in the directory Correlations/ are split in three main functions in two files: - Getter.py (read the .csv files storing the coefficients - separate functions for the drag, lift and torque coefficients) - ManuscriptCorrelation.py with all the correlations derived in this work for an effective implementation in any solver, and a plotting function to have visual representation of the correlations. - generalmain.py (calls Getter and Plotter) The Getter is called from the generalmain.py file. (run python3 generalmain.py) so that all coefficients can be gathered in a 3D array. First dimension : Reynolds number Second dimension : Orientation angle Third dimension : Mach number The user just needs to give the absolute path to the folder ResultsCoefficients/. This project has received funding from the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation), grant number 447633787.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.020 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.005 | 0.004 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.002 | 0.003 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.059 | 0.036 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".