& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:03
When working with 2D modelling, ICM allows some tolerance and advanced 2D simulation parameters to be edited.
00:12
For typical models, there is no need to adjust these settings.
00:16
However, it is useful to familiarize yourself with these options.
00:21
Depth: Used to determine whether to consider a mesh element wet or dry.
00:27
Mesh elements with depth of water below this value are considered dry and only mass conservation will be considered.
00:35
Momentum: Depth threshold used to determine whether to consider momentum in a mesh element.
00:42
Movement of water is not calculated for mesh elements with depth of water below this value—only mass conservation is considered.
00:52
Velocity: Mesh elements with water velocity below this value have velocity reset to zero in terms of momentum calculations.
01:03
Ignore rain falling on dry elements: If checked, rainfall and evaporation applied to the 2D mesh is only applied to wet elements in the mesh.
01:14
Adjust bank levels based on adjacent element ground levels:
01:19
If selected, the levels of bank sections that are lower than adjoining mesh elements
01:25
are adjusted by the engine to match the mesh element ground level.
01:29
This is enabled by default.
01:32
Link 1D and 2D calculations at minor timestep: If unchecked, 2D calculations are performed at every run timestep.
01:42
If checked, the 2D simulation engine performs calculations at a maximum of every minor timestep.
01:50
Using this option may help in reducing the occurrence of oscillations at banks for some networks.
01:57
The Advanced tab includes settings used as part of the calculations.
02:02
For example: Timestep Stability Control: Ensures that the internal timestep used by the 2D engine
02:10
is within the stability bounds given by the CFL condition.
02:14
This is valid below 1.
02:17
Maximum Velocity: Sets a threshold limiting the velocities that can be achieved in an element in a 2D simulation.
02:26
Inundation mapping depth threshold: Depth threshold used to determine the time to first inundation for mesh elements,
02:35
reported as the time (from the start of the simulation) at which water depth in the mesh element first exceeds this threshold.
02:44
Steady state mode is only available on the CPU, as it is not widely applied.
02:50
When the Deactivate steady state areas option is checked,
02:54
the 2D engine checks if a local steady state has been reached in each element of the 2D zone.
03:01
Elements in the 2D zone are put in sleep mode whenever a steady state is reached.
03:07
The threshold criteria to determine whether an element has reached a steady state is specified in the fields of this tab.
03:15
This functionality has the potential to speed up simulations,
03:19
particularly in 2D river applications where 2D zones are large with different flooded areas acting independently.
03:28
GPU cards can be used to accelerate the 2D calculation speed for models with greater than 1,000 elements.
03:36
The more elements, the greater the benefit.
03:40
You can see how run times for large 2D models may compare between a CPU-only run,
03:46
taking around 2 hours, and a GPU run taking around 5 minutes to complete.
03:52
Any CUDA capable NVIDIA GPU card with compute capability 3.0 (Kepler family) or above
04:01
can currently be used for the 2D engine calculations.
04:05
Note that while this only speeds up the 2D engine, it can also reduce the load on the CPU undertaking the 1D engine calculations.
04:15
The time taken for a simulation should be considered additive between the 1D and 2D engine times.
04:23
The on-premise default is to use the GPU card for 2D calculations,
04:29
If suitable card is available.
04:31
Not all functionality is supported by the GPU.
04:35
If non-supported functionality is present in the network (such as sediment transport)
04:41
and the Always or If suitable card is available option is selected, the simulation fails or a warning is displayed in the log.
04:51
For cloud the default is to use the GPU card, If optimal for selected network.
04:58
This uses an algorithm to determine whether it will be quicker to run on the GPU or CPU.
05:05
You can override this by selecting the Never or Always options.
Video transcript
00:03
When working with 2D modelling, ICM allows some tolerance and advanced 2D simulation parameters to be edited.
00:12
For typical models, there is no need to adjust these settings.
00:16
However, it is useful to familiarize yourself with these options.
00:21
Depth: Used to determine whether to consider a mesh element wet or dry.
00:27
Mesh elements with depth of water below this value are considered dry and only mass conservation will be considered.
00:35
Momentum: Depth threshold used to determine whether to consider momentum in a mesh element.
00:42
Movement of water is not calculated for mesh elements with depth of water below this value—only mass conservation is considered.
00:52
Velocity: Mesh elements with water velocity below this value have velocity reset to zero in terms of momentum calculations.
01:03
Ignore rain falling on dry elements: If checked, rainfall and evaporation applied to the 2D mesh is only applied to wet elements in the mesh.
01:14
Adjust bank levels based on adjacent element ground levels:
01:19
If selected, the levels of bank sections that are lower than adjoining mesh elements
01:25
are adjusted by the engine to match the mesh element ground level.
01:29
This is enabled by default.
01:32
Link 1D and 2D calculations at minor timestep: If unchecked, 2D calculations are performed at every run timestep.
01:42
If checked, the 2D simulation engine performs calculations at a maximum of every minor timestep.
01:50
Using this option may help in reducing the occurrence of oscillations at banks for some networks.
01:57
The Advanced tab includes settings used as part of the calculations.
02:02
For example: Timestep Stability Control: Ensures that the internal timestep used by the 2D engine
02:10
is within the stability bounds given by the CFL condition.
02:14
This is valid below 1.
02:17
Maximum Velocity: Sets a threshold limiting the velocities that can be achieved in an element in a 2D simulation.
02:26
Inundation mapping depth threshold: Depth threshold used to determine the time to first inundation for mesh elements,
02:35
reported as the time (from the start of the simulation) at which water depth in the mesh element first exceeds this threshold.
02:44
Steady state mode is only available on the CPU, as it is not widely applied.
02:50
When the Deactivate steady state areas option is checked,
02:54
the 2D engine checks if a local steady state has been reached in each element of the 2D zone.
03:01
Elements in the 2D zone are put in sleep mode whenever a steady state is reached.
03:07
The threshold criteria to determine whether an element has reached a steady state is specified in the fields of this tab.
03:15
This functionality has the potential to speed up simulations,
03:19
particularly in 2D river applications where 2D zones are large with different flooded areas acting independently.
03:28
GPU cards can be used to accelerate the 2D calculation speed for models with greater than 1,000 elements.
03:36
The more elements, the greater the benefit.
03:40
You can see how run times for large 2D models may compare between a CPU-only run,
03:46
taking around 2 hours, and a GPU run taking around 5 minutes to complete.
03:52
Any CUDA capable NVIDIA GPU card with compute capability 3.0 (Kepler family) or above
04:01
can currently be used for the 2D engine calculations.
04:05
Note that while this only speeds up the 2D engine, it can also reduce the load on the CPU undertaking the 1D engine calculations.
04:15
The time taken for a simulation should be considered additive between the 1D and 2D engine times.
04:23
The on-premise default is to use the GPU card for 2D calculations,
04:29
If suitable card is available.
04:31
Not all functionality is supported by the GPU.
04:35
If non-supported functionality is present in the network (such as sediment transport)
04:41
and the Always or If suitable card is available option is selected, the simulation fails or a warning is displayed in the log.
04:51
For cloud the default is to use the GPU card, If optimal for selected network.
04:58
This uses an algorithm to determine whether it will be quicker to run on the GPU or CPU.
05:05
You can override this by selecting the Never or Always options.
Some tolerance and advanced 2D simulation parameters can be edited during 2D modelling.
Accessible from Run dialog box, 2D parameters button.
No need to adjust settings for typical models, but useful to be familiar with options."
Depth:
Used to determine whether mesh element is considered wet or dry.
Mesh elements with depth of water below value are considered dry, and only mass conservation is considered.
Momentum:
Depth threshold used to determine whether to consider momentum in mesh element.
Movement of water not calculated for mesh elements with depth of water below this value—only mass conservation is considered.
Velocity:
Mesh elements with water velocity below this value have velocity reset to zero in terms of momentum calculations.
Ignore rain falling on dry elements:
If checked, applies rainfall and evaporation only to wet elements in the 2D mesh.
Adjust bank levels based on adjacent element ground levels:
If selected, levels of bank sections lower than adjoining mesh elements are adjusted by the engine to match mesh element ground level.
Enabled by default.
Link 1D and 2D calculations at minor timestep:
Unchecked— 2D calculations performed at every run timestep.
Checked — 2D simulation engine performs calculations at a maximum of every minor timestep.
May help to reduce occurrence of oscillations at banks for some networks.
Includes settings used as part of the calculations.
Timestep Stability Control:
Ensures internal timestep used by 2D engine is within stability bounds given by CFL condition.
Valid below 1.
Maximum Velocity:
Threshold limiting velocities that can be achieved in an element in 2D simulation.
Inundation mapping depth threshold:
Used to determine the time to first inundation for mesh elements.
Reported as time (from start of simulation) water depth in mesh element first exceeds this threshold.
Steady state mode only available on CPU — not widely applied.
When Deactivate steady state areas option is checked, 2D engine checks if local steady state has been reached in each element of 2D zone.
Elements in 2D zone are put in sleep mode whenever steady state is reached.
Can specify threshold criteria to determine whether an element has reached a steady state.
Has the potential to speed up simulations, particularly in 2D river applications with large 2D zones and different flooded areas acting independently.
GPU cards can be used to accelerate 2D calculation speed for models with greater than 1,000 elements.
The more elements, the greater the benefit.
For large 2D models, consider example comparing CPU-only run, which takes around 2 hours, and GPU run, which takes around 5 minutes.
CUDA capable NVIDIA GPU card with compute capability 3.0 (Kepler family) or above can currently be used for 2D engine calculations.
Only speeds up 2D engine, but can also reduce load on CPU undertaking 1D engine calculations.
Time taken for simulation should be considered additive between 1D and 2D engine times.
On-premise default is to use the GPU card for 2D calculations, If suitable card is available.
Not all functionality is supported by the GPU.
With non-supported functionality in network (such as sediment transport), if Always or If suitable card is available selected, the simulation fails or a warning is displayed in the log.
For cloud, the default is to use the GPU card, If optimal for selected network.
Uses algorithm to determine whether quicker to run on GPU or CPU.
Can be overridden by selecting Never or Always.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.