Replies: 1 comment 3 replies
|
Hi @asmunds, Technically you don't need this library to do it — optimizations are triggered by calling the Optimal Gateway REST API directly (typically available at http://localhost:18261/Gateway on the server its installed at). Optimal Gateway then reads its input from Mesh, runs the optimization, and writes the results back to Mesh. So the flow is: your script calls Optimal Gateway over REST, then you can use mesh-python to read the results out of Mesh afterwards. Adding it inside mesh-python is a different question. Everything this library exposes today (including the HydSim runs — run_simulation, run_inflow_calculation, get_mc_file) goes over the Mesh gRPC API to the Mesh server. Wrapping a call to a separate REST service would mean the library also needs to know Optimal Gateway's URL, auth and lifecycle, which is a bigger scope change than it looks. We'd rather not couple the two unless there's a clear need. Could you say a bit more about your use case? Specifically: are you looking for a convenience wrapper so it's all one client, or is something blocking you from calling the optimal gateway REST API from your own code? |

Uh oh!
There was an error while loading. Please reload this page.
Is it technically possible to add a feature to start an optimization in Optimal Gateway via this library?
All reactions