agentleFS
equinorequinor/neqsim-community-skills/skills/flow-assurance/neqsim-two-phase-flow-regime-screening/SKILL.md

neqsim-two-phase-flow-regime-screening

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Educational two-phase flow-regime screening that classifies a horizontal gas-liquid flow pattern from superficial velocities using a simplified public Mandhane-style map and flags slug risk. USE WHEN: a task needs a public, screening-level flow-regime flag (stratified, slug, annular, bubble) and slug-risk triage to pair with slug-flow and flow-induced-vibration work.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a user asks what flow regime a horizontal line is likely in.

    line 20
  2. Distinctive:

    When an agent needs a quick slug-risk flag before slug or vibration work.

    line 21
  3. Distinctive:

    When examples must run without confidential pipeline models or field data.

    line 22
  4. Very specific:

    When the regime is transient rather than steady — terrain slugging, ramp-up surge, shut-in and restart — escalate instead to the …

    line 85
  5. Distinctive:

    No surface-tension, viscosity, or entrainment effects.

    line 107

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Two-Phase Flow Regime Screening

Use this skill for public, educational two-phase flow-regime screening. It classifies a horizontal gas-liquid flow pattern from the superficial gas and liquid velocities using a simplified Mandhane-style decision tree and flags slug risk so an agent can decide whether to invoke validated NeqSim multiphase pipe-flow modelling.

When to Use

  • When a user asks what flow regime a horizontal line is likely in.
  • When an agent needs a quick slug-risk flag before slug or vibration work.
  • When examples must run without confidential pipeline models or field data.

Inputs

Provide either the superficial velocities directly, or enough data to compute them:

  • superficial_gas_velocity: gas superficial velocity Vsg in m/s.
  • superficial_liquid_velocity: liquid superficial velocity Vsl in m/s.

or

  • pipe_inner_diameter: pipe inner diameter in m.
  • gas_mass_flow: gas mass flow in kg/s.
  • liquid_mass_flow: liquid mass flow in kg/s.
  • gas_density: gas density in kg/m3.
  • liquid_density: liquid density in kg/m3.

Outputs

  • superficial_gas_velocity_m_s: gas superficial velocity used.
  • superficial_liquid_velocity_m_s: liquid superficial velocity used.
  • mixture_velocity_m_s: Vsg + Vsl.
  • flow_regime: stratified-smooth, stratified-wavy, elongated-bubble, slug, dispersed-bubble, or annular-mist.
  • slug_risk: true when the regime is slug or elongated-bubble.
  • regime_warning: ok, slug-risk, or high-velocity.
  • assumptions: public assumptions used by the placeholder model.

Engineering Method

The Python class TwoPhaseRegimeModel uses a simplified public Mandhane-style classifier for horizontal flow:

  • superficial velocities use Vs = (mdot / rho) / (pi/4 * D^2) when computed from flows.
  • the regime is selected from public approximate boundaries: annular-mist above Vsg = 10 m/s, dispersed-bubble above Vsl = 2 m/s, stratified below Vsl = 0.1 m/s, elongated-bubble for low gas velocity, otherwise slug.
  • slug_risk is flagged for the slug and elongated-bubble regimes.

This is educational and screening-only logic. The boundaries are public approximations, not the digitized Mandhane chart or a mechanistic model. It ignores pipe inclination, surface tension, viscosity, entrainment, and transient slugging. It is not a replacement for validated multiphase flow modelling and qualified flow assurance review.

Python Usage Pattern

from two_phase_flow_regime_screening import TwoPhaseRegimeModel

model = TwoPhaseRegimeModel()
result = model.evaluate(
    superficial_gas_velocity=3.0,
    superficial_liquid_velocity=0.5,
)

print(result.flow_regime)
print(result.slug_risk)
print(result.regime_warning)

Related NeqSim Functionality

For validated multiphase flow behaviour, redirect to existing NeqSim classes:

  • neqsim.process.equipment.pipeline.PipeBeggsAndBrills — Beggs and Brills multiphase pressure drop and holdup with internal regime determination.
  • neqsim.process.equipment.pipeline.TwoFluidPipe — two-fluid transient pipe flow.
  • neqsim.process.equipment.pipeline.AdiabaticTwoPhasePipe — adiabatic two-phase line modelling.

This skill is a public flow-regime triage layer that decides when to invoke those validated pipe-flow classes.

When the regime is transient rather than steady — terrain slugging, ramp-up surge, shut-in and restart — escalate instead to the neqsim-olga-multiphase-simulator skill (or the olga-simulation-agent), which runs an OLGA transient case and reads its trend and profile results.

Validation Checklist

  • Either superficial velocities or full flow/density/diameter data are supplied.
  • Velocities are non-negative and finite.
  • The regime and slug-risk flag are reported as screening indicators.
  • Tests cover stratified, slug, annular, computed velocities, and invalid input.
  • Real regime analysis is redirected to validated NeqSim pipe-flow classes and qualified review.

Common Mistakes

SymptomCauseFix
Regime looks wrongUsed vertical or inclined lineThis map is for horizontal flow only
Velocities too highMass flow given in kg/h not kg/sUse kg/s, or pass velocities directly
Slug missedOperating near a public boundaryUse a mechanistic NeqSim model near boundaries

Limitations

  • Horizontal flow only; no inclination or terrain slugging.
  • Public approximate boundaries, not the digitized Mandhane chart.
  • No surface-tension, viscosity, or entrainment effects.

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.