A benchmark dataset for steady-state flow models in fibrous microstructures

Open data API in a single place

Provided by Zenodo

Get early access to A benchmark dataset for steady-state flow models in fibrous microstructures API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.11.12 00:00
Created
2025.01.01
Available languages
English
Keywords
Resin Transfer Molding, FRPC, Composites, Permeability, Microstructure, Machine Learning
Quality scoring

Dataset description

This dataset includes steady-state flow simulations for 5250 (periodic) 2D fibrous microstructures that are representative of those encountered in the manufacturing processes (e.g., resin transfer molding) of fiber-reinforced polymer composite (FRPC). The microstructures have varying  size: [50, 75, 100, ..., 200] µm  fiber diameter: [7, 10, 15] µm  fiber volume fraction: [20, 30, 40, 50, 60] %  and were generated through an in-house Python package [1]. Each microstructure was subjected to two distinct flow cases: one in the horizontal and one in the vertical direction, yielding 10500 total simulations. The inlet/outlet were respectively placed at the left/right and bottom/top. The simulations were velocity-driven, with inlet velocity equal to 10⁻⁴ m/s, and outlet pressure equal to 0 Pa. The fluid flowing between the fibers was assumed to be epoxy resin having a density ρ=1250 kg/m³ and dynamic viscosity µ=0.5 Pa·s. All simulations were carried out through the same Python package [1] running OpenFOAM [2] in the background. The raw OpenFOAM files are accessible through simulations.zip, with the following folder structure:  simulations/ |-- domain_{SIZE1}_vf_{VF1}_diameter_{DIAM1}/ |   |-- domain_{SIZE1}_vf_{VF1}_diameter_{DIAM1}_seed_{SEED1}/  |       |-- geometry.json  |       |-- x_flow/  |       |-- y_flow/ |   |-- ...  |   |-- domain_{SIZE1}_vf_{VF1}_diameter_{DIAM1}_seed_{SEEDn}/ |-- ...  |-- domain_{SIZEn}_vf_{VFn}_diameter_{DIAMn}/    The simulation results were then post-processed by a custom Python script to convert the microstructures, velocity, and pressure fields into corresponding image (PyTorch) tensors suitable for training convolutional neural networks. The post-processed data can be found in dataset.zip, with the following folder structure:  dataset/  |-- metadata.json  |-- x/  |   |-- domain.pt  |   |-- dxyz.pt  |   |-- U.pt  |   |-- p.pt  |   |-- permeability.pt  |-- y/  |   |-- domain.pt  |   |-- dxyz.pt  |   |-- U.pt  |   |-- p.pt  |   |-- permeability.pt  The tensors have a shape of (n, C, 256, 256), where n is the number of microstructures. C is the number of channels: C=1 for the microstructure (domain.pt) and pressure (p.pt) tensors, C=2 for the velocity (U.pt) tensor, the two channels corresponding respectively to the x-component and y-component of the velocity field. The physical dimensions and permeability of the microstructures are additionally saved in dyxz.pt and permeability.pt.    References  [1] Broggi, G., Bessa, M., & Caglar, B. (2024, July 4). A realistic Python 2D microstructural generator: towards an open-source, bottom-up, and multiscale machine learning-based simulation pipeline for composite materials. Zenodo. https://doi.org/10.5281/zenodo.12771720  [2] Weller, H. G., Tabor, G., Jasak, H., & Fureby, C. (1998). A tensorial approach to computational continuum mechanics using object-oriented techniques. Computers in physics, 12(6), 620-631. 
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks