Read MIKE+ .res1d results via the mike-plus MCP server — list contents, summarize peaks, extract a single time series, or check which nodes flood (peak water level vs ground level). Use when an agent needs to inspect or pull numbers from MIKE+ network results (node water levels, link/reach discharge, velocities, flooding). No MIKE+ license or installation required.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Reads MIKE+ .res1d result files (via mikeio1d). No license / no MIKE+ install needed — fully portable.
To find out what is in a result file, get peak values, extract a series for analysis/plotting, or answer "which manholes flood?". Use after mike_run, or on any existing .res1d. (Two result files side by side: mike-compare.)
mike_results_list — {res1d} → quantities, element counts + sample ids (nodes/reaches/structures/catchments), time range. Start here to discover valid quantity/element values.mike_results_summary — {res1d, quantities?, skip_hours?} → per-quantity peak (value, element, chainage, time), in the canonical schema.mike_results_read — {res1d, quantity, element, max_points?} → a single downsampled time series (times, values, unit, peak_value, peak_time).mike_results_flooding — {res1d, skip_hours?, top_n?, include_outlets?} → per node: peak water level vs ground_level (and critical_level) → n_flooded, flooded[] ranked by exceedance (freeboard_m < 0, with peak_time, node type), n_above_critical, closest_to_flooding[]. Outlets are skipped by default (their level is the boundary, not flooding).Quantity:ElementId[:chainage] (e.g. Discharge:Link_29:33.5333). element matches the id prefix.{engine, quantity, element_id, chainage, unit, ...}) so the same downstream skills work for SWMM/LSTM later. (mike_results_summary reports the peak's element as peak_element — same idea, named for the peak.)mike_results_summary returns the max over the WHOLE run, which can land in the warm-up / initial-condition period (e.g. a base-flow value near t=0), not the storm peak. Always check peak_time; when you want the event peak, pass skip_hours (e.g. skip_hours: 6) to drop the initial window. The same applies to mike_results_flooding.critical_level (e.g. 100 m) or river/basin nodes may carry a nominal ground level: report the type and level, and let the user judge; do not filter them silently (only outlets are excluded by default, and that is stated in the output).quantity/element has no series, say so (the tool errors with a clear message) rather than guessing.mike_results_list -> learn quantities + element ids
mike_results_summary -> peaks for a quick read (skip_hours)
mike_results_flooding -> flooded nodes ranked (skip_hours)
mike_results_read -> a series for a specific element -> mike-plot
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.