You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I’m working with a cubic unit cell containing 8 pores (nodes) and 28 cylindrical throats (edges), each defined by a pore radius and throat radius.
I’ve noticed that multiple throats can geometrically overlap (especially near corners or diagonals), which leads to an overestimation of porosity when I compute the total pore + throat volume directly.
Is there a function or recommended approach in this library to:
detect and handle throat–throat (or multi-throat) overlaps based on input throat-dia and network, or
subtract shared volumes between intersecting throats?
This discussion was converted from issue #3003 on November 12, 2025 16:03.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I’m working with a cubic unit cell containing 8 pores (nodes) and 28 cylindrical throats (edges), each defined by a pore radius and throat radius.
I’ve noticed that multiple throats can geometrically overlap (especially near corners or diagonals), which leads to an overestimation of porosity when I compute the total pore + throat volume directly.
Is there a function or recommended approach in this library to:
detect and handle throat–throat (or multi-throat) overlaps based on input throat-dia and network, or
subtract shared volumes between intersecting throats?
Thanks for the help.
Beta Was this translation helpful? Give feedback.
All reactions