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.
See how to installReview the instructions the agent will receive before you install.
Closes the loop identify -> change -> re-run -> compare. Works on any two .res1d
files with the same element ids (same model, different parameters / scenario / rain).
runs/<case>/00_model_baseline/ <- copy of the model folder, untouched
runs/<case>/00_model_<variant>/ <- second copy; mike_set_values here only
mike_run on each -> A.res1d (baseline), B.res1d (variant)
Why not mike_set_scenario + create a scenario? Verified on MIKE+ 2026: a scenario
created through mikeplus shares its parent's alternatives, so an edit "in the
scenario" changes Base too; and if the scenario is given its own alternatives,
mikeplus cannot write into them (mike_set_values reports "did not persist").
mike_set_scenario is therefore only for running scenarios that were prepared in
the GUI. Copies are unambiguous and audit-friendly.
mike_results_compare — {res1d_a, res1d_b, quantity, element?, skip_hours?, top_n?, label_a?, label_b?}
element): peak change for every element of quantity, sorted by |delta| — by_element.top[], n_increased / n_decreased / n_unchanged, n_only_a/b (ids missing on one side). Ask this first: "where did my edit matter?"element given): comparison{peak_a, peak_b, delta_peak, delta_peak_pct, peak_time_a/b, peak_time_shift_min, mean_a/b, max_abs_diff(+time), rmse, nse_b_vs_a}; for flow quantities (unit m3/s) also volume_a/b, delta_volume(_pct) in m3. aligned = exact (same time base) or interpolated (B was interpolated onto A's steps; say so).mike_plot_compare — {res1d_a, res1d_b, quantity?, element, out_png, label_a?, label_b?, rain_dfs0?, skip_hours?} → overlay (baseline dashed grey, variant solid orange), optional inverted hyetograph on top. House style; no title.skip_hours (warm-up) to both.mean / max_abs_diff.nse_b_vs_a measures how different B is from A (1 = identical), not model skill.n_only_a/n_only_b > 0, the two runs are not the same network: say so before comparing further.{ok:true, png}.mike_results_compare (ranked, quantity=Discharge|WaterLevel) -> top elements
mike_results_compare (element=<top id>) -> deltas for the story
mike_plot_compare (same element, rain_dfs0 if any) -> 03_plots/compare_<id>.png
mike_manifest_write (both res1d as results, the edit as edits)
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.
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.
Produce publication-style figures from MIKE+ .res1d results via the mike-plus MCP server — a stacked rainfall-runoff hydrograph, a single time series, a network map, a baseline-vs-scenario overlay, or a longitudinal profile (bed / crown / ground / max water level along a pipe string), in the house style (Arial 12, ticks inward, SI units, no title). Use when an agent must render MIKE+ results as a PNG without opening the GUI. No license required.
The English summary is being prepared. Showing the original description.