neqsim-e300-fluid-io

Read, write, and add water to Eclipse E300 compositional EOS fluid files for NeqSim.

4|2|Updated May 31, 2026
One-click install
npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-e300-fluid-io-equinor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neqsim-e300-fluid-io
Source: https://github.com/equinor/neqsim-community-skills/tree/main/skills/pvt/e300-fluid-io
Command: npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-e300-fluid-io-equinor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving compositional fluid definitions between Eclipse 300 (E300) EOS files and NeqSim simulations is error-prone, and adding water with the correct PVTsim parameters by hand risks inconsistent volume shifts, parachors, and binary interaction parameters. ## Core Features & Use Cases - Pure-Python E300 parser and writer: Parse, inspect, edit, and serialize E300 keyword files (CNAMES, TCRIT, PCRIT, BIC, ZI, and more) without requiring NeqSim or Java. - PVTsim-consistent water addition: Append water as the last component with the public PVTsim calibration (volume shift 0.084004, parachor 10.0, kij 0.5), reproducing a PVTsim *_water.e300 file. - NeqSim bridge: Wrap EclipseFluidReadWrite to load E300 files into rigorous NeqSim fluids, add water, and export fluids back to E300 text or files. - Use Case: Given a dry gas osebergfluid.e300, generate a water-bearing copy for PVTsim, then load it into NeqSim with setMixingRule("classic") for phase equilibrium calculations. ## Quick Start Ask the agent to read your E300 file, add water with the PVTsim parameters, and write a new water-containing E300 file using the e300_fluid_io package.

Frequently Asked Questions about neqsim-e300-fluid-io

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add water to an Eclipse E300 fluid file?▼

Call add_water_to_e300_file(input_path, output_path) from the e300_fluid_io package. It appends H2O as the last component with the public PVTsim water parameters (volume shift 0.084004, parachor 10.0, kij 0.5) and writes a new E300 file.

How do I read an E300 file into a NeqSim fluid in Python?▼

Use read_e300_to_neqsim(path) from the neqsim bridge, which wraps NeqSim's EclipseFluidReadWrite.read. It requires the optional neqsim Python package; afterwards call fluid.setMixingRule("classic") only if you did not rely on the file's BIC block.

Does the E300 parser work without NeqSim installed?▼

Yes. The pure-Python layer (parse_e300, read_e300_file, add_water, write_e300_file) has no dependencies and runs without NeqSim or Java. Only the bridge functions require the optional neqsim package and raise a clear RuntimeError when it is missing.

Why do NeqSim properties return zero after reading an E300 file?▼

The mixing rule was not set on the fluid. Call fluid.setMixingRule("classic") before property calculations, but note that EclipseFluidReadWrite.read already installs the mixing rule and file BIC values, so calling it again can discard tuned kij values.

What are the limitations of this E300 writer?▼

The pure-Python writer emits one value per line, so output is valid E300 but not byte-identical to a PVTsim Nova export. The skill does not characterize plus fractions, regress binary interaction parameters, tune the EOS, or validate laboratory data.