Papers › Python workflow for segmenting multiphase flow in porous rocks
Python workflow for segmenting multiphase flow in porous rocks
Catherine Spurin, Sharon Ellman, Dane Sherburn, Tom Bultreys, Hamdi A. Tchelepi
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
X-ray micro-computed tomography (X-ray micro-CT) is widely employed to investigate flow phenomena in porous media, providing a powerful alternative to core-scale experiments for estimating traditional petrophysical properties such as porosity, single-phase permeability or fluid connectivity. However, the segmentation process, critical for deriving these properties from greyscale images, varies significantly between studies due to the absence of a standardized workflow or any ground truth data. This introduces challenges in comparing results across different studies, especially for properties sensitive to segmentation. To address this, we present a fully open-source, automated workflow for the segmentation of a Bentheimer sandstone filled with nitrogen and brine. The workflow incorporates a traditional image processing pipeline, including non-local means filtering, image registration, watershed segmentation of grains, and a combination of differential imaging and thresholding for segmentation of the fluid phases. Our workflow enhances reproducibility by enabling other research groups to easily replicate and validate findings, fostering consistency in petrophysical property estimation. Moreover, its modular structure facilitates integration into modeling frameworks, allowing for forward-backward communication and parameter sensitivity analyses. We apply the workflow to exploring the sensitivity of the non-wetting phase volume, surface area, and connectivity to image processing. This adaptable tool paves the way for future advancements in X-ray micro-CT analysis of porous media.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2410.18937")
Code
Syntology Ran 0 of 3 code samples harvested from 1 repository linked to this paper; 3 have no recorded run.
By repository: official repository: 3 samples from 1 repository, 0 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
3 samples harvested; 0 ran; 0 honoured the contract we drafted; 3 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.
Licence: 3 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from cspurin/image_processing. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
e49e8d27e1d125db · report
4d6926c81c636616 · report
2972faff8c7fcad2 · report
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections