Tuflow - Recent changes [en]

TUFLOW Viewer

Teegan.Burke — Wed, 17 Jun 2026 02:40:45 GMT

← Older revision		Revision as of 12:40, 17 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	Two versions of the TUFLOW Viewer are available. ~~TUFLOW Viewer has been available since 2018. The new TUFLOW Viewer 2 was updated as part of the 2026.0.0 QGIS TUFLOW Plugin release, hence has been available since March 2026.~~		Two versions of the TUFLOW Viewer are available.

			<b>New TUFLOW Viewer 2:</b>
⚫	~~The~~ original TUFLOW Viewer replaces Crayfish and TUPLOT as the TUFLOW result viewer for <u>[[QGIS_Tips \| QGIS]]</u> (version 3.6 onwards). It uses the Mesh Data Abstraction Library (MDAL) available in QGIS to display and interact with TUFLOW map output results, and the TUFLOW results python library (the same library used by TUPLOT in earlier versions of QGIS) for viewing TUFLOW time series results.~~<br>~~

			* The new TUFLOW Viewer 2 was updated as part of the 2026.0.0 QGIS TUFLOW Plugin release, hence has been available since March 2026.
	<b>For all information ~~on TUFLOW Viewer 2~~, including switching from TUFLOW Viewer to TUFLOW Viewer 2, its functionality and the roadmap on outstanding features, refer to the <u>[https://docs.tuflow.com/qgis-tuflow-plugin/latest/tuflow-viewer/ TUFLOW Viewer Documentation]</u>. </b>		* <b>For all information, including switching from the original TUFLOW Viewer to the new TUFLOW Viewer 2, its functionality and the roadmap on outstanding features, refer to the <u>[https://docs.tuflow.com/qgis-tuflow-plugin/latest/tuflow-viewer/ TUFLOW Viewer Documentation]</u>.</b>

			Original TUFLOW Viewer:

			* TUFLOW Viewer has been available since 2018.
		⚫	* This following page documents the original TUFLOW Viewer, which replaces Crayfish and TUPLOT as the TUFLOW result viewer for <u>[[QGIS_Tips \| QGIS]]</u> (version 3.6 onwards). It uses the Mesh Data Abstraction Library (MDAL) available in QGIS to display and interact with TUFLOW map output results, and the TUFLOW results python library (the same library used by TUPLOT in earlier versions of QGIS) for viewing TUFLOW time series results.
	<br>		<br>
	__TOC__		__TOC__

TUFLOW Viewer

Anne.Kolega — Tue, 16 Jun 2026 23:00:01 GMT

← Older revision		Revision as of 09:00, 17 June 2026
(9 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			Two versions of the TUFLOW Viewer are available. TUFLOW Viewer has been available since 2018. The new TUFLOW Viewer 2 was updated as part of the 2026.0.0 QGIS TUFLOW Plugin release, hence has been available since March 2026.
⚫	TUFLOW Viewer replaces Crayfish and TUPLOT as the TUFLOW result viewer for <u>[[QGIS_Tips \| QGIS]]</u> (version 3.6 onwards). It uses the Mesh Data Abstraction Library (MDAL) available in QGIS to display and interact with TUFLOW map output results, and the TUFLOW results python library (the same library used by TUPLOT in earlier versions of QGIS) for viewing TUFLOW time series results.<br>

		⚫	The original TUFLOW Viewer replaces Crayfish and TUPLOT as the TUFLOW result viewer for <u>[[QGIS_Tips \| QGIS]]</u> (version 3.6 onwards). It uses the Mesh Data Abstraction Library (MDAL) available in QGIS to display and interact with TUFLOW map output results, and the TUFLOW results python library (the same library used by TUPLOT in earlier versions of QGIS) for viewing TUFLOW time series results.<br>
⚫	<b>~~The~~ TUFLOW Viewer ~~tool~~ ~~has~~ ~~been~~ ~~significantly~~ ~~updated~~ in ~~the~~ ~~2026.0.0~~ ~~QGIS~~ ~~TUFLOW~~ ~~Plugin~~ ~~release.~~ ~~Refer~~ to the <u>[https://docs.tuflow.com/qgis-tuflow-plugin/latest/tuflow-viewer/ TUFLOW Viewer Documentation]</u> ~~for more information~~. </b>

		⚫	<b>For all information on TUFLOW Viewer 2, including switching from TUFLOW Viewer to TUFLOW Viewer 2, its functionality and the roadmap on outstanding features, refer to the <u>[https://docs.tuflow.com/qgis-tuflow-plugin/latest/tuflow-viewer/ TUFLOW Viewer Documentation]</u>. </b>
	<br>		<br>
	__TOC__		__TOC__

DRAFT Direct Rainfall (Rain on Grid) Modelling Guidance

Teegan.Burke — Tue, 16 Jun 2026 05:29:54 GMT

What is the best approach for modelling buildings in rain on grid model?

Show changes

Quadtree and Sub-Grid Sampling FAQ

Teegan.Burke — Tue, 16 Jun 2026 01:14:00 GMT

What is best practice when applying Quadtree cell sizes within a channel?

← Older revision		Revision as of 11:14, 16 June 2026
(One intermediate revision by the same user not shown)
Line 6:		Line 6:

	=How coarse can the base cell size be for a Quadtree model with Sub-Grid Sampling (SGS)?=		=How coarse can the base cell size be for a Quadtree model with Sub-Grid Sampling (SGS)?=
	There are two answers to this question depending on your modelling objectives. For example, by doubling your base cell size, and not changing the Quadtree levels, you will be doubling the cell sizes throughout your model. Provided this doubling of cell sizes does not conflict with other objectives (remember, only one velocity is calculated per cell face, so a consequence of doubling cell size is to reduce the quality of velocity based outputs such as hazard), whether or not it is okay to increase the base cell size simply comes down to whether results convergence can be proven. By results convergence we mean you can increase (or decrease) your cell sizes without unacceptably changing the model results. If you do see a significant change in results that is considered unacceptable, then you need to possibly make your cell sizes smaller (not larger!). A well-designed model ~~mesh~~ is one where you can decrease cells sizes without seeing an unacceptable change in results. SGS will greatly help with achieving results convergence and very much increase your ability to use a coarser base cell size or coarsen up parts of your model.		There are two answers to this question depending on your modelling objectives. For example, by doubling your base cell size, and not changing the Quadtree levels, you will be doubling the cell sizes throughout your model. Provided this doubling of cell sizes does not conflict with other objectives (remember, only one velocity is calculated per cell face, so a consequence of doubling cell size is to reduce the quality of velocity based outputs such as hazard), whether or not it is okay to increase the base cell size simply comes down to whether results convergence can be proven. By results convergence we mean you can increase (or decrease) your cell sizes without unacceptably changing the model results. If you do see a significant change in results that is considered unacceptable, then you need to possibly make your cell sizes smaller (not larger!). A well-designed model grid is one where you can decrease cells sizes without seeing an unacceptable change in results. SGS will greatly help with achieving results convergence and very much increase your ability to use a coarser base cell size or coarsen up parts of your model.
	The second part of the answer is if you wish to coarsen up parts of your model but retain the same cell sizes in your focus area. To achieve this you can increase your base cell size to your largest cell size you wish to use, then add additional levels of nesting layers for your Quadtree ~~mesh~~ noting that the 2020-01 release of TUFLOW allows for up to 9 levels of nesting, so your smallest cell size can be (1/2)<sup>8</sup>, or 1/256, of your base cell size.		The second part of the answer is if you wish to coarsen up parts of your model but retain the same cell sizes in your focus area. To achieve this you can increase your base cell size to your largest cell size you wish to use, then add additional levels of nesting layers for your Quadtree grid noting that the 2020-01 release of TUFLOW allows for up to 9 levels of nesting, so your smallest cell size can be (1/2)<sup>8</sup>, or 1/256, of your base cell size.
	<br>		<br>

Line 45:		Line 45:

	=Should the same model using Quadtree with smaller cell count always be faster than HPC?=		=Should the same model using Quadtree with smaller cell count always be faster than HPC?=
	Not necessarily. By default, running a model with a single level Quadtree ~~mesh~~ identical to a HPC grid is always slower, on average 20%. Quadtree really starts to have major benefits once there is at least three levels of cell size and judicious refinement resulting in 80% of cell count reduction. ~~There~~ is ~~one~~ ~~major~~ ~~benefit~~ of ~~Quadtree~~ ~~regardless~~ in that in ~~nearly~~ ~~always~~ ~~has~~ a ~~much~~ ~~smaller~~ ~~GPU~~ ~~RAM~~ ~~memory~~ ~~footprint~~ ~~because~~ ~~unused~~ 2D ~~cells~~ ~~within~~ ~~the~~ ~~bounding~~ ~~rectangle~~ ~~used~~ by a ~~HPC~~ grid ~~are~~ ~~not~~ ~~stored~~ in ~~memory~~ ~~whereas~~ ~~for~~ a ~~grid~~ ~~they~~ ~~are~~.		Not necessarily. By default, running a model with a single level Quadtree grid identical to a HPC grid is always slower, on average 20%. Quadtree really starts to have major benefits once there is at least three levels of cell size and judicious refinement resulting in 80% of cell count reduction. The speed of a simulation is also affected by the adaptive timestepping - introducing cell sizes that are smaller in the refined Quadtree grid than those in the HPC model will require a smaller minimum timestep, which gets applied to the whole model. How a Quadtree grid interacts with hydraulic controls may also cause changes to the model’s adaptive timestepping.
	<br>		<br>

Line 73:		Line 73:

	=With SGS, can I have less cells across the main channel than is recommended for HPC without SGS?=		=With SGS, can I have less cells across the main channel than is recommended for HPC without SGS?=
	You can get accurate results with less 2D cells across the width of flow if you use SGS with a high resolution DEM or preferably a TIN that is based on accurate field surveys. The quality of the channel’s bathymetry is critical to the quality of the modelling, ideally the TIN would extend to dry ground if the data are available to avoid bumpy terrain data from the DEM along the edge of the TIN within the channel (this is even more so for concrete trapezoidal channels). Benchmarking to check similar results are achieved using a finer ~~mesh~~ is strongly recommended to demonstrate the coarser ~~mesh~~ is not affecting results.		You can get accurate results with less 2D cells across the width of flow if you use SGS with a high resolution DEM or preferably a TIN that is based on accurate field surveys. The quality of the channel’s bathymetry is critical to the quality of the modelling, ideally the TIN would extend to dry ground if the data are available to avoid bumpy terrain data from the DEM along the edge of the TIN within the channel (this is even more so for concrete trapezoidal channels). Benchmarking to check similar results are achieved using a finer grid resolution is strongly recommended to demonstrate the coarser grid resolution is not affecting results.
	<br>		<br>

Line 109:		Line 109:
	Where this behaviour is observed, a useful sensitivity test is to refine the channel so that a single Quadtree cell size is used across the channel bed and along the section of interest. The Quadtree transitions can then be moved outside the channel, for example onto the overbank or floodplain areas where the hydraulic gradients are less critical.		Where this behaviour is observed, a useful sensitivity test is to refine the channel so that a single Quadtree cell size is used across the channel bed and along the section of interest. The Quadtree transitions can then be moved outside the channel, for example onto the overbank or floodplain areas where the hydraulic gradients are less critical.

	This does not mean that every channel must use the finest cell size everywhere. However, for narrow channels, low flow conditions, bends, crossings, or locations where water level and velocity results are important, maintaining a consistent cell size within the channel can help avoid artificial changes in conveyance and improve results convergence. As always, the final cell size should be checked by benchmarking against a finer ~~mesh~~ to confirm that the adopted resolution is not adversely affecting the results.		This does not mean that every channel must use the finest cell size everywhere. However, for narrow channels, low flow conditions, bends, crossings, or locations where water level and velocity results are important, maintaining a consistent cell size within the channel can help avoid artificial changes in conveyance and improve results convergence. As always, the final cell size should be checked by benchmarking against a finer grid to confirm that the adopted resolution is not adversely affecting the results.

			= How does memory usage compare between Quadtree and HPC? =
	<br>
			A common benefit of Quadtree is that it nearly always has a much smaller GPU RAM memory footprint, when comparing a single level Quadtree grid to an identical HPC grid. This is due to Quadtree only storing a grid of active cells (within the code boundary) compared with HPC and Classic single fixed grid models, that use the domain’s bounding rectangle to allocate memory, which may include large areas of inactive (redundant) cells and consume memory.

			Judicious refinement and using larger cells in non-focus areas in Quadtree will decrease the number of active cells and therefore the RAM requirement. When using Quadtree, the .qcf command <font color="blue"><tt>Quadtree Mesh Processing Method </tt></font> <font color="red"><tt>==</tt></font><tt> Memory Efficient</tt> can reduce the amount of CPU RAM memory, although the model initialisation might take longer.

			= How do results compare between Quadtree and HPC? =
			The Quadtree and HPC solvers use the same fundamental solution scheme, though require slightly different code implementations to accommodate for the fact both solvers are applied to differing grid designs (HPC operating on a fixed grid, whereas Quadtree uses a grid of varying cell sizes). For example, slightly different code is required by the Quadtree solver for line geometry topography update (Read GIS Z Shape) cell selection rules, using a "spider web" approach, rather than the HPC solver's "cross-hair" approach.

			As a result of these subtle differences between the HPC single grid and Quadtree solvers, they produce near though not identical results if both are used for the same single grid (same cell size, orientation and extent).<br>

	{{Tips Navigation		{{Tips Navigation

TUFLOW Simulation Speed

Teegan.Burke — Mon, 15 Jun 2026 22:21:36 GMT

Common Questions Answered (FAQ)

@@ Line 29: / Line 29: @@
 ** The better the hardware, the faster TUFLOW model would run. To see how different hardware compares to each other, see <u>[[Hardware_Benchmarking_-_Results#CPU_Results | Hardware Benchmarking Results]]</u>.
 ** For more information on hardware specification, see <u>[[Hardware_Selection_Advice | Hardware Selection Advice]]</u>.<br>
 <br>

TUFLOW Example Models

ElizaCollison — Mon, 15 Jun 2026 05:26:37 GMT

Example Model Data

← Older revision		Revision as of 15:26, 15 June 2026
Line 4:		Line 4:
	=Example Model Data=		=Example Model Data=
	The model data is available for download from <u>https://downloads.tuflow.com/TUFLOW/Wiki_Example_Models/TUFLOW_Example_Model_Dataset.zip</u><br>		The model data is available for download from <u>https://downloads.tuflow.com/TUFLOW/Wiki_Example_Models/TUFLOW_Example_Model_Dataset.zip</u><br>
	The dataset only includes model input files. The models can be run to create simulation check and result files. Batch files (*.bat) for each of the example feature categories has been provided within the "runs" folder of the TUFLOW project. <br>		The dataset only includes model input files. The models can be run to create simulation check and result files. Batch files (.bat) (for windows) and shell scripts (sh) (for linux) for each of the example feature categories has been provided within the "runs" folder of the TUFLOW project. <br>

	If you are unfamiliar with using batch files, additional information explaining how to use them to execute multiple simulations is available here: <u>[[Run_TUFLOW_From_a_Batch-file\| Run TUFLOW From a Batch-file]]</u>.		If you are unfamiliar with using batch files, additional information explaining how to use them to execute multiple simulations is available here: <u>[[Run_TUFLOW_From_a_Batch-file\| Run TUFLOW From a Batch-file]]</u>.

			For Linux users, the shell script has been set up assuming TUFLOW was installed via the [https://docs.tuflow.com/classic-hpc/manual/2026.0/InstallTUFLOW-2.html#TUFLOWInstaller-4 Installer (.deb or .rpm)]

	=Example Model Catalogue=		=Example Model Catalogue=

Quadtree and Sub-Grid Sampling FAQ

Abrar.Alttahir — Fri, 12 Jun 2026 01:29:41 GMT

What is best practice when applying Quadtree cell sizes within a channel?

← Older revision		Revision as of 11:29, 12 June 2026
(One intermediate revision by the same user not shown)
Line 94:		Line 94:
	=How to decide between using SGS, Quadtree and 1D open channel?=		=How to decide between using SGS, Quadtree and 1D open channel?=
	The number of 2D cells across channel is critical. Based on the <u>[https://downloads.tuflow.com/_archive/Australian_Rainfall_Runoff_Project15_TwoDimensional_Modelling_DraftReport.pdf ARR 2D modelling guidelines]</u> the aim is to have 6 cells across the river, creek or drain (if not using SGS). However, use of SGS does allow use of a much fewer cells across a waterway whilst preserving the total conveyance of the waterway. The only downside of SGS is that if the velocity distribution across the waterway, or for example the super-elevation of the water surface around a bend, is important then sufficient number of cells is needed to accurately reproduce the velocity distribution or water level variation. Quadtree grid can be useful for this purpose.		The number of 2D cells across channel is critical. Based on the <u>[https://downloads.tuflow.com/_archive/Australian_Rainfall_Runoff_Project15_TwoDimensional_Modelling_DraftReport.pdf ARR 2D modelling guidelines]</u> the aim is to have 6 cells across the river, creek or drain (if not using SGS). However, use of SGS does allow use of a much fewer cells across a waterway whilst preserving the total conveyance of the waterway. The only downside of SGS is that if the velocity distribution across the waterway, or for example the super-elevation of the water surface around a bend, is important then sufficient number of cells is needed to accurately reproduce the velocity distribution or water level variation. Quadtree grid can be useful for this purpose.
	<br>

	=How can I convert 1D open channel into Quadtree?=		=How can I convert 1D open channel into Quadtree?=
Line 102:		Line 101:
	# Read the 2d_zsh line and points cross section inputs into the model using the "Read GIS Z Shape" command in the tgc file. <br>		# Read the 2d_zsh line and points cross section inputs into the model using the "Read GIS Z Shape" command in the tgc file. <br>
	# Read the 2d_zsh merge polygon into the model using the "Create TIN Zpts Write TIN" command in the tgc file.		# Read the 2d_zsh merge polygon into the model using the "Create TIN Zpts Write TIN" command in the tgc file.

			= What is best practice when applying Quadtree cell sizes within a channel? =
			It is generally recommended to use a consistent Quadtree cell size within a channel, particularly where the channel hydraulics are an important focus of the model results.

			Although SGS can preserve the channel conveyance using sub-grid elevation sampling, TUFLOW still calculates one velocity per cell face. If the Quadtree cell size changes within the channel bed, or across the active flow width of the channel, this can locally change the effective flow width represented by the 2D cells. In some cases this may produce recirculation, bumpy water levels, or inconsistent water level results between scenarios, even where the channel geometry and flow are similar.

			Where this behaviour is observed, a useful sensitivity test is to refine the channel so that a single Quadtree cell size is used across the channel bed and along the section of interest. The Quadtree transitions can then be moved outside the channel, for example onto the overbank or floodplain areas where the hydraulic gradients are less critical.

			This does not mean that every channel must use the finest cell size everywhere. However, for narrow channels, low flow conditions, bends, crossings, or locations where water level and velocity results are important, maintaining a consistent cell size within the channel can help avoid artificial changes in conveyance and improve results convergence. As always, the final cell size should be checked by benchmarking against a finer mesh to confirm that the adopted resolution is not adversely affecting the results.

	<br>		<br>

Tutorial M11 002 Results QGIS update V2 draft

Anne.Kolega — Fri, 12 Jun 2026 01:15:35 GMT

Method

← Older revision		Revision as of 11:15, 12 June 2026
(One intermediate revision by the same user not shown)
Line 6:		Line 6:
	Inspect water level and velocity outputs:		Inspect water level and velocity outputs:
	<ol>		<ol>
	<li>Open the ~~TUFLOW~~ ~~Viewer.~~		<li>Open the Map Outputs results, either:
			*Within the QGIS Browser Panel drag the following layers into the QGIS workspace, or
	<li>Select File > Load Results. Navigate to the '''M11_5m_002.tcf''' in the '''Module_11\TUFLOW\runs''' folder and open it.
			::* '''Module_11\TUFLOW\results\M10_5m_002.xmdf''' > loads the map output
	<li>When prompted to open result GIS layer, select 'Yes'.
			* In File Explorer, navigate to the files above and drag and drop them into the QGIS workspace.
	<li>~~Select~~ the 'Water Level' and 'Vector Velocity' output type in the Result Type panel. The resolution of the vector velocity is different between the 1D and 2D sections. The 1D section shows vectors at the water level lines (2d_WLL) every 2.5m, the 2D section shows vectors based on the 2D cell resolution, every 5m. The direction of the vectors shows water moving between the 1D and 2D domain.		<li>In the Layer Panel, click on '''M11_5m_002''' then in the Layer Styling panel, select the 'Water Level' and 'Vector Velocity' output type in the Result Type panel. The resolution of the vector velocity is different between the 1D and 2D sections. The 1D section shows vectors at the water level lines (2d_WLL) every 2.5m, the 2D section shows vectors based on the 2D cell resolution, every 5m. The direction of the vectors shows water moving between the 1D and 2D domain.
	<li>Use the Time Series tool to plot a time series of flow through the 1D bridge and weir at the downstream crossing. Select 'Flow' from the ~~result~~ ~~type~~ panel. Water is overtopping the bridge through the 1D weir: <br>		<li>Use the Time Series Plot tool to plot a time series of flow through the 1D bridge and weir at the downstream crossing. Select 'Flow' from the Data Types panel. Water is overtopping the bridge through the 1D weir: <br>
	<br>		<br>
	{{Video\|name=Animation_M11_002_Results_01a.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_002_Results_01a.mp4\|width=1231}}<br>
	<br>		<br>
	<li>Use the Time Series tool to plot a time series of flow through the 1D bridge at the upstream crossing. Select 'Flow' from the ~~result~~ ~~type~~ panel. Water is overtopping the bridge in 2D: <br>		<li>Use the Time Series Plot tool to plot a time series of flow through the 1D bridge at the upstream crossing. Select 'Flow' from the Data Types panel. Water is overtopping the bridge in 2D: <br>
	<br>		<br>
	{{Video\|name=Animation_M11_002_Results_02a.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_002_Results_02a.mp4\|width=1231}}<br>

Tutorial M11 001 Results QGIS

Anne.Kolega — Fri, 12 Jun 2026 01:11:28 GMT

Method

← Older revision		Revision as of 11:11, 12 June 2026
(2 intermediate revisions by the same user not shown)
Line 18:		Line 18:
	{{Video\|name=Animation_M11_001_Results_02b.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_001_Results_02b.mp4\|width=1231}}<br>
	<br>		<br>
	<li>Use the Plot Time Series tool to see the time series of the flow at the reporting location and open channel PLOT_L line. The reporting location shows the total flow across the line in both the 1D and 2D. The open channel line shows flow only ~~though~~ the 1D. <br>		<li>Use the Plot Time Series tool to see the time series of the flow at the reporting location and open channel PLOT_L line. The reporting location shows the total flow across the line in both the 1D and 2D. The open channel line shows flow only through the 1D. <br>
	<br>		<br>
	{{Video\|name=Animation_M11_001_Results_03b.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_001_Results_03b.mp4\|width=1231}}<br>

Tutorial M11 001 Results QGIS update V2 draft

Anne.Kolega — Fri, 12 Jun 2026 01:04:37 GMT

Method

← Older revision		Revision as of 11:04, 12 June 2026
(2 intermediate revisions by the same user not shown)
Line 8:		Line 8:
	<li>Open the Map Outputs and Time Series results, either:		<li>Open the Map Outputs and Time Series results, either:
	*Within the QGIS Browser Panel drag the following layers into the QGIS workspace, or		*Within the QGIS Browser Panel drag the following layers into the QGIS workspace, or
	::* '''~~Module_10~~\TUFLOW\results\~~M10_5m_001~~.xmdf''' > loads the map output		::* '''Module_11\TUFLOW\results\M11_5m_001.xmdf''' > loads the map output
	* In File Explorer, navigate to the files above and drag and drop them into the QGIS workspace.		* In File Explorer, navigate to the files above and drag and drop them into the QGIS workspace.
	<li>In the 'Layer' Panel, click on '''M11_5m_001''' and select the 'Depth' and 'Vector Velocity' output type in the 'Datasets' tab.<br>		<li>In the 'Layer' Panel, click on '''M11_5m_001''' and select the 'Depth' and 'Vector Velocity' output type in the 'Datasets' tab.<br>
Line 15:		Line 15:
	{{Video\|name=Animation_M11_001_Results_01b.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_001_Results_01b.mp4\|width=1231}}<br>
	<br>		<br>
	<li>Use the Profile Plot tool to see a long profile of water through the 1D open channel. Select 'Water Level', 'Max Water Level', 'Bed Level' and '~~Culverts and~~ Pipes' from the ~~Result~~ ~~Names~~ panel.		<li>Use the Profile Plot tool to see a long profile of water through the 1D open channel. Select 'Water Level', 'Max Water Level', 'Bed Level' and 'Pipes' from the Data Types panel.
	<li>Select a section of open channel by clicking on an upstream and downstream PLOT_L result by holding shift. If only one line is selected, the tool plots the entire open channel downstream of the selected line:<br>		<li>Select a section of open channel by clicking on an upstream and downstream PLOT_L result by holding shift. If only one line is selected, the tool plots the entire open channel downstream of the selected line:<br>
	<br>		<br>
	{{Video\|name=Animation_M11_001_Results_02b.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_001_Results_02b.mp4\|width=1231}}<br>
	<br>		<br>
	<li>Use the Time Series Plot tool to see the time series of the flow at the reporting location and open channel PLOT_L line. The reporting location shows the total flow across the line in both the 1D and 2D. The open channel line shows flow only ~~though~~ the 1D. <br>		<li>Use the Time Series Plot tool to see the time series of the flow at the reporting location and open channel PLOT_L line. The reporting location shows the total flow across the line in both the 1D and 2D. The open channel line shows flow only through the 1D. <br>
	<br>		<br>
	{{Video\|name=Animation_M11_001_Results_03b.mp4\|width=1231}}<br>		{{Video\|name=Animation_M11_001_Results_03b.mp4\|width=1231}}<br>