View source for HPC Features Archive


=New Features Available to HPC (2017 release)= 
TUFLOW HPC’s solution scheme underwent extensive advanced development for the 2017 release. It now includes the majority of TUFLOW Classic features.
* The spatial accuracy was upgraded from 1st to 2nd order.
* It’s cell design was upgraded from a cell centered configuration, to a cell centre and face design. This is the same configuration as TUFLOW Classic. TUFLOW HPC now treats all thin and thick breakline topography modification inputs identical to TUFLOW Classic. 
* TUFLOW HPC is linked with TUFLOW’s 1D solver, ESTRY. It has the same advanced 2D/1D link functionality as TUFLOW Classic.
* TUFLOW HPC now supports all 1D and most 2D boundary condition types, including:
<ol>
<li> 1D and 2D QT, HQ and HT boundaries
<li> 2D SA and RF boundaries
<li> 1D/2D HX and SX boundaries
</ol>

In addition to the above mentioned TUFLOW Classic inclusions, TUFLOW HPC includes a handful of new features that are specific to it, and not applicable to TUFLOW Classic: 

'''CPU and GPU Execution Option'''<br>
Modellers can now specify whether they would like to run TUFLOW HPC models on CPU or GPU hardware, with the ability to run the model across several CPU cores or GPU cards for increased modelling speeds. CPU simulations can be done using a standard TUFLOW licence. The GPU Hardware Module is required in addition to a standard TUFLOW licence to run on GPU.<br>
<br>
<font color="blue"><tt>Solution Scheme </tt></font> <font color="red"><tt>== </tt></font><tt>HPC</tt>     <font color="green"><tt>   !Used to call the HPC solver. Classic is the default.</tt></font><br>
<font color="blue"><tt>Hardware </tt></font><font color="red"><tt>==</tt></font><tt> CPU or GPU </tt>	<font color="green"><tt>     !The hardware command instructs TUFLOW to run the HPC model on either a CPU or GPU processor.CPU is default.</tt></font><br>
<font color="blue"><tt>CPU Threads </tt></font><font color="red"><tt>== </tt></font><tt> 8	</tt>    <font color="green"><tt>    !This instructs TUFLOW to search for and run the model across four different core processors we run using CPU Hardware (i.e. This command does not apply to GPU). Default is 4. </tt></font><br>
<font color="blue"><tt>GPU Device IDs </tt></font><font color="red"><tt>== </tt></font><tt> 0, 1 </tt>	<font color="green"><tt>     !This command instructs TUFLOW to run the model on GPU Device 0 and GPU Device 1.</tt></font><br><br>
'''Adaptive Timestepping'''<br> 
TUFLOW HPC implements an adaptive timestep, meaning it changes over time, to meet the conditions of the model “Control Numbers” (see [[HPC Adaptive Timestepping | HPC Adaptive Timestepping]]). Using the "Control Number Factor ==" command, modellers can increase or decrease the HPC timestep. <br>
<br>
The model timestep can be reduced (underclocked) by applying a Control Number Factor less than 1, or increased (overclocked) by implementing a Control Number Factor greater than 1. Reducing the model timestep is likely to increase model stability and model run times, while increasing the model timestep is likely to decrease model stability and run times. <br>
<br>
Modellers can also define a minimum model timestep using the "<font color="blue"><tt>Timestep Minimum </tt></font> <font color="red"><tt>== </tt></font>" command or a fixed model timestep with the "<font color="blue"><tt>Control Number Factor </tt></font> <font color="red"><tt>== </tt></font><tt> 0</tt>" command. <br>

'''dt Map Output'''<br>
The dt map output (see [[HPC Output Files | HPC Output Files]]) provides a raster grid of the minimum timestep in each cell of the model. To produce the dt raster grid, the following command is required in the TCF file.<br>

"<font color="blue"><tt>Map Output Data Type </tt></font> <font color="red"><tt>== </tt></font><tt> dt</tt>"

=Features not yet supported in HPC=
Now TUFLOW HPC includes most TUFLOW Classic features it is easier to list the Classic features not yet included in HPC, instead of providing a full list outlining what HPC includes. The features below are currently not supported by TUFLOW HPC in the 2017 release, please note the later versions of HPC have added functionality and may support features listed below.<br>

'''Bed Resistance coefficients'''<br>
The Chezy and Fric bed resistance coefficients are not supported by HPC. Manning’s n is the only bed resistance coefficient currently supported by HPC.<br>
'''Map Outputs Data Types'''<br>
Map output data types not currently supported in HPC include:<br>
* UD (User Defined Output)<br>
* MB1 and MB2 (HPC is mass conserving and does not require these outputs)<br>
* RC (Route Categories)<br>
* n (Manning’s n values when using depth varying n values)<br>
* R (flow regime)<br>
* AP and WI (Atmospheric Pressure and Wind)<br>
'''Minimum Map Outputs'''<br>
Minimum value map outputs are not yet available in HPC.<br>
'''Read GIS Z Shape Route'''<br>
Evacuation route modelling (“<font color="blue"><tt>Read GIS Z Shape Route </tt></font> <font color="red"><tt>==</tt></font>”) is not yet supported in HPC. <br>
'''Read GIS Objects'''<br>
The “<font color="blue"><tt>Read GIS Objects</tt></font>” feature which is used to record the water level and simulation time when one or more receptors are triggered in the model is not available in the HPC solver.<br>
'''Reporting Locations, Longitudinal Profiles and Structure Groups'''<br>
Reporting Locations, Longitudinal Profiles and Structure Groups are not yet fully built into HPC. These features are targeted for the next major HPC update. <br>
'''Tracking of Plot Output Minimums and Maximums'''<br>
HPC now tracks the minimum and maximum values for the plot outputs at each time series output interval. This still differs to Classic which is able to track the minimum and maximum values at every timestep of the model. Therefore there may be differences in the reported minimum and maximum values of these two TUFLOW engines. The degree of difference may be dependent on the time series output interval of the HPC model.<br>
'''Traditional Flow Constrictions'''<br>
2d_fc layers are currently not supported by HPC. If running a model with a traditional 2d_fc layer, HPC should report Error 2320. <br>
Please note that layered flow constrictions (2d_lfcsh) are supported in HPC.<br>
'''Water Level (_H) outputs for PO lines'''<br>
HPC does not currently handle the _H (water level) output flag for the Plot Output feature. However, Plot Output points can still be used to produce a water level time series for a specified location.<br>
'''Weir Factors'''<br>
Weir Factors (WrF) which are used for adjusting and calibrating 2d weir flow are not yet available in the HPC engine.<br>
<br>
<br>
{{Tips Navigation
|uplink=[[ HPC_Modelling_Guidance | Back to HPC Modelling Guidance]]
}}