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.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Renders MIKE+ results in the project house style. No license / no MIKE+ install needed.
Arial 12 · ticks inward (direction='in', both axes) · SI units · no title · inverted hyetograph · dpi 300. Rain #4C78A8, flow #F58518, baseline-in-a-comparison #4D4D4D (dashed). Style lives in mikeplus_mcp/contracts/plot_style.py and is shared with the SWMM figures layer.
mike_plot_rain_flow — {res1d, element, quantity?='Discharge', rain_dfs0?, out_png} → stacked two-panel figure: rainfall inverted on top, flow on the bottom, shared time axis. rain_dfs0 is optional (a .dfs0); without it only the flow panel is drawn.mike_plot_timeseries — {res1d, quantity, element, out_png} → single-panel series.mike_plot_network — {res1d, out_png} → network layout map (reaches as lines, nodes as points, equal aspect). Use for an overview / location figure of the whole model.mike_plot_compare — {res1d_a, res1d_b, quantity?, element, out_png, label_a?, label_b?, rain_dfs0?, skip_hours?} → overlay of the same series from two runs (baseline dashed grey, scenario solid), optional hyetograph on top. Numbers come from mike_results_compare (see mike-compare).mike_plot_profile — {res1d, reaches?[] | from_node + to_node, out_png, skip_hours?} → longitudinal profile along a pipe string: bed/invert, pipe crown (invert + height), ground level (interpolated between nodes) and the max water level envelope vs cumulative chainage, node boundaries marked. Give the ordered reach ids, or two node ids and the shortest chain is found (flow direction first). Returns reaches, length_m, max_water_level (+ chainage, reach), min_freeboard_m, connectivity_problems.element / quantity / node ids with mike_results_list first; don't guess ids.{ok:true, png:...} and the file was written.skip_hours so the envelope is the storm, not the initial condition; if connectivity_problems is non-empty the chain you gave is not contiguous, say so.Requests like a stage-discharge curve, a flooding map, a 2D (dfsu) inundation map, catchment runoff panels, or an animated profile are not covered. Do not force an existing tool to fit them:
.res1d (or other file) exists and mike_results_list shows the quantity/element.mike_results_read / mike_results_compare and say the figure type is not available yet.contracts/plot_style.py + workers/plot_worker.py + tools/plot.py (house style, tested on a real res1d) — do not paint ad-hoc matplotlib in a chat unless the user asks for a one-off.mike_results_list -> pick element + quantity (or a reach chain / two nodes)
mike_plot_rain_flow | mike_plot_timeseries | mike_plot_network | mike_plot_compare | mike_plot_profile -> out_png
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。