Turn a timestamped rainfall CSV (design storm, gauge record, climate-scenario series) into a MIKE+ rainfall .dfs0 via the mike-plus MCP server, verified by read-back, ready to drive a model's rainfall boundary or to sit on top of a hydrograph figure. Use when the user brings rain as CSV or asks to run a model with a different storm. No license required (writing the file); wiring it into the model needs one.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
MIKE+ rainfall boundaries read a .dfs0 of Rainfall Intensity, mm/h,
mean-step-backward: exactly the shape of DHI's own example rain files
(Sirius_IDF_1year_rainfall.dfs0). This skill produces that file from a CSV.
mike_rain_to_dfs0 — {csv, out_dfs0, time_col?, value_col?, unit?, item_name?}
unit: 'mm/h' (intensity, default) or 'mm' (depth per step, converted with each step's own duration; the conversion is reported).{dfs0, item, n_steps, start, end, timestep_s, uniform_step, total_depth_mm, peak_intensity_mm_h, peak_time, conversion} after reading the file back.total_depth_mm and peak_intensity_mm_h; if uniform_step is false say so (MIKE 1D accepts irregular steps, but the user should know).mike-params on a COPY. The boundary lives in table msm_BBoundary (the rainfall row has TypeNo = 1; in Sirius_RTC its MUID is Rainfall) with columns
TSConnection = dfs0 path relative to the model folder (DHI's example: Sirius_IDF_1year_rainfall.dfs0), so write the new file into the model copy folder,TimeseriesName = the dfs0 item name (must match: pass item_name to mike_rain_to_dfs0, or set this column to Rainfall),DataTypeName = Rainfall Intensity.
mike_get_values {table: msm_BBoundary, columns: [TypeNo, TSConnection, TimeseriesName, DataTypeName]} first, then mike_set_values on that MUID, then run and check mike_results_summary..dfs0 is what mike_plot_rain_flow / mike_plot_compare take as rain_dfs0, so use it for the figure of the run it drove.mike_rain_to_dfs0 {csv, out_dfs0: runs/<case>/00_model/storm.dfs0, item_name: <existing TimeseriesName or 'Rainfall'>}
mike_get_values {sqlite: <copy>, table: msm_BBoundary, columns: [TypeNo, TSConnection, TimeseriesName]}
mike_set_values {sqlite: <copy>, table: msm_BBoundary, muids: [<rain row>], values: {TSConnection: storm.dfs0, TimeseriesName: ...}}
mike_run -> mike_results_summary (skip_hours) -> mike_plot_rain_flow {rain_dfs0: storm.dfs0}
mike_manifest_write {inputs: [csv, storm.dfs0], ...}
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.