Introduce NeqSim Studio alongside Classic - #93
Draft
EvenSol wants to merge 11 commits into
Draft
Conversation
This was referenced Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First tranche of the new NeqSim Web Studio Campaign, superseding the former Process Flowsheet Studio schedule without restarting its mature implementation.
pages/35_Process_Flowsheet_Studio.pythe first enabled Studio engineering workflowdocs/neqsim_web_studio_roadmap.mddefining the three-repository architecture and inherited Process Flowsheet Studio foundationProcess Flowsheet StudioGitHub Actions gate so Classic/Studio shell changes receive hosted compile, Streamlit AppTest, real HTTP/health, and inherited simulation-regression coverageEvenSol/neqsimweb2repositoryProduct boundary
Classic remains available. Existing users can continue using the current pages, calculations, saved cases and sidebar workflow. Studio is introduced side-by-side and is explicitly labelled Beta.
Studio does not create a second simulation engine:
equinor/neqsim: authoritative thermodynamics, process simulation, design, dynamics, optimization and PFD/P&ID/DEXPI semanticsEvenSol/neqsimweb2: Classic + Studio UI, orchestration and shared adaptersEvenSol/NeqSim-Colab: executable reference workflows and acceptance evidenceThe active NeqSim ISO PFD (#1332) and DEXPI/P&ID (#2899) campaigns remain authoritative for drawing semantics; this PR deliberately does not implement a competing diagram engine.
Inherited foundation
The new campaign inherits the merged Process Flowsheet Studio work: generic graph/schema execution, explicit named streams/ports, multiple feeds, mixers/splitters/phase outlets, workbooks, studies, equipment design, subflowsheets, persistence, Process Chat handoff, convergence/conservation evidence, timeout/fail-loud behavior and deployment hardening.
Validation
Exact head:
4e2db28de200a335ca1f9cd34d994c51236e512dLocal source validation:
PYTHONPATH=. python tests/test_studio_navigation.py -v— 4/4 passedHosted GitHub Actions Process Flowsheet Studio #384, run
31332379742, completed successfully on the exact head. All steps passed:AppTest/_stcore/healthreturnsokon repeated probes, and the process remains liveBranch/diff evidence:
mainRoadmap
Advances:
Next largest safe tranche after merge: establish the shared Studio case context/lifecycle, then integrate the mature Process Flowsheet Studio behind that context rather than rewriting it.
Documentation impact
Adds the persistent Studio roadmap/architecture ledger. Classic user documentation remains in place; only incorrect web-repository URLs are corrected.