A dynamic, graph-driven Multidisciplinary Design Optimization (MDO) framework integrating FalkorDB, GEMSEO, and multi-fidelity surrogate models.
Project description
GraphMDO: Dynamic Multi-Fidelity MDO Framework
GraphMDO bridges data engineering and MDO. It extracts topological data (solvers, variables, fidelity levels) to form an oriented graph, specifically utilizing GEMSEO for semantic formulation and execution. Execution is handled natively by GEMSEO and the Surrogate Modeling Toolbox (SMT), with optimization workflows currently centered on constrained Bayesian optimization (ax-platform) and DOE exploration through GEMSEO. The framework supports single- and multi-objective optimization over graph-derived design variables with explicit inequality constraints.
Key Features
- Native Graph Formulation: Uses FalkorDB to store problem definitions (variables, tools, dependencies) as a property graph.
- Dynamic Problem Construction: Automatically translates the graph topology into an executable GEMSEO MDO formulation.
- Multi-Fidelity Surrogates: Integrates SMT for Co-Kriging and other surrogate models.
- Constrained Bayesian Optimization: Leverages Ax Platform for robust optimization, supporting GEMSEO objectives, inequality constraints, and mixed discrete/continuous parameters.
Project Architecture
The framework is divided into four sequential phases, each corresponding to a layer of abstraction:
- Graph Layer — FalkorDB stores the Fundamental Problem Graph (FPG): variables, tools, and directed connections.
- Core Layer — Python modules translate the graph schema into executable GEMSEO constructs (disciplines, design space, topology).
- Execution Service — A FastAPI microservice that manages a pool of GEMSEO
OptimizationProbleminstances and exposes an HTTP evaluation endpoint. - Optimization Layer — Bayesian (Ax Platform) or DOE (GEMSEO Sobol) drivers run over the GEMSEO MDO scenario.
flowchart TD
subgraph USER["👤 User"]
U1["Define Variables\n& Tools"]
U2["Provide Tool\nCallables / Registry"]
U3["Read Results"]
end
subgraph GRAPH["🗄️ Graph Layer — FalkorDB"]
G1["GraphManager\n(graph_manager.py)"]
G2[("FalkorDB\nProperty Graph\nFPG")]
G3["FalkorDB Client\n(client.py)"]
G1 -- "add_variable / add_tool\nconnect_input_to_tool" --> G2
G3 -- "Cypher queries" --> G2
G1 -- uses --> G3
end
subgraph CORE["⚙️ Core Layer — mdo_framework.core"]
C1["TopologicalAnalyzer\n(topology.py)\nresolve_dependencies()"]
C2["GraphProblemBuilder\n(translator.py)\nbuild_problem()"]
C3["GemseoComponent\n(components.py)\nGEMSEO Discipline wrapper"]
C4["SurrogateComponent\n(surrogates.py)\nSMT Co-Kriging"]
C5["LocalEvaluator\n(evaluators.py)"]
C2 --> C3
C2 --> C4
C3 --> C5
end
subgraph GEMSEO["📐 GEMSEO MDO Engine"]
GS1["DesignSpace"]
GS2["MDOScenario / DOEScenario"]
GS3["OptimizationProblem"]
GS2 --> GS3
GS1 --> GS2
end
subgraph OPT["🔬 Optimization Layer — mdo_framework.optimization"]
O1["BayesianOptimizer\n(optimizer.py)"]
O2["AxOptimizationLibrary\n(ax_algo_lib.py)\nCustom GEMSEO Algorithm"]
O3["Ax Client\n(ax-platform)"]
O4["DOE Explore\nSobol sampler"]
O1 --> O2
O1 --> O4
O2 --> O3
O3 -- "suggest_next_trials()" --> O2
O2 -- "complete_trial() / mark_failed()" --> O3
end
subgraph SVC["🌐 Execution Service — services.execution"]
S1["FastAPI App\n(main.py)"]
S2["SchemaProvider\n(schema cache + TTL)"]
S3["ProblemPool\n(GEMSEO problem pool)"]
S4["/evaluate endpoint"]
S5["/health endpoint"]
S1 --> S2
S1 --> S3
S1 --> S4
S1 --> S5
S4 --> S3
end
%% Cross-layer data flow
U1 --> G1
U2 --> C2
G2 -- "get_graph_schema()" --> C1
G2 -- "get_graph_schema()" --> C2
C1 -- "design parameters\n& bounds" --> O1
C5 --> GS3
GS1 --> O1
GS3 --> O2
O2 -- "evaluate_functions(x)" --> GS3
O3 -- "best_parameterization" --> O1
O1 --> U3
%% Remote path
O1 -. "RemoteEvaluator\n(HTTP /evaluate)" .-> S4
S3 -. "GEMSEO problem\ninstance" .-> S4
style USER fill:#1e293b,stroke:#64748b,color:#f1f5f9
style GRAPH fill:#0f172a,stroke:#3b82f6,color:#bfdbfe
style CORE fill:#0f172a,stroke:#8b5cf6,color:#ddd6fe
style GEMSEO fill:#0f172a,stroke:#06b6d4,color:#a5f3fc
style OPT fill:#0f172a,stroke:#f59e0b,color:#fef3c7
style SVC fill:#0f172a,stroke:#10b981,color:#a7f3d0
Installation
This project uses uv for dependency management.
-
Install uv (if not installed): See astral.sh/uv.
-
Clone and Install:
git clone https://github.com/jultou-raa/GraphMDO.git cd GraphMDO uv sync
-
FalkorDB: Ensure you have a running FalkorDB instance (e.g., via Docker):
docker run -p 6379:6379 -it falkordb/falkordb
Usage
1. Defining a Problem (Python API)
You can programmatically build your MDO problem graph:
from mdo_framework.db.graph_manager import GraphManager
gm = GraphManager()
gm.clear_graph()
# Define Variables
gm.add_variable("x", value=1.0, lower=0.0, upper=10.0)
gm.add_variable("y", value=2.0, lower=0.0, upper=10.0)
gm.add_variable("z", value=0.0)
# Define Tool
gm.add_tool("MyTool")
# Define Connections
gm.connect_input_to_tool("x", "MyTool")
gm.connect_input_to_tool("y", "MyTool")
gm.connect_tool_to_output("MyTool", "z")
2. Running Optimization
Once the graph is populated, you can run the optimization workflow. You need to provide the actual Python functions corresponding to the tool names in the graph.
from mdo_framework.core.translator import GraphProblemBuilder
from mdo_framework.optimization.optimizer import BayesianOptimizer
from mdo_framework.core.evaluators import LocalEvaluator
from mdo_framework.core.topology import TopologicalAnalyzer
# Define tool implementation
def my_tool_func(x, y):
return x + y # Simple example
# Registry maps graph tool names to Python callables
tool_registry = {
"MyTool": my_tool_func
}
# Build GEMSEO Problem from Graph
schema = gm.get_graph_schema()
builder = GraphProblemBuilder(schema)
prob = builder.build_problem(tool_registry)
# Resolve Topology mapping design_vars automatically from the graph schema
analyzer = TopologicalAnalyzer(schema)
design_vars, _ = analyzer.resolve_dependencies(["z"])
parameters = analyzer.extract_parameters(design_vars)
# Run Optimization
evaluator = LocalEvaluator(prob)
optimizer = BayesianOptimizer(
evaluator=evaluator,
parameters=parameters,
objectives=[{"name": "z", "minimize": True}],
)
result = optimizer.optimize(n_steps=10)
print(f"Best Result: {result['best_objectives']} at {result['best_parameters']}")
print(f"Trial History: {result['history']}")
3. Running Tests
uv run pytest tests/
Contributing
- Follow PEP 8 guidelines.
- Ensure 100% test coverage for new features.
- Use
uv run pre-commit run --all-filesbefore committing.
License
This project is licensed under the Mozilla Public License 2.0 (MPL-2.0). See the LICENSE file for details.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file graphmdo-1.0.0.tar.gz.
File metadata
- Download URL: graphmdo-1.0.0.tar.gz
- Upload date:
- Size: 215.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
07ea18bbeff670f7f94766022f2b937842ddf2792500714c18f22416ed8b82e4
|
|
| MD5 |
3e30b48c2bfe0117b9fe86044d7a1494
|
|
| BLAKE2b-256 |
2276fafc4ed19773e8db0b539fa2f90f0d95c0d800af99c3f92d56c05da7dccc
|
Provenance
The following attestation bundles were made for graphmdo-1.0.0.tar.gz:
Publisher:
pypi-publish.yml on jultou-raa/GraphMDO
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
graphmdo-1.0.0.tar.gz -
Subject digest:
07ea18bbeff670f7f94766022f2b937842ddf2792500714c18f22416ed8b82e4 - Sigstore transparency entry: 1075003044
- Sigstore integration time:
-
Permalink:
jultou-raa/GraphMDO@c81bab0f807db81f970dafabcc8f1be43e820cc6 -
Branch / Tag:
refs/tags/v1.0.0 - Owner: https://github.com/jultou-raa
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
pypi-publish.yml@c81bab0f807db81f970dafabcc8f1be43e820cc6 -
Trigger Event:
release
-
Statement type:
File details
Details for the file graphmdo-1.0.0-py3-none-any.whl.
File metadata
- Download URL: graphmdo-1.0.0-py3-none-any.whl
- Upload date:
- Size: 66.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
307b23c7113b35f5e739f7ab621e3a1d4212c67f52b328de95ef188671083388
|
|
| MD5 |
9a87fc1fbef2ee0fd968ba1f4d88ad24
|
|
| BLAKE2b-256 |
f20f419ef7dcba16c76786d2c4c48cd381ae0e764b57c9f689f61b80de469563
|
Provenance
The following attestation bundles were made for graphmdo-1.0.0-py3-none-any.whl:
Publisher:
pypi-publish.yml on jultou-raa/GraphMDO
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
graphmdo-1.0.0-py3-none-any.whl -
Subject digest:
307b23c7113b35f5e739f7ab621e3a1d4212c67f52b328de95ef188671083388 - Sigstore transparency entry: 1075003087
- Sigstore integration time:
-
Permalink:
jultou-raa/GraphMDO@c81bab0f807db81f970dafabcc8f1be43e820cc6 -
Branch / Tag:
refs/tags/v1.0.0 - Owner: https://github.com/jultou-raa
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
pypi-publish.yml@c81bab0f807db81f970dafabcc8f1be43e820cc6 -
Trigger Event:
release
-
Statement type: