Sargent
Sargent is an integrated process systems engineering platform. One desktop application covers the whole design loop of a chemical process: flowsheet simulation, heat integration, optimization, techno-economic and life cycle assessment, AI prediction of reactions and properties, and links to commercial simulators and to a physical plant.
Version 0.1 is the first public build. It contains the simulator, the optimizers, the simulator links and the AI assistant. Heat exchanger network synthesis, TEA / LCA and the AI prediction models are not included in this build; their buttons are shown but disabled. They will be enabled in a later release.
Integrated features
| Feature | What it does | 0.1 |
|---|---|---|
| Flowsheet simulation | Sequential-modular solver with automatic or user-chosen tear streams (Wegstein, Broyden, direct substitution) and compiled property kernels | Included |
| Proxy run | Solve the same flowsheet with Aspen Plus or DWSIM installed on your computer and bring the results and errors back; import and export Aspen Plus and DWSIM files | Included |
| Equation-oriented optimization | Pyomo model of the converged flowsheet, solved with IPOPT | Included |
| Derivative-free optimization | NSGA-II (multi-objective) or Bayesian optimization; cases run in parallel on local workers or a Ray cluster; Pareto and parallel-coordinate plots | Included |
| Online connection | TCP/IP connection to a reconfigurable plant (self-driving lab): module map, interlocks, wiring export. Links to PubChem, NIST Chemistry WebBook, Reaxys, SciFinder, Open Reaction Database and ASKCOS | Included (plant control in development) |
| Agentic AI | In-app AI assistant that reads and edits the model, runs simulations and studies (OpenAI, Anthropic or a local OpenAI-compatible server, with your own API key), and an MCP server for external AI agents | Included |
| Heat exchanger network synthesis (HENS) | Heat exchanger network of the solved flowsheet: matches, heat recovered, total annual cost | Not included |
| Techno-economic analysis (TEA) | CAPEX, OPEX, NPV and minimum selling price of the target product; tornado sensitivity | Not included |
| Life cycle assessment (LCA) | Cradle-to-gate and cradle-to-grave impacts per kg of product; uncertainty from the choice of LCI datasets | Not included |
| Reaction prediction | Forward prediction, retrosynthesis and reaction-network generation with trained graph neural networks | Not included |
| Property prediction | Pure-component parameters from the molecular structure: Joback (included) and graph neural networks (not included) | Joback only |
Simulator
- Property methods: IDEAL, NRTL, WILSON, UNIQUAC, Peng-Robinson, Redlich-Kwong-Soave, Henry components, and electrolyte NRTL with an electrolyte wizard
- Unit operations: MIXER, FSPLIT, SEP, HEATER, HEATX, FLASH2, RADFRAC, FILTER, PUMP, COMPR, VALVE, RSTOIC, REQUIL, RCSTR, RPLUG and a Calculator block
- Property analysis: pure-component curves, Txy / Pxy, ternary residue-curve maps, azeotrope search, phase envelopes
Installation
Python 3.12 to 3.15, Windows (64-bit). Linux builds will follow in a later release. Package: pypi.org/project/sargent.
pip install "sargent[gui]"
sargent
Aspen Plus, DWSIM, optimization solvers (IPOPT and others) and life cycle inventory databases are not part of Sargent. Install and license them yourself to use the features that need them.
License
Sargent is proprietary software distributed as compiled packages only (see LICENSE).
- Free for academic research, teaching and personal non-commercial use.
- Commercial use requires a separate license. Contact: https://github.com/damdaepark
- Third-party components and their licenses: THIRD_PARTY_NOTICES.md.
Citation
A paper describing Sargent is in preparation. Until it is published, please cite:
Damdae Park, Sargent: an integrated process systems engineering platform, https://github.com/damdaepark/sargent
Name
Named in honor of Roger W. H. Sargent (1926-2018), founder of process systems engineering. Not affiliated with the Sargent Centre for Process Systems Engineering (Imperial College London / UCL).
Copyright (c) 2026 Damdae Park. All rights reserved.
1 maintainer
Metadata
1 maintainer
Release files for sargent 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| sargent-0.1-cp315-cp315-win_amd64.whl | CPython 3.15 | CPython 3.15 | Windows x86-64 | Details |
| sargent-0.1-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details |
| sargent-0.1-cp313-cp313-win_amd64.whl | CPython 3.13 | CPython 3.13 | Windows x86-64 | Details |
| sargent-0.1-cp312-cp312-win_amd64.whl | CPython 3.12 | CPython 3.12 | Windows x86-64 | Details |
Total release size: 31.7 MB
Release files / sargent-0.1-cp315-cp315-win_amd64.whl
| Download URL | sargent-0.1-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4e58f100a1437a3eddb838e3fb5a7aa3d9e634300285858eb642d17d166f37ae
|
|
BLAKE2b-256 checksum How to use checksums |
710b74e7c3a9cfaf5cb5255257ae6273565d356f3a0bee426aa730e681f786c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / sargent-0.1-cp314-cp314-win_amd64.whl
| Download URL | sargent-0.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 7.9 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
06bccd114a20f88d72c4fe1428b4e3005477fee66e9fd266011549495ad9a3d2
|
|
BLAKE2b-256 checksum How to use checksums |
c770cf3ddd7ba0d0bc035adea2da799b474a86443e519e62f635feccd4fbb1f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / sargent-0.1-cp313-cp313-win_amd64.whl
| Download URL | sargent-0.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 7.9 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ef761feb900c0202afc574461008ea0fd6e6984b093b7ca704e88d4050ec2e98
|
|
BLAKE2b-256 checksum How to use checksums |
af7173862caf2f3d51d0c4760341956e4cfbb02f3e79b586a413efb6c7fd3ec2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / sargent-0.1-cp312-cp312-win_amd64.whl
| Download URL | sargent-0.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 7.9 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fc39754b6628d54dd5746598a408e53500090ed4827e909db63a2a7b12c00343
|
|
BLAKE2b-256 checksum How to use checksums |
c85671af18c7ddcc70e010fb9ac2b783288d3c81ecc3144662e1e0b4ec8aee6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log
