neqsim-e300-fluid-io

E300 Fluid I/O

Use this skill to move fluids between Eclipse 300 (E300) compositional EOS files and NeqSim, and to add water to a fluid or E300 file using the public PVTsim water parameterization.

The skill has two layers:

• A pure-Python layer that parses, edits, and writes the E300 keyword format without requiring NeqSim. It is used to inspect files, add water, and produce E300 files that NeqSim can read back.
• A NeqSim bridge that wraps neqsim.thermo.util.readwrite.EclipseFluidReadWrite to load E300 files into rigorous NeqSim SystemInterface fluids, add water, and write fluids back to E300.

When to Use

• When a task provides an E300 file and needs a NeqSim fluid for simulation.
• When a NeqSim fluid must be exported to an E300 file for PVTsim or Eclipse.
• When water must be added to a dry fluid using the public PVTsim water parameters (reproducing a PVTsim *_water.e300 file).
• When an existing E300 file must be copied with water appended as the last component with a binary interaction parameter of 0.5 against all components.
• When a task must document or verify the E300 keyword layout.

Inputs

• e300_path: path to an Eclipse E300 file.
• add_water: whether to append a water component (H2O).
• water_kij: water binary interaction parameter (PVTsim default 0.5).
• reservoir_temp_c: reservoir temperature written to the RTEMP keyword.
• neqsim_fluid: a NeqSim SystemInterface fluid (for export).

Outputs

• neqsim_fluid: a NeqSim fluid created from an E300 file.
• e300_file: a written E300 file (with or without water).
• e300_string: E300 keyword text for a NeqSim fluid.
• E300Fluid: a pure-Python object with component names, EOS parameters, the binary interaction matrix, and the overall composition.

Engineering Method

E300 file format

An E300 file is a keyword text file. Each keyword introduces a value block that is terminated by a /. Lines starting with -- are comments. The keywords this skill reads and writes are: