HPC Running and Converting Models - Revision history

Pavlina Monhartova: /* Running HPC on Multiple GPU Devices */

2025-06-18T04:14:21Z

Running HPC on Multiple GPU Devices

← Older revision		Revision as of 14:14, 18 June 2025
Line 19:		Line 19:
	= Running HPC on Multiple GPU Devices =		= Running HPC on Multiple GPU Devices =
	Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>		Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>
	If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''. (Note that the order may not match ~~your~~ expectations, ~~more on that in~~ [[Configure CUDA device selection]]) <br>		If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines Device Manager. Note that the order may not match the expectations, see <u>[[Configure CUDA device selection]]</u> for more information. <br>
	The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>		The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>
	Example below will run single simulation across the first and second GPU card (ID 0 and 1).		Example below will run single simulation across the first and second GPU card (ID 0 and 1).

Jaap.vandervelde at 02:17, 18 June 2025

2025-06-18T02:17:36Z

← Older revision		Revision as of 12:17, 18 June 2025
Line 19:		Line 19:
	= Running HPC on Multiple GPU Devices =		= Running HPC on Multiple GPU Devices =
	Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>		Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>
	If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''. (Note that the order may not match your expectations, more on that in [Configure CUDA device selection]) <br>		If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''. (Note that the order may not match your expectations, more on that in [[Configure CUDA device selection]]) <br>
	The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>		The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>
	Example below will run single simulation across the first and second GPU card (ID 0 and 1).		Example below will run single simulation across the first and second GPU card (ID 0 and 1).

Jaap.vandervelde: add reference back to Configure CUDA device selection

2025-06-18T02:17:18Z

add reference back to Configure CUDA device selection

← Older revision		Revision as of 12:17, 18 June 2025
Line 19:		Line 19:
	= Running HPC on Multiple GPU Devices =		= Running HPC on Multiple GPU Devices =
	Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>		Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>
	If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''.<br>		If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''. (Note that the order may not match your expectations, more on that in [Configure CUDA device selection]) <br>
	The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>		The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>
	Example below will run single simulation across the first and second GPU card (ID 0 and 1).		Example below will run single simulation across the first and second GPU card (ID 0 and 1).

Emilie Nielsen at 00:04, 23 September 2024

2024-09-23T00:04:55Z

← Older revision		Revision as of 10:04, 23 September 2024
Line 2:		Line 2:
	This page contains information about converting an existing TUFLOW Classic or GPU (pre 2017 HPC release) model to a format that can be run using the TUFLOW HPC engine. This page provides a quick summary for experienced TUFLOW users to use as a reference point for updating their models. It is recommended that less experienced TUFLOW users refer to our <u>[[Tutorial_Introduction \|TUFLOW Tutorial Modules]]</u> for greater support and guidance on creating a HPC model.<br>		This page contains information about converting an existing TUFLOW Classic or GPU (pre 2017 HPC release) model to a format that can be run using the TUFLOW HPC engine. This page provides a quick summary for experienced TUFLOW users to use as a reference point for updating their models. It is recommended that less experienced TUFLOW users refer to our <u>[[Tutorial_Introduction \|TUFLOW Tutorial Modules]]</u> for greater support and guidance on creating a HPC model.<br>

	To convert an existing TUFLOW Classic or GPU Model to run on HPC, an update to the TUFLOW Control File (TCF) is needed. Some features from TUFLOW Classic that are not currently supported in HPC, may prevent the HPC model running successfully. To find out more about unsupported features in HPC, refer to ~~Section 10.1.5 in~~ the <u>[https://~~downloads~~.tuflow.com/~~_archive~~/~~TUFLOW~~/~~Releases~~/~~2018-03/TUFLOW%20Manual.2018-03.pdf~~ TUFLOW Manual ~~(2018)~~]</u>. <br>		To convert an existing TUFLOW Classic or GPU Model to run on HPC, an update to the TUFLOW Control File (TCF) is needed. Some features from TUFLOW Classic that are not currently supported in HPC, may prevent the HPC model running successfully. To find out more about unsupported features in HPC, refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>. <br>

	= Converting TUFLOW Classic to HPC (TCF Updates) =		= Converting TUFLOW Classic to HPC (TCF Updates) =

Chris Huxley: /* Running HPC on Multiple GPU Devices */

2024-08-23T00:58:51Z

Running HPC on Multiple GPU Devices

← Older revision		Revision as of 10:58, 23 August 2024
Line 20:		Line 20:
	Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>		Much like HPC can be run across multiple CPU processors, HPC can be run across multiple GPU cards. Models can also be instructed to run on a specific GPU card.<br>
	If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''.<br>		If a machine only has a single GPU card, the GPU Device ID should be 0, this is a default. If a second GPU card was added, the Device ID would be 1 and so on. The GPU IDs can be checked by reviewing the machines ''Device Manager''.<br>
	The most common is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>		The most common method is to specify the GPU card ID in the batch file / command line by using the -pu<id> argument.<br>
	Example below will run single simulation across the first and second GPU card (ID 0 and 1).		Example below will run single simulation across the first and second GPU card (ID 0 and 1).
	<pre>"TUFLOW_iSP_w64.exe" -pu0 -pu1 "M01_5m_001.tcf"</pre>		<pre>"TUFLOW_iSP_w64.exe" -pu0 -pu1 "M01_5m_001.tcf"</pre>

Abigail.lillo: /* Introduction */

2024-01-29T01:19:25Z

Introduction

← Older revision		Revision as of 11:19, 29 January 2024
Line 2:		Line 2:
	This page contains information about converting an existing TUFLOW Classic or GPU (pre 2017 HPC release) model to a format that can be run using the TUFLOW HPC engine. This page provides a quick summary for experienced TUFLOW users to use as a reference point for updating their models. It is recommended that less experienced TUFLOW users refer to our <u>[[Tutorial_Introduction \|TUFLOW Tutorial Modules]]</u> for greater support and guidance on creating a HPC model.<br>		This page contains information about converting an existing TUFLOW Classic or GPU (pre 2017 HPC release) model to a format that can be run using the TUFLOW HPC engine. This page provides a quick summary for experienced TUFLOW users to use as a reference point for updating their models. It is recommended that less experienced TUFLOW users refer to our <u>[[Tutorial_Introduction \|TUFLOW Tutorial Modules]]</u> for greater support and guidance on creating a HPC model.<br>

	To convert an existing TUFLOW Classic or GPU Model to run on HPC, an update to the TUFLOW Control File (TCF) is needed. Some features from TUFLOW Classic that are not currently supported in HPC, may prevent the HPC model running successfully. To find out more about unsupported features in HPC ~~be sure~~ to ~~review~~ the <u>[https://tuflow.com/~~Download~~/TUFLOW/Releases/~~2017~~-09/TUFLOW%~~20Release%20Notes~~.~~2017~~-09.pdf TUFLOW ~~2017-09 Release~~ ~~Notes~~]</u> ~~or the <u>[[HPC Features \| HPC Features Wiki Page]]</u>.~~<br>		To convert an existing TUFLOW Classic or GPU Model to run on HPC, an update to the TUFLOW Control File (TCF) is needed. Some features from TUFLOW Classic that are not currently supported in HPC, may prevent the HPC model running successfully. To find out more about unsupported features in HPC, refer to Section 10.1.5 in the <u>[https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual (2018)]</u>. <br>

	= Converting TUFLOW Classic to HPC (TCF Updates) =		= Converting TUFLOW Classic to HPC (TCF Updates) =

Jaap.vandervelde: Brought partially correct command line option description in line with tcf command description (which was correct)

2023-12-11T01:54:07Z

Brought partially correct command line option description in line with tcf command description (which was correct)

← Older revision		Revision as of 11:54, 11 December 2023
Line 56:		Line 56:
	Other useful batch file switches include:<br>		Other useful batch file switches include:<br>
	<font color="blue"><tt>-nt <number_of_threads> </tt></font>: This switch is used to set the number of CPU threads used for CPU mode simulations.<br>		<font color="blue"><tt>-nt <number_of_threads> </tt></font>: This switch is used to set the number of CPU threads used for CPU mode simulations.<br>
	<font color="blue"><tt>-pu <GPU Device IDs> </tt></font>: This switch is used to ~~select~~ the number of GPU ~~cards~~ ~~that~~ ~~TUFLOW~~ ~~uses~~.<br>		<font color="blue"><tt>-pu <GPU Device IDs> </tt></font>: This switch is used to set the number of GPU devices and which devices to use.<br>
	An example of how this would be implemented into a simple batch file for CPU and GPU are shown below.<br>		An example of how this would be implemented into a simple batch file for CPU and GPU are shown below.<br>

ElizaCollison: /* HPC Scenarios and Updating the Batch File */

2023-01-08T23:48:44Z

HPC Scenarios and Updating the Batch File

← Older revision		Revision as of 09:48, 9 January 2023
Line 52:		Line 52:
	If using the above Scenario Logic, the modeller must include a scenario call in the batch file.<br>		If using the above Scenario Logic, the modeller must include a scenario call in the batch file.<br>
	<font color="blue"><tt>-s1 <Hardware Type> </tt></font><br>		<font color="blue"><tt>-s1 <Hardware Type> </tt></font><br>
	If you are unfamiliar with using Scenario Logic, please refer to <u>[[~~Tutorial_Module05~~ \|Tutorial Module 05]]</u>.<br>		If you are unfamiliar with using Scenario Logic, please refer to <u>[[Tutorial_M08 \|Tutorial Module 08]]</u>.<br>

	Other useful batch file switches include:<br>		Other useful batch file switches include:<br>

ElizaCollison: /* Introduction */

2022-09-29T00:20:25Z

Introduction

← Older revision		Revision as of 10:20, 29 September 2022
Line 1:		Line 1:
	= Introduction =		= Introduction =
	This page contains information about converting an existing TUFLOW Classic or GPU (pre 2017 HPC release) model to a format that can be run using the TUFLOW HPC engine. This page provides a quick summary for experienced TUFLOW users to use as a reference point for updating their models. It is recommended that less experienced TUFLOW users refer to our <u>[[~~Tutorial_Model~~ \|TUFLOW Tutorial Modules]]</u> for greater support and guidance on creating a HPC model.<br>		This page contains information about converting an existing TUFLOW Classic or GPU (pre 2017 HPC release) model to a format that can be run using the TUFLOW HPC engine. This page provides a quick summary for experienced TUFLOW users to use as a reference point for updating their models. It is recommended that less experienced TUFLOW users refer to our <u>[[Tutorial_Introduction \|TUFLOW Tutorial Modules]]</u> for greater support and guidance on creating a HPC model.<br>

	To convert an existing TUFLOW Classic or GPU Model to run on HPC, an update to the TUFLOW Control File (TCF) is needed. Some features from TUFLOW Classic that are not currently supported in HPC, may prevent the HPC model running successfully. To find out more about unsupported features in HPC be sure to review the <u>[https://tuflow.com/Download/TUFLOW/Releases/2017-09/TUFLOW%20Release%20Notes.2017-09.pdf TUFLOW 2017-09 Release Notes]</u> or the <u>[[HPC Features \| HPC Features Wiki Page]]</u>.<br>		To convert an existing TUFLOW Classic or GPU Model to run on HPC, an update to the TUFLOW Control File (TCF) is needed. Some features from TUFLOW Classic that are not currently supported in HPC, may prevent the HPC model running successfully. To find out more about unsupported features in HPC be sure to review the <u>[https://tuflow.com/Download/TUFLOW/Releases/2017-09/TUFLOW%20Release%20Notes.2017-09.pdf TUFLOW 2017-09 Release Notes]</u> or the <u>[[HPC Features \| HPC Features Wiki Page]]</u>.<br>

Chris Huxley: /* HPC Scenarios and Updating the Batch File */

2022-05-30T05:30:52Z

HPC Scenarios and Updating the Batch File

← Older revision		Revision as of 15:30, 30 May 2022
Line 57:		Line 57:
	<font color="blue"><tt>-nt <number_of_threads> </tt></font>: This switch is used to set the number of CPU threads used for CPU mode simulations.<br>		<font color="blue"><tt>-nt <number_of_threads> </tt></font>: This switch is used to set the number of CPU threads used for CPU mode simulations.<br>
	<font color="blue"><tt>-pu <GPU Device IDs> </tt></font>: This switch is used to select the number of GPU cards that TUFLOW uses.<br>		<font color="blue"><tt>-pu <GPU Device IDs> </tt></font>: This switch is used to select the number of GPU cards that TUFLOW uses.<br>
⚫	<br>
	<br>
⚫	{{Tips Navigation
⚫	\|uplink=[[ HPC_Modelling_Guidance \| Back to HPC Modelling Guidance]]
⚫	}}
	An example of how this would be implemented into a simple batch file for CPU and GPU are shown below.<br>		An example of how this would be implemented into a simple batch file for CPU and GPU are shown below.<br>

Line 72:		Line 67:
	This example will run TUFLOW HPC on GPU using 2 GPU cards.<br>		This example will run TUFLOW HPC on GPU using 2 GPU cards.<br>
	<br>		<br>
		⚫	<br>
		⚫	{{Tips Navigation
		⚫	\|uplink=[[ HPC_Modelling_Guidance \| Back to HPC Modelling Guidance]]
		⚫	}}