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.