Run MIKE+ simulations headless via the mike-plus MCP server and report result files + engine status. Use when an agent must execute a MIKE+ .sqlite model's active (or a named) simulation without opening the MIKE+ GUI, then hand the .res1d outputs to reading/plotting. Requires MIKE+ installed + a valid license. Always run on a copy.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Executes a MIKE+ model headless through the mike-plus MCP server (engine: MIKE 1D).
After a model is ready and you need to actually run it — the active simulation, or a named setup from msm_Project. Do not use this to read results (that's mike-results) or to plot (mike-plot). The whole-workflow rules (run directory, copy policy, stop rules, QA gates) are in mike-end-to-end; a baseline-vs-variant pair of runs is compared with mike-compare.
mike_run — args: sqlite (path), simulation (optional setup id), timeout_s (optional). Returns {ok, active_simulation, result_files[], elapsed_s}, a parsed QA gate {completed, errors, warnings, issues, status, log_file}, and _log_tail (engine console).mike_run loads the local MIKE 1D engine; it fails on a machine without MIKE+ + a valid license. (Reading/plotting do not.)ok. ok only means the call returned. Check status: ok / completed_with_warnings are usable; completed_with_errors or incomplete mean the run is untrustworthy — surface errors/warnings and point at log_file for detail, don't bury them. status="unknown" means no engine log was found.result_files to mike-results / mike-plot, and the whole return value to mike_manifest_write (mike-audit).mike_model_info -> confirm the active simulation / pick one (mike_set_scenario if a GUI scenario is wanted)
mike_run -> result_files (.res1d) + status
-> mike-results (summary / flooding / read) -> mike-plot -> mike-audit
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record provenance for an Agentic MIKE+ step via the mike-plus MCP server — a manifest.json tying the model copy, inputs, edits, run QA status, result files and figures together, each file with a sha256. Use at the end of every run/compare/plot task (successful or failed) so the work can be audited, re-compared or reproduced later. No license required.
The English summary is being prepared. Showing the original description.
Compare two MIKE+ runs via the mike-plus MCP server — baseline vs scenario, before vs after a parameter edit — to say WHERE a change mattered and BY HOW MUCH (delta peak, delta volume, timing shift, RMSE/NSE) and to draw the overlay hydrograph. Use whenever two .res1d files of the same model exist or a re-run just finished. Comparing needs no license; producing the second run does.
The English summary is being prepared. Showing the original description.
Standard operating procedure for an auditable, headless MIKE+ workflow via the mike-plus MCP server — how to plan, copy, run, QA-gate, compare, plot, audit, and safely stop. Use FIRST whenever an agent is handed a MIKE+ model (.sqlite) or result (.res1d) plus a plain-language goal; it picks the operating mode and tells the agent which mike-* skill to open next and in what order.
The English summary is being prepared. Showing the original description.
Bring an EPA SWMM (.inp) or EPANET (.inp) model into MIKE+ via the mike-plus MCP server — the bridge from an INP builder such as SWMMCanada or agentic-swmm into a MIKE+ database that mike_model_info / mike_run can use. Use when the user has an .inp and wants it in MIKE+. Requires MIKE+ installed + a checked-out license (demo mode caps the model size).
The English summary is being prepared. Showing the original description.
Inspect a MIKE+ .sqlite model via the mike-plus MCP server — active simulation/scenario/model type, unit system, the list of simulation setups and scenarios, element counts — and switch the active scenario. Use when an agent needs to understand a MIKE+ model before running or editing it, or must run a scenario prepared in the GUI. Requires MIKE+ installed + a license.
The English summary is being prepared. Showing the original description.
Read and modify MIKE+ model parameters via the mike-plus MCP server — inspect or change values in any model table (pipe Diameter/Manning in msm_Link, node levels in msm_Node, catchment properties in msm_Catchment, etc.). Use when an agent must identify a current parameter and change it before re-running. Requires MIKE+ + license; mutating tools must run on a copy.
The English summary is being prepared. Showing the original description.