Stormwater-Management-Model icon indicating copy to clipboard operation
Stormwater-Management-Model copied to clipboard

Open Water Analytics Stormwater Management Model repository

Results 40 Stormwater-Management-Model issues
Sort by recently updated
recently updated
newest added

This was reported by a pyswmm user. When we use the `swmm_setSimulationDateTime` SWMM recalculates the new `StartDateTime` and `TotalDuration` or `EndDateTime` and `TotalDuration` for the state and end times, respectively....

```cmd ", line 48, in after_start_callback SU1.initial_depth=8 ^^^^^^^^^^^^^^^^^ File "/Users/bryant/local_development/pyswmm/_attic/venv/lib/python3.12/site-packages/pyswmm/nodes.py", line 430, in initial_depth self._model.setNodeParam(self._nodeid, NodeParams.initDepth.value, File "/Users/bryant/local_development/pyswmm/_attic/venv/lib/python3.12/site-packages/pyswmm/swmm5.py", line 701, in setNodeParam solver.node_set_parameter(index, parameter, value) File "/Users/bryant/local_development/pyswmm/_attic/venv/lib/python3.12/site-packages/swmm/toolkit/solver.py", line 1117, in...

Closes #189 Hello Bryant, Here are the modifications we was talking about. I'm not so sure about the units. As I told you before this is the first time I...

type:enhancement
Easy

The API for getting/setting RDII parameters can be useful during the calibration or RTK values using measured flow/depth data.

Documentation in its current state does not reflect all the functionality of OWA-SWMM.

type:tech-debt

I think it's time to dream up an Input API that will find its way into the formal distribution of SWMM. :) @rkertesz @fmyers @michaeltryby

type:enhancement

If you are a contributor or user of this library please consider the implications of relicensing on your work and comment here. Thank you for supporting our project!

type:discussion

I posted this suggestion in the OpenWaterAnalytics/pyswmm and was referred to ask it here. It seems that Subcatchment parameters that can be set by user are limited to width, area,...

The subcatchment runoff rate returned by the API endpoint is missing LID runoff rate. This issue is significant when LIDs cover the entire subcatchment. https://github.com/OpenWaterAnalytics/Stormwater-Management-Model/blob/6d6b5272250acaa3939db9e265f0e593dc96e43e/src/solver/toolkit.c#L2150-L2191 https://github.com/OpenWaterAnalytics/Stormwater-Management-Model/blob/025337c026dc2b6d493fb23ab05016329f7547cb/src/solver/output.c#L588 https://github.com/OpenWaterAnalytics/Stormwater-Management-Model/blob/develop/src/solver/subcatch.c#L866-L932 https://github.com/OpenWaterAnalytics/Stormwater-Management-Model/blob/025337c026dc2b6d493fb23ab05016329f7547cb/src/solver/subcatch.c#L894-L905

type:bug

``` { "project": "SWMM", "organization": "Open_Water_Analytics", "version": { "string": "5.1.14", "major": "5", "minor": "1", "patch": "14" }, "git_hash": "6d74d607553c3edc7004192b6e847fa79cbd117d", "platform": "Darwin", "complier": { "id": "AppleClang", "version": "13.0.0.13000029" }, "build_id": "2021-11-08T16:06:48Z"...

Easy