Skip to the content.

NeqSim 3.27.0

Status: prepared release candidate; publication pending. Prepared on 2026-10-31 from master 3c1c5dda4a58cbab78330612889e377b57f7793c, covering 232 commits after v3.26.0. Only changes merged into that snapshot are included. The version-preparation PR does not publish artifacts or create a tag.

Complete change list for this snapshot.

Review before upgrading

Numerical changes and model qualification

Rebaseline saved engineering cases against their measured data and balance checks. Results can change for wet-gas and trace-water flashes, CPA caloric properties, Huron–Vidal derivatives, compressor chart calculations, transport properties, reservoir depletion and two-fluid transient energy balances. Passing software tests does not qualify every fluid or operating range.

Saved models and public contracts

#4630 repairs loading of older .neqsim files, and thermodynamic deserialization reconciles inconsistent total-mole inventories. Validate representative prior-release files, equipment state, units, component inventories and rerun results before migrating an application. Same-version serialization round trips do not establish compatibility with every older object graph. A complete API and cross-version persistence assessment remains a release gate; this candidate does not claim universal backward compatibility.

When upgrading from before 3.26.0, also follow the 3.26.0 migration notes, particularly the JAMA-to-EJML interfaces, saved numerical-solver state and corrected E300 critical-volume units. Those changes already shipped in 3.26.0. Any newly identified breaking contract must follow governance and the API lifecycle policy, including the required NRC and major contract review; preparing the requested number does not waive those gates.

Runtime and packaging

The standard core artifact requires Java 17+, the separate Java 8 artifact requires Java 8+, and the MCP runner requires Java 21+. Java source in the repository remains Java 8 compatible. The Python development/report toolkit now requires Python 3.11+, following the Pillow security update; that requirement is separate from the core Java artifacts (#4542, #4713).

Main changes since 3.26.0

Thermodynamics, physical properties and PVT

Reservoir history and well-to-host systems

Process equipment, control and optimization

Transient pipelines and safety: retain experimental limits

Two-fluid updates conserve phase-appearance sources, boundary/component energy, node thermodynamics and mechanical pressure at closed walls, with improved thermal recovery and stiff friction treatment (#4608, #4611, #4673, #4679, #4689, #4732, #4758). Review the canonical two-fluid evidence matrix. These individual repairs do not establish full rich-gas blowdown, terrain pooling and repressurization/evaporation qualification.

The experimental Safety Shutdown acoustic path adds exact valve-travel timing, conservative cell inventory, bounded forward pump curves and lift-check boundaries (#4708, #4714, #4720, #4724, #4734, #4746). Respect its documented fluid, wave-speed, pump-flow and boundary assumptions. This is not a general multiphase hydraulic-hammer or safety-system certification.

Live release-inventory studies now gate outlet withdrawal using current phase geometry (#4690); see the coupled inventory guide.

Structure-H hydrate data: preliminary qualification only

#4754 adds 24 digitized published experimental markers, provenance, reproducible system-correlation fits and checks. These coefficients describe complete methane/water/promoter systems; they are not component Langmuir/Kihara parameters, do not update COMP with qualified sH parameters, and do not enable structure H in hydrate flashes. Executable hydrate models still support sI and sII. See the structure-H qualification record.

Engineering reports, agents and development tools

Add process, PVT, flow-assurance, SURF, utilities and onshore/offshore layout study/report workflows, with executable documentation, equipment tables, drawings, capability discovery and PFD layout review (#4503, #4578, #4592, #4604, #4612, #4613, #4749, #4757). Plugin-only installs gain required report modules and explicit engine-version checks (#4643). Engineering-coverage CI retains validation while avoiding writes to protected master (#4763).

Planned distributions

Distribution Version or expected asset Runtime
Core Maven artifact com.equinor.neqsim:neqsim:3.27.0 Java 17+
Core standalone library neqsim-3.27.0.jar Java 17+
Java 8 Maven artifact com.equinor.neqsim:neqsim:3.27.0-Java8 Java 8+
Java 8 standalone library neqsim-3.27.0-Java8.jar Java 8+
MCP runner and checksum neqsim-mcp-server-3.27.0-runner.jar and .jar.sha256 Java 21+
MCP container ghcr.io/equinor/neqsim-mcp-server:3.27.0 Container runtime

The MCP module’s own Maven identity remains 1.0.0-SNAPSHOT; its core revision/neqsim.version resolve to 3.27.0. The runner filename and container tag use the core release version. The Python package and agent-plugin marketplace have separate publication processes.

The preparation restores Maven 3.9.16, the publishing baseline used by 3.25.0 and 3.26.0. Dependency update #4615 had reintroduced 3.10.0 while the Java 8 release profile still uses central-publishing 0.11.0. #4318 documents the unwanted local metadata in that combination’s publication bundle. Keep the standard profile at 0.12.0 and both profiles at waitUntil=published; qualify both bundles before advancing the wrapper. This preparation changes no library dependency or simulation source.

Release completion requirements

  1. Review these notes against the final candidate and confirm API and saved-model compatibility, migration instructions and any required contract decisions.
  2. Require configured CI and security gates on the final candidate: full core tests on supported configurations, slow-test shards, model specifications, formatting, documentation/Javadoc, coverage and packaged MCP protocol tests. Parent-commit results do not establish final-candidate success.
  3. Build and inspect the Java 17/Java 8 libraries, sources/Javadoc, and Java 21 MCP runner. Verify embedded versions, class-file targets, Java 8 dependency pins and runtime behavior, and MCP checksums. Local POM validation alone is not package or protocol qualification.
  4. Merge the reviewed version PR. The default-branch workflow can build assets and create a draft release. Include these notes and the generated change list in the release body. Preparation alone does not authorize publication.
  5. After release-owner approval, publish and verify both Maven Central versions reach PUBLISHED, GitHub assets/checksums are downloadable, and the MCP container is available. Record the final tag, commit and workflow evidence.

Local and hosted validation evidence is recorded in the preparation PR. These notes describe candidate changes and required gates; the expected artifacts above are not asserted to be published or available.