We are now in a time where models no longer sit on the shelf and become out-of-date in between master plans. Improvements in computing resources, software, and weather forecasts allow any model to turn into a real-time forecasting system.
ICMLive lets you connect your ICM model to live data streams (and SWMMLive for SWMM models), and then run it on an automated basis on a server to produce forecasts and alerts. Once you have a model, the rest is quite easy. If you’re an InfoSWMM user, you’ll need to export your desired scenario as a SWMM INP text file and import it into SWMMLive.
• InfoWorks ICM or InfoSWMM with a calibrated model
• Install ICMLive/SWMMLive, Workgroup Data Server, Live Server, and Data Loader (refer to our Getting Started Document)
We often get asked about troubleshooting models, and it’s often quite a difficult task to provide a good response, as much of troubleshooting is based on modelling experience of a range of models over a prolonged period of time…even then there are new things which crop up with either we’ve never seen or even thought of. Anyway, I thought I would put together a few tips, things to look at when troubleshooting models. This is by no-means an exhaustive list but is the type of approach I would take to troubleshoot a model. I’ll focus on models which have successfully initialised as approaches to troubleshooting initialisation issues have been discussed elsewhere on this blog (http://blog.innovyze.com/2014/07/02/initialisation-in-infoworks-cs/).
Of course, troubleshooting a problematic, non-convergent model can be avoided by following best practice, providing sensible and well thought schematisation and using the validation errors/warnings to help the model process. I also find it useful to build models iteratively, testing the model out at various stages, for instance as a 1D river model, before merging with a 1D urban drainage model before merging with a simple 2D mesh, before adding mesh detail. It may be more time-consuming in the short term but my experience is that it helps solves many issues and speeds up the whole modelling process. In fact whenever I get sent an integrated 1D-2D model, the first thing I do is ‘turn off’ the 2D, by setting bank discharge coefficients to 0 and all 2D nodes to sealed flood types, to check the 1D model works on it’s own.
Simulation Log Files
The first point that you’ll notice that a model is non-convergent will be the premature failure of the simulation and the simulation icon in the database tree will turn red. I would advise reviewing the log file regardless of the simulation status. With a non-convergent simulation you will still be able to open the results but the first step should always be to take a look at the simulation log file (Right click on the simulation icon Open As…Log Results text). Scroll down to the bottom of the log file and you will see that final place that convergence failure occurred and the point the simulation ultimately failed.
Figure 1: Convergence Failure Message in Simulation Log File
In most situations it will be the locations noted here which are responsible for the simulation failure. Continue reading
Posted in ICMLive, InfoWorks ICM
Tagged 1D-2D, Banklines, Discharge Coefficient, failed, headloss, ICM, instability, poor convergence, Simulation parameters, Timestep, troubleshooting, unstable
The formal announcement of the retirement of InfoWorks WS was made on the 17th January 2017, following the successful introduction of InfoWorks WS Pro.
Following this schedule, the Support Program for InfoWorks WS was formally closed on 15th December 2017. All existing customer support contracts for InfoWorks WS have now expired. This does not affect support contracts for any other Innovyze products. Continue reading
One of the reasons that Innovyze implemented Scenario functionality in InfoWorks ICM is because there were some complaints about the process of exploring alternatives in ICM’s predecessor InfoWorks CS that we wanted to improve. In InfoWorks CS, any alternative to the Base network that was explored would require a new network. These alternatives were branched off from their parent network, sometimes creating large trees of networks. This was frustrating for a few reasons:
- This would often result in a large tree of networks, making it difficult to find the network alternative that you wish to work with. And cleaning up this tree of networks was difficult because if a parent network were deleted, all of its children (or branched networks) would have to be deleted.
- If a mistake were corrected (such as an incorrect pipe diameter) in a parent network, this correction would not get implemented in branched networks, so each network in the potentially very large tree of networks would need to be corrected.
One of the best features in InfoMaster is its flexibility in terms of leveraging GIS data and the ArcGIS data structure. 95% of the time, clients can apply data fields in whatever way they specify. However, there are some fields InfoMaster looks at specifically for specific functions. These are the 5%. Below are brief descriptions of these ‘special’ fields.
‘Special’ Facility Fields
These fields are System Fields from the InfoMaster Facility Data Import or Facility and Asset Type Manager windows. These fields directly relate to the clients Facility Types.
InfoNet 18.5 is now out in the wild and along with a wealth of new functionality, we’ve thrown in some that will hopefully make day to day usage somewhat more pleasant. One of these is the SQL dialog box which is now resizable. So for those of you who indulge in SQLs and specifically writing those long and complex SQLs then the following should bring you a smile.
We all know the classic SQL Dialog box…
Classic SQL Dialog Box
InfoWorks ICM version 8.0 was released with several new features. One new feature is the “Averaged Spatial Rainfall on TVD connectors” and this post is an example of the flexibility that it offers you.
What is it for?
Have you wonder what is the rainfall over an area? This can simply be answered with the “Averaged Spatial Rainfall on TVD connectors” feature.
The increasing resolution of spatial rainfall from radar data, with spatial resolutions as detailed as 50 metres, means the number of radar cells over an area can be significant and instead of analysing each cell you might want to analyse the average rainfall intensity over an area. This new feature enables you to calculate the Averaged Spatial Rainfall on a TVD connector polygon, which can then be used to plot rainfall averages and also to trigger alerts in a live system with InfoWorks ICMLive. Continue reading
This is the fourth instalment in a series of blogs I’ve written summarising run times for 2D simulations conducted on PC hardware and NVIDIA GPU cards. The first was in December 2012, I then followed up with a second in September 2016 and a third in June 2017. Each blog shows how InfoWorks ICM has been designed to leverage technological improvements as soon as new hardware platforms and new GPU cards come onto the market.
The tables below give simulation runtimes for two of our standard 2D testing models that were run on a high-end AMD based Workstation containing an NVidia GeForce GTX 1070Ti GPU card and a high-end Intel Xeon Server fitted with an NVidia Quadro GP100 GPU card. Continue reading
At the end of running a rehab flowchart, the rehab summary report is generated which shows the assigned rehab action for each pipe. However, many utilities and engineering consultants do not perform rehab actions on an individual pipe basis, but on many pipes grouped into individual projects. This blog addresses how InfoMaster users can bundle pipes into work orders and projects.
Many times, our clients will have custom inspection data for assets and will want to bring that information into InfoMaster. Because InfoMaster is extremely flexible with both GIS and tabular data, there are lots of ways of doing this, but the technique below is one suggested method. The following steps describe how custom inspection data can be brought into InfoMaster through the Work Manager tool.
1. First, convert your survey data to an attribute table and import this attribute table into your InfoMaster project database. Below is my example: