Data repository for the paper: A marching cubes based method for topology changes in three-dimensional two-phase flows with front tracking
Bibliographic record
Abstract
# Data repository for the paper # *A marching cubes based method for topology changes in three-dimensional two-phase flows with front tracking* ## Corresponding email: # berend.van.wachem@multiflow.org This repository contains the results' data for the paper "A marching cubes based method for topology changes in three-dimensional two-phase flows with front tracking" by Gabriele Gennari, Christian Gorges, Fabian Denner and Berend van Wachem.The data stored in this repository has the following format: - .txt files contain the raw data used for the plots in the validation section of the paper.- .zip files contain .pvtu and .vtu files of the front mesh for all the simulations (the results can be visualised with the open-source software Paraview or with similar tools).- .gnuplot files contain the gnuplot script to reproduce the plots from the raw data contained in the .txt files. The main folders of this repository are named as the paragraphs in the validation section of the paper. Within the main folders, sub-folders contain the raw data for the specific simulations. The naming style of the raw data files and the sub-folders is explained in the following. *4.2_Droplet_breakup_in_simple_shear_flow*:This main folder contains sub-folders for all the cases with a droplet in a simple shear flow from section 4.2. Run1, Run2 and Run3 are the three simulations reported in Table 3 (in the same order). *4.3_Droplet-droplet_collision*:This main folder contains sub-folders for all the droplet-droplet collision cases analysed in section 4.3. Run1, Run2 and Run3 are the three simulations reported in Table 5 (in the same order).The file output.txt contains the data for the plot of the Weber number reported in Figure 22, which can be reproduced with the gnuplot script Weber.gnuplot.The content in the .txt file is the following:"%f,%f\\n"which corresponds to"Time, Weber number". *4.4_Breakup_of_a_rising_bubble*:This main folder contains the two cases of a rising bubble analysed in section 4.4. The sub-folders Central and Peripheral correspond to central and peripheral breakup, respectively. *4.4.1_A_more_complex_scenario*:This folder contains the rising bubble case reported in section 4.4.1. # AcknowledgementsThis project has received funding from the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation), grant numbers 420239128 and 458610925.
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.003 | 0.017 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.003 | 0.005 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.008 | 0.004 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.282 | 0.175 |
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".