Release notes

Release 3Di - Hotfix

On Monday January 14th, we will release a hotfix on our 3Di servers. We expect a very limited downtime around 8.00 AM (CEST).

After the hotfix, the following issues will be fixed:

  • Bug concerning the chosen boundary condition type for some cases that include 1D and 2D boundaries
  • For a specific combination of SpatiaLite-settings, e.g. multiple entries in v2_global_settings table, egg-shaped profiles were not processed correctly
  • DEM edits are now possible outside the -10 m and +10 m range

Furthermore, on de LiveSite a wider range of design rainfall events is availble. This concern some specific Dutch rainfall events (DPRA buien).

The next full release of 3Di is scheduled for the 4th of March. Therefore, the Web Interface will be unavailable between 8.00 AM and 12.00 AM (CEST).

Release 3Di – Hotfix

On the 5th of December 2018 3Di, will be updated with some minor fixes. These include:

  • The cross-sections in case of a breach in combination with interflow
  • The 1D discharge written in the results NetCDF and the aggregation NetCDF in some special cases
  • Included a correct initialisation for aggregation setting ‘current’

Release 3Di – Fall Release 2018

The newest version of 3Di is released on 26th of November 2018. With this update, the following features are available for all users of 3Di:

  • Interception
  • Culvert discharge coefficients
  • Water balance tool
  • Option for custom rain event
  • Software updates and bug fixes

Interception

With this release, we introduce a new process in 3Di to extend the processes of the hydrological cycle. It is now possible to take interception into account during your simulation. Interception refers to precipitation that does not reach the bottom, but is instead intercepted by buildings or vegetation.

The interception layer can be used in the following situations:

  • The obvious application is to take the effect of interception into account due to vegetation, green roofs and other buildings.
  • However, it can also be used in the so-called hybride models, where urban areas are modelled and the inflow to the sewer from buildings is directly coupled to the sewer system.

It is possible to edit the interception layer in the 3Di live site.

Culvert discharge coefficients

From this release, the culvert discharge coefficient will be enabled. The coefficient allows to take inlet losses for culverts into account and can be defined for positive and negative flow directions. The coefficient is defined via an attribute per culvert in the table ‘v2_culvert’. Prior to the release, the coefficients were already available in the spatialite. However, these coefficients were not yet taken into account. After the release, these will become active, this might, of course, affect the results. In case, these coefficients were unintended, set these coefficients to 1, and you will return to your previous results.

Water balance Tool

A new version of the 3Di QGIS plugin is released as well. Hereby, we also release the 3Di water balance tool. Users can select an area on the map and see the exact water balance, including an overview of the flows between the 2D surface water, 2D groundwater and the 1D flow domains for a certain area and period. To be able to use this water balance an aggregation NetCDF is required. This exciting new tool helps users to get an improved insight in their water system. With this water balance tool, we help experts in their analysis and understanding of the modeling results.

For more information have a look at our documentation on the Water Balance Tool. Here, one finds an overview of the aggregation settings required for the use of the water balance tool as well.

The water balance tool is an initiative of Deltares and a co-creation of experts of Deltares and Nelen & Schuurmans. It is co-funded by the Ministry of Economic Affairs (Top Sector Water).

Option for custom rain event

In the 3Di live site, the options for rain events are extended. It is now possible to define a time-varying rain event.

Software updates and bug fixes

Behind the scenes there have been some major changes to the 3Di software. We have fundamentally improved the server-interaction. Note, this changed some minor things. When you want to load a new model, quit your previous session first. Your session on the live site will close after 1 hour of inactivity. Use the API, for longer simulations with no interaction.

Threedigrid has been extended with some more information of your model to allow for a more accessible analysis.

Moreover, several bug fixes have been performed. These include;

  • The message No more sessions available was sometimes visible, when it was not true. We have added a new session count system, which eliminates this bug
  • No more potentially leaking levees in case of interflow
  • Removed check for type 2 pumps on lower stop level.
  • Added check for overlapping vertices in channels and culverts
  • Fix in visualizing the groundwater results in the live site
  • Fix for dealing with obstacles after a DEM-edit

Release 3Di – Autumn Release 2018

The newest version of 3Di is now available. With this update, it is possible to edit the bathymetry layer in the 3Di live site. The following has been adjusted in 3Di:

  • Bathymetry edits in live site
  • Groundwater levels visible in live site
  • Friction based on the Chezy formulation in 2D domain
  • Adjusted logging
  • Documentation update

Moreover, we took measures for the maintenance of the 3Di software. Soon you will receive an update with several developments around our QGIS plugin.

Please note! Due to technical problems, not all input files are updated to the newest 3Di version. We expect all models to be available October 8th. You can update the input files of your own model to the newest version manually, by following the tutorial at the end of these release notes. You are also welcome to contact our service desk to update the model for you.

A DEM (Digital Elevation Model) edit is the newest tool in our live site, it allows to adjust the height of the bathymetry. This can be done at any time during the simulation by drawing a polygon. The DEM edit is immediately committed when finishing the polygon. The result can be checked using the ‘Cross profile’ tool. A DEM edit is also possible via our API , thereby allowing external applications to perform a DEM edit as well. However, the steps performed by ‘process results’ do not take the DEM edit into account. Take this into consideration when interpreting the results.

In our previous release ground water has been added to 3Di. From now on groundwater levels are visible in the live site in the cross-profiles and in a pop-up panel for waterlevels.

From the start of 3Di, the Manning formulation is implemented to compute friction. In some cases users prefer to use a different friction formulation, for this the Chezy formulation is now available in the 2D domain.

The overview of the spatialite database is updated in our documentation, because we found an error in a cross-section definition. It concerns type 1 rectangle. We advise everyone to download the newest database overview: here

The next cases will be marked as “Error” instead of “Warning”. - Non-Existing foreign key relations, for example non-existing connections to impervious surfaces - Friction type has to be specified for 2D (required as we now support both Manning and Chezy) - Levee at inactive location in raster. Levee entree is skipped and lies between pixel coordinates ([i0,j0] and [i1,j1]) - Friction raster and DEM are not aligned, please check coordinates: - Maximum infiltration raster and DEM are not aligned, erroneous coordinates are: - Maximum infiltration raster and DEM are not aligned, number of erroneous coordinates exceed 10. File is not further evaluated and values are set to default value

We hope by doing this, to improve the feedback for users about errors in the model, before the model starts with the computation. When you receive one or more errors, you cannot proceed with your simulation until your errors are resolved. We ask users to check the warning and error messages after the model generation and try to solve them before contacting the service desk.

To run some simulations in first week of October, you may need to update the input files of your model manually. This tutorial explains the manual steps:

  • Browse to https://3di.lizard.net/models
  • Search your model. If not listed, click on ‘also show repositories that do not have inp files yet’. Only the version of your latest commit of your model will be listed, during this week. When you need an older and/or pinned version, please contact the service desk. We will make this version for you available.
_images/rn_tut_1.png
  • After you have found your model, click the icon in the column ‘initialize inp generation’
_images/rn_tut_2.png
  • Depending on the size of your model, the input generation can take a few minutes up to 15 minutes before it appears.
  • As soon as the model appears, the column ‘last run’ will show a green button with the word ‘success’ or a red button with ‘failed’. In case, the generation failed, take a look at the log files.
  • Click on the button ‘success’
_images/rn_tut_3.png
  • Click on the pencil icon on the left [1] and then on the button ‘visible’. [2]
_images/rn_tut_4.png
  • Store your result (save icon appears on the location of the pencil icon) [1].
  • Your model is now ready for use in the live site and for use with the API.

Release 3Di - Hotfix

On Thursday the 5th of July, we released a new version of 3Di to solve some minor bugs. The following has been added or changed:

  • The wind forcing was not working properly after the previous release.
  • Some computations, run with the rain radar input from The Netherlands, endured from a specific technical problem with map projections between the live site and rain radar. This is fixed.

The log-messages concerning errors in input data is improved. Users can find the error messages in the logging files on the model page. However, 3Di became also more strict to errors. If errors occur in the grid generation, a simulation cannot be initiated. An example of an error, that is often ignored: is when the lower stop level of a pump is defined below the bottom level of the connection node. Naturally, this is an impossible configuration. Therefor, this needs to be fixed by the modeller.

Furthermore, if a certain error occurs more than 10 times it will stop printing the error. This is to ensure that the log files remain compact and readable. This does not mean that the error is less important. An example of an error message that is encountered many times is when users supply rasters that are not aligned.

In 1D modelling, a mapping table is build to map connection nodes with the (impervious) surfaces related to the inflow model. Previously, we needed the ids of the mapping table to be incremental with no missing numbers. This is not required anymore. An example: after building a mapping table, the user deletes one of these mappings. In the past this meant that the ids of the table needed to be rebuild. In the current situation, no further action from the user is required.

The formulation to compute the flow through a breach is improved, in response to lack of the flow through a breach in case of a very small breach and high infiltration.

Release 3Di – Spring Release 2018

On Monday the 28th of May 2018 the latest version of 3Di will be released. This is a so-called major release. The past months, the team included groundwater in 3Di. In close collaboration with Prof. Stelling and in association with Deltares, we extended 3Di to a two-layer system to be able to compute the interaction between surface water and groundwater. A more elaborate explanation about the new features can be found in the 3Di documentation (https://docs.3di.lizard.net).

Some other changes:

Some of the visualizations in the LiveSite are improved. For example, the levees and breach locations are much better visible. Also, more information about the computational grid becomes available, such as the deepest point in the cell, the IDs and the levee heights.

The progress of simulations that are computing via the API is shown on a progress bar. The progress bar can be found from the start screen (https://3di.lizard.net) under follow running simulations.

There are several adaptations in the input. There are three new input tables; v2_groundwater, v2_interflow and v2_simple_infiltration, to which you can refer to in the v2_global_settings table. The content of the final two table is not new, but are removed, for clarity, from the v2_global_settings table. In addition to this, there are some small changes concerning the aggregation input. For more detailed information, we refer to the 3Di documentation.

There will also be a new version of the 3Di Plugin required (Version 1.0). With this release, we meet different conventions for NetCDF (CF conventions). With the new 3Di Plugin, results from the old type and the new type of the NetCDF can be evaluated. Behind the scenes, there has been a lot of work to reorganize the Plugin, as a preparation to future developments.

Release 3Di – April 2018

On Monday the 23th of April 2018 the latest version of 3Di will be released. The 3Di team worked mainly on improving the performance of computational times when using the API, and on implementing groundwater flow. Groundwater flow will be available to everyone from next month. In this release we have worked on:

When you want to run batches of scenario’s or set up operational scenario’s the best route is using the API. An explaination for using the API can be found in the manual :https://docs.3di.lizard.net/en/stable/d_api.html

  • The computational times are greatly improved with this Release. Times can be up to ten times as fast.

Note: The reduction in computational time does not occur for simulations, making use of wind and/or breaches. It is no longer possible to follow these API simulations via the Livesite. At the next release, user feedback for API simulations in the livesite will be improved.

There are improvements concerning:

  • Computations using embedded channels
  • The stability of connection to the livesite to make it more robust.

On Monday the 23th of April 2018 the 3Di web interface will be unavailable between 8.00 AM and 10.00 AM (CEST). The next full release is planned on Tuesday May the 22nd 2018.