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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Opens a MIKE+ .sqlite and reports its high-level structure (via mikeplus).
First step on any unfamiliar model: find the active simulation (what mike_run would run), the available simulation setups and scenarios, the model type, and the network size. Then, if the goal names a scenario that already exists, activate it.
mike_model_info — {sqlite} → {active_simulation, active_scenario, active_model, unit_system, simulations[], scenarios[], counts{nodes,links,catchments}}. Read-only. For MIKE 1D models (CS_MIKE1D) the setups/counts come from msm_Project / msm_Node / msm_Link; for MIKE+ SWMM models (CS_SWMM, e.g. after mike_import_swmm) from mss_Project / mss_Node / mss_Link.mike_set_scenario — {sqlite, scenario} → activates an EXISTING scenario (name from scenarios[]), verifies by re-opening the database, and reports per alternative group whether the scenario has its own alternative (own_alternatives_in) or shares Base (shares_base_alternatives_in). Mutates the model's active state: use a copy.simulations list are msm_Project (or mss_Project) setup ids — pass one as mike_run's simulation to run a non-active setup.mike_set_scenario does not create scenarios, and edits made under a scenario either leak into Base (shared alternatives) or are refused (own alternatives): see mike-compare and use model copies.mike_model_info -> choose simulation / scenario -> (mike_set_scenario) -> mike_run -> mike-results / mike-plot
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.