GEOS-DEV / GEOS-DEV/GEOS

Permeability models for PorousSolid

Open
#3,918 0 comments 0 reactions 1 assignee View on GitHub

@jhuang2601 is already working on this.

Since May 15, 2026.

  • #3824 by @jhuang2601 — open
type: bug
Dominant language
C++
Stars
287
Forks
109
Avg merge
4d 41m
Merged PRs (30d)
5

Description

Hello,
My name is Ibrahima Djiba, a research engineer currently working with Olga Dufour’s team (https://github.com/ol-n-ga).
I am writing to you regarding the implementation of the Kozeny-Carman model for permeability calculation in GEOS.
I have tested the following examples:

staircase_3d.xml (CompressibleSolid)
PoroElastic_CarmanKozenyPermeability_base.xml and PoroElastic_CarmanKozenyPermeability_fim_smoke.xml (PorousSolid)

Then, I visualized both models in ParaView. For the first example, permeability is correctly computed and displayed. However, for the second example, no permeability variation is observed.
I compared the source files CompressibleSolid.cpp and CompressibleSolid.hpp with PorousSolid.cpp and PorousSolid.hpp and their dependencies. I noticed that the CompressibleSolid files (used in staircase_3d.xml) include routines that define variations in porosity and permeability, whereas the PorousSolid files only seem to handle porosity changes without updating permeability.
Additionally, I extracted porosity values from the VTK files and then calculated and plotted permeability values using the Kozeny-Carman model in Python. In this case, the permeability variation is clearly visible.
Could you please confirm whether the routines for updating permeability variations are indeed missing in the PorousSolid model?
Best regards,
Ibrahima Djiba

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.