Sunday, May 14, 2023

Basic Files in InfoSewer and InfoSWMM


Below are tables that organize the information provided for the basic files in InfoSewer and InfoSWMM:

Basic Files in InfoSewer

Each Project ContainsProject Storage Structure
Network MapNetwork Schematic - Stored as *.MXD File.
Feature AttributesDatabase Tables and Modeling Files - Stored as *.IEDB Folder
Modeling ParametersResults Directory - *.OUT Folder (post-successful Run).
Model Solution and Results
Model Scenarios

Files Associated with Each Scenario in InfoSewer

File TypeFile Extensions and Names
Text Files~SSNINP, ~DGNINP, ~EPSINP, STEADY.RPT, DESIGN.RPT, EPS.RPT
Binary FilesSTEADY.OUT, EPS.OUT

Basic Files in InfoSWMM

Each Project ContainsProject Storage Structure
Network MapNetwork Schematic - Stored as *.MXD File.
Feature AttributesDatabase Tables and Modeling Files - Stored as *.ISDB Folder
Modeling ParametersResults Directory - *.OUT Folder (post-successful Run).
Model Solution and Results
Model Scenarios

Files Associated with Each Scenario in InfoSWMM

File TypeFile Extensions and Names
Text FilesHYDQUA.INP, HYDQUA.RPT.TXT, HYDQUA.HTML
Binary FilesHYDQUA.OUT

These tables provide a structured view of the essential components that constitute an InfoSewer and InfoSWMM project. Each project element is essential for the visualization, manipulation, and analysis of hydraulic data within the respective software.

How to import infoSewer into InfoSWMM

 How to import infoSewer into InfoSWMM

The direct import of InfoSewer to InfoSWMM (Figure 1) is both direct and robust, but you must be aware of Run Manager changes to optimize the InfoSWMM model: by Mel Meng, 10/9/2019
Jul 19, 2022Knowledge

DESCRIPTION
Importing Data from InfoSewer to InfoSWMM

The direct import of InfoSewer to InfoSWMM (Figure 1) is both direct and robust, but you must be aware of Run Manager changes to optimize the InfoSWMM model:


1. Ensure that the Flow Units in InfoSWMM Run Manager match the default flow units in InfoSewer so that the DWF values are comparable.

2. Ensure that the Output Flow Units in InfoSWMM match the Output Flow Units in InfoSewer so that direct comparisons are possible.

3. Add a Pump On and Pump Off depth to the Pumps in InfoSWMM so that the pumps work better in a fully dynamic solution.

4. The Fixed Pump Curves of InfoSewer should be checked in the Pump Curve section of InfoSWMM to ensure they are comparable.

5. If your InfoSewer links are short, use the InfoSWMM conduit step lengthening option to speed up the model.

6. You can compare the overall balance in the two modeling platforms by comparing the System Load Graph in InfoSewer to the Total Inflow Graph in InfoSWMM.

InfoSewer models can be imported info InfoSWMM, however not the other way around. Prior to initializing the InfoSWMM model import the InfoSewer Model from the InfoSWMM Dropdown menu > Project > Import InfoSewer. And only one scenario can be imported.

image.png

Approaches for representing a culvert within the 2D domain (ICM)

 From the Innovyze Blog 

Approaches for representing a culvert within the 2D domain (ICM)

This article details some of the methods available to the user when they are trying to represent culverts in ICM which accept flow from the 2D mesh. These approaches will extend to underpasses and similar structures, although they may be best represented using Base Linear Structures (2D).
Mar 8, 2022Knowledge

DESCRIPTION

Introduction

In this article we’ll give recommendations on how to model culverts which will interact with the 2D mesh in our ICM model. For this purpose our culvert is assumed to be a structure which has a depth which may impact its hydraulic performance. For structures which are less than a 2D element in depth the "Base linear structure (2D)" line may provide the best form of representation. More information can be found in the Help files: LINK

When modelling a culvert in the 2D domain it is different from a normal 1D pipe configuration; culverts don't have manholes at either end, they open directly to the channel. The wingwall arrangement, if present, is likely to control the hydraulic performance at the inlet.
 
image.png

When considering the “ground level” it is very important to match the culvert inlet and outlet levels with the bed of the channel. That is where the linkage is going to be taking place and where the calculation points will be taken from.
 

Approaches

2D Conduit

2D conduits are recommended if stability is a concern. This is because the flow does not have to be exchanged between the 1D and 2D engine at the coupling points (nodes). It will also ensure the continuity of mass and momentum in the calculations. However, at present the 2D Conduits do have limited functionality in terms of shapes and inlet / outlet headlosses cannot be modelled directly.
 
Connect 2D > 2D Conduit > Connect 2D

This approach is best avoided for small pipes as the conduit is descritized into elements. This could lead to the generation of small internal elements and significant impact model run times.
 

1D Conduit

If you need to model the culvert using the FHWA/CIRIA method, things can get tricky because the method is only developed for 1D. In theory, we should model a section of the channel and the culvert in 1D. Therefore, we’ll need to model the channels as 1D river, and connect the 1D river to the 2D surface. The system could look like this:
 
Inline bank > River reach > Culvert inlet > Conduit >  Outfall 2D

We might need to a Culvert outlet link and another section of downstream river reach with an inline bank if reverse flow is expected.

As you can see this approach can be quite tedious, and it is still prone to stability issues with the complication of 1D river sections and inline banks. And without calibration data, it can be hard to judge which method is more accurate.

In practice, you might want to try different variations of this setup. For example, you can simplify this setup without adding the river reaches and the outlet link but it would be sensible to check the stability and validity from the model results:
 
Outfall 2D > Culvert Inlet > Break node > Culvert > Outfall 2.
 

1D-2D linkage basis

When linking a culvert to the 2D mesh using Connect 2D or Outfall2D, in most cases we should use the "Depth" basis because a culvert should be flush with the channel bed. There may be some very localised scour, but we can overlook that in the majority of cases. The "Elevation" linkage should only be used where the culvert entrance / exit is at a high level above the ground level (i.e. channel bed level).
 
image.png
 
If the entrance to the culvert is below the ground level of the terrain model, then the mesh elements at the entrance will have to be lowered to that level to reflect the topology of the channel bed. This can be achieved using a mesh zone or mesh level zone. It can also be a very good idea to use a mesh zone to increase the element size where the connection is made, this can help to increase the element area(volume) and reduce drying or oscillations that may occur on small elements.
 
image.png

FAQ

Can I use node types other than Connect 2D for 2D conduit? If so, which type should I use?

When using conduit 2D, you can choose to use types other than connect 2D, but it will turn the node into a manhole and transfer the flow into the 1D engine. This would negate the reason for using the 2d conduit.

When modelling a 1D culvert, what type of node to choose from? Outfall 2D, manhole, connect 2D which one to choose from?

If you are modelling using a 1D conduit, use Outfall 2D to connect the culvert to the 2D. You should not use a manhole type node to connect a culvert to 2D. The node type between a river reach and any link is always a "break" node type.

What is the difference between 1D-2D linkage basis elevation vs depth?

Users should really follow the rule that “elevation” applies when the conduit invert is above the element level i.e. the pipe is significantly raised above the bed. Minor differences due to scour can typically be ignored.

For Outfall2D/Connect 2D when using elevation basis, what elevation is used?

ICM will look at the elevation of water in the element and the elevation of water in the node/conduit to calculate a head difference and flow rate.

How to model blockage and flap gate for culvert?

Blockages can be modelled by either adding “sediment” to the conduit or adding a “blockage” link to the appropriate location. Note that a blockage link is intended for calibration against recorded data. A flap valve can be modelled to ensure unidirectional flow. However, all of these would currently dictate employing the 1D-2D connection mentioned above.

For a more in-depth discussion of culvert design, refer to this medium post: HDS 5 .

My blogs and the Taxicab number 1729

My blogs and the Taxicab number 1729  

The help file of ICM SWMM (Storm Water Management Model) and InfoWorks networks is undoubtedly world-class, and the online version provided by Autodesk with ICM Standard and Ultimate 2024 is exceptional. It provides comprehensive guidance, detailed descriptions, and user-friendly navigation, making it a powerful tool for anyone seeking to understand and utilize these complex software systems.

However, there is one limitation I've observed with the Autodesk online version - it lacks a significant number of 'how-to' guides. These guides are vital for users, especially beginners, as they provide step-by-step instructions on how to use specific features or perform specific tasks.

In my case, I want to demonstrate how ICM SWMM and ICM InfoWorks networks are interconnected and coexist within the same Graphical User Interface (GUI). These two software systems share the same 2D engine, indicating a high level of integration and compatibility. This integration makes it possible for users to switch seamlessly between the two systems within the same interface, thus increasing efficiency and user-friendliness.

As an avid LinkedIn user, I appreciate the feedback I receive from my followers, and I find the platform's article format to be extremely conducive for sharing knowledge and insights. I enjoy the professional interaction and the knowledge-sharing aspect of the platform, which allows me to connect with like-minded professionals in my field.

The reason I chose to post this information here on LinkedIn is to provide a more in-depth explanation of both ICM InfoWorks and ICM SWMM. I believe using a single model example to demonstrate how these two systems interact and coexist will be beneficial to my followers and anyone else interested in these systems.

My ultimate goal is to make these complex systems more accessible and understandable to a wider audience, thereby encouraging more people to utilize these powerful tools in their work. By explaining the intricacies of these systems, I hope to bridge the gap between the users and the software, allowing for a more efficient and effective use of these engineering tools.

 

In addition to the Autodesk resources and my LinkedIn posts, there are other valuable sources of information available. I manage two blogs - swmm5.org and swmm446.com - that delve deeper into the world of SWMM. These blogs offer a wealth of resources, from basic guides to in-depth analyses, that cater to both beginners and experienced users alike.

Another resource worth mentioning is the official Autodesk Innovyze blog (https://blogs.autodesk.com/innovyze/). This blog is managed by Autodesk's top-tier writers who possess a profound understanding of our software. They consistently produce high-quality content that showcases our software in all its glory, providing users with a comprehensive understanding of its features, capabilities, and potential applications.

As for my LinkedIn articles, I've adopted a unique organizational structure inspired by the taxicab number 1729, which has the factors 1, 7, 13, and 19. This structure involves dividing the content into 13 main topics, each of which has seven subtopics - totaling 91 specific points of discussion within each main topic.

For instance, in my 'Elephant Stories' blog series, I aim to generate a total of 91 stories or sub-blogs. Once I've completed these 91 pieces, I'll move on to the next topic and create another set of 91 sub-blogs. This methodical approach allows me to cover a wide range of topics in a comprehensive and systematic manner.

This unique way of organizing content not only helps me stay focused and structured in my writing but also makes it easier for readers to navigate through the various topics and subtopics. It offers a clear roadmap of what to expect and ensures a balanced distribution of content across a diverse range of subjects.

Streets in SWMM 5.2+

 


The purpose of this entry is to define and describe the cross-sectional geometry of conduits that are used to represent streets in a certain engineering or urban planning context.

Format: The required format to define these parameters follows a certain order: Name Tcrown Hcurb Sx nRoad (a W)(Sides Tback Sback nBack)

Parameters: Each parameter represents a specific aspect of the street's cross-sectional geometry.

  1. Name: This is the unique identifier or name assigned to the street cross-section.

  2. Tcrown: This represents the distance from the street’s curb to its highest point or crown. The measurements are in feet or meters.

  3. Hcurb: This parameter indicates the height of the curb, measured in feet or meters.

  4. Sx: This is the cross slope of the street, expressed as a percentage.

  5. nRoad: This is the Manning’s roughness coefficient (n) of the road surface. It is a measure of how rough the surface is and affects how water flows over it.

  6. a: This parameter represents the gutter depression height, measured in inches or millimeters. It defaults to 0 if not specified.

  7. W: This is the width of the depressed gutter, measured in feet or meters. It defaults to 0 if not specified.

  8. Sides: This indicates whether the street is single-sided or two-sided. It defaults to 2 if not specified.

  9. Tback: This is the street backing width, measured in feet or meters. It defaults to 0 if not specified.

  10. Sback: This is the slope of the street backing, expressed as a percentage. It defaults to 0 if not specified.

  11. nBack: This is the Manning’s roughness coefficient (n) for the street backing. It defaults to 0 if not specified.

Remarks:

If the street does not have a depressed gutter (meaning a = 0), then the gutter width parameter (W) is ignored. Similarly, if the street does not have backing, the three backing parameters (Tback, Sback, nBack) can be omitted. This allows for flexibility and customization based on the specific characteristics of each street.

GitHub code and Markdown (MD) files Leveraging

 To better achieve your goal of leveraging your GitHub code and Markdown (MD) files for your WordPress blog or LinkedIn articles, consider t...