Linux Install - Revision history

Tor.veimo: Grammar

2026-03-30T03:19:17Z

Grammar

← Older revision		Revision as of 13:19, 30 March 2026
Line 62:		Line 62:

	== Notes on ULIMIT ==		== Notes on ULIMIT ==
	The stack size limit is set to the highest allowed limit specified ~~(usually unlimited)~~ in the shell that TUFLOW is run in. Thus it's no longer necessary to set the limit in a launcher shell script. This behaviour can be disabled by passing the <code>-nua</code> command line flag, causing TUFLOW to revert to the old behaviour.		The stack size limit is set to the highest allowed limit specified in the shell that TUFLOW is run in (usually unlimited). Thus it's no longer necessary to set the limit in a launcher shell script. This behaviour can be disabled by passing the <code>-nua</code> command line flag, causing TUFLOW to revert to the old behaviour.

	== Return to Home Page ==		== Return to Home Page ==

Tor.veimo: /* Notes on ULIMIT */

2026-03-30T03:08:45Z

Notes on ULIMIT

← Older revision		Revision as of 13:08, 30 March 2026
Line 62:		Line 62:

	== Notes on ULIMIT ==		== Notes on ULIMIT ==
	~~We now set the~~ stack size limit to the highest allowed ~~ULIMIT~~ specified (usually unlimited) in the shell that TUFLOW is run in. Thus it's no longer necessary to set the limit in a launcher shell script. ~~You~~ can ~~disable~~ ~~this behaviour~~ by passing the <code>-nua</code> command line flag, causing TUFLOW to revert to the old behaviour.		The stack size limit is set to the highest allowed limit specified (usually unlimited) in the shell that TUFLOW is run in. Thus it's no longer necessary to set the limit in a launcher shell script. This behaviour can be disabled by passing the <code>-nua</code> command line flag, causing TUFLOW to revert to the old behaviour.

	== Return to Home Page ==		== Return to Home Page ==

Tor.veimo: Added section about setting ulimit

2026-03-30T03:03:56Z

Added section about setting ulimit

← Older revision		Revision as of 13:03, 30 March 2026
Line 60:		Line 60:
	chmod +x run_model.sh		chmod +x run_model.sh
	</syntaxhighlight>		</syntaxhighlight>

			== Notes on ULIMIT ==
			We now set the stack size limit to the highest allowed ULIMIT specified (usually unlimited) in the shell that TUFLOW is run in. Thus it's no longer necessary to set the limit in a launcher shell script. You can disable this behaviour by passing the <code>-nua</code> command line flag, causing TUFLOW to revert to the old behaviour.

	== Return to Home Page ==		== Return to Home Page ==

Jaap.vandervelde: Jaap.vandervelde moved page Linux Install Draft to Linux Install without leaving a redirect: Publishing Linux install Draft

2026-03-29T22:39:22Z

Jaap.vandervelde moved page Linux Install Draft to Linux Install without leaving a redirect: Publishing Linux install Draft

← Older revision		Revision as of 08:39, 30 March 2026
(No difference)

Jaap.vandervelde: spelling

2026-03-27T08:04:25Z

spelling

← Older revision		Revision as of 18:04, 27 March 2026
Line 44:		Line 44:
	''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''		''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''

	== <span>Notes ~~For~~ Running TUFLOW Under WSL</span> ==		== <span>Notes for Running TUFLOW Under WSL</span> ==
	If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that work in WSL:		If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that work in WSL:
	export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH		export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH
	In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by the Microsoft Windows driver.		In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by the Microsoft Windows driver.

	== Running A Model ==		== Running a Model ==
	For either Linux distribution TUFLOW can be run by calling <code>tuflow-2026.0-isp</code> (this example would the currently installed patch for version 2026.0 and single precision) and by passing it a configuration file name:<syntaxhighlight lang="bash">		For either Linux distribution TUFLOW can be run by calling <code>tuflow-2026.0-isp</code> (this example would the currently installed patch for version 2026.0 and single precision) and by passing it a configuration file name:<syntaxhighlight lang="bash">
	tuflow-2026.0-isp my_run.tcf		tuflow-2026.0-isp my_run.tcf
Line 61:		Line 61:
	</syntaxhighlight>		</syntaxhighlight>

	== Return To Home Page ==		== Return to Home Page ==
	Return to [[Main_Page \| Wiki Home Page]].		Return to [[Main_Page \| Wiki Home Page]].

Jaap.vandervelde: various minor corrections, match other wiki

2026-03-27T08:03:21Z

various minor corrections, match other wiki

← Older revision		Revision as of 18:03, 27 March 2026
Line 5:		Line 5:

	== Codemeter Configuration ==		== Codemeter Configuration ==
	To ~~license~~ TUFLOW on Linux install and configure CodeMeter User Runtime Package for Linux (.rpm or .deb options are available) https://www.wibu.com/support/user/user-software.html.		To provide licenses to TUFLOW on Linux install and configure the CodeMeter User Runtime Package for Linux (.rpm or .deb options are available) https://www.wibu.com/support/user/user-software.html.

	* If using a hardware based usb dongle (either network or local licenses) please follow the instructions within [[Installing_Wibu_CodeMeter_Linux \| Installing Wibu Codemeter Linux]].		* If using a hardware based usb dongle (either network or local licenses) please follow the instructions within [[Installing_Wibu_CodeMeter_Linux \| Installing Wibu Codemeter Linux]].
Line 44:		Line 44:
	''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''		''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''

	== <span>Notes For Running ~~Linux~~ Under WSL</span> ==		== <span>Notes For Running TUFLOW Under WSL</span> ==
	If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that ~~works~~ in WSL:		If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that work in WSL:
	export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH		export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH
	In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by the Microsoft Windows driver.		In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by the Microsoft Windows driver.

Jaap.vandervelde: a few minor corrections, and reformatting of code examples

2026-03-27T07:47:58Z

a few minor corrections, and reformatting of code examples

← Older revision		Revision as of 17:47, 27 March 2026
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	TUFLOW is installed on Linux using the <code>.rpm</code> and <code>.deb</code> installer packages, which can be [https://www.tuflow.com/downloads/#tuflow downloaded here]. There's also a tar.gz archive which can be ~~downloaded~~ ~~from~~ the ~~same~~ ~~location~~.		TUFLOW is installed on Linux using the <code>.rpm</code> and <code>.deb</code> installer packages, which can be [https://www.tuflow.com/downloads/#tuflow downloaded here]. There's also a tar.gz archive available from the same location, which can serve as a portable application, similar to the .zip archive available for Windows.

	The installers have been tested on Rocky Linux 9 and Ubuntu 22.04, but should work on other modern Red Hat and Debian distributions.		The installers have been tested on Rocky Linux 9 and Ubuntu 22.04, but should work on other modern Red Hat and Debian distributions.
Line 13:		Line 13:
	TUFLOW uses a year.minor.patch versioning convention as follows.		TUFLOW uses a year.minor.patch versioning convention as follows.

	* The year corresponds to the major version number e.g. 2026.0.0. Major releases are the only releases that will admit the possibility of breaking changes ~~(changing~~ in defaults or features that may change model results between versions). There is one major release per year		* The year corresponds to the major version number e.g. 2026.0.0. Major releases are the only releases that will admit the possibility of breaking changes, which are changes in defaults or features that may change model results between versions. There is one major release per year

	* Minor releases contain new features and bug fixes, but no breaking changes and increment the minor version number, e.g. 2026.1.0		* Minor releases contain new features and bug fixes, but no breaking changes and increment the minor version number, e.g. 2026.1.0
Line 19:		Line 19:

	== RPM Install ==		== RPM Install ==
	<ol>		<ul>
	<li> Download the <code>.rpm</code> for the specific TUFLOW build from https://www.tuflow.com/downloads/#tuflow		<li> Download the <code>.rpm</code> for the specific TUFLOW build from https://www.tuflow.com/downloads/#tuflow
	<li> Save the <code>.rpm</code> locally. A common location is the home folder for the current user <code>~/</code>		<li> Save the <code>.rpm</code> locally. A common location is the home folder for the current user <code>~/</code>
	<li> Run the preferred installation command. For example, if installing the TUFLOW 2026.0.0 release:<~~/li~~>		<li> Run the preferred installation command. For example, if installing the TUFLOW 2026.0.0 release:<syntaxhighlight lang="bash">
	sudo ~~rpm~~ ~~-ivh~~ ~/tuflow-2026.0-2026.0.0-1.~~x86_64~~.rpm		sudo dnf install ~/tuflow-2026.0-2026.0.0-1.x86_x64.rpm
			</syntaxhighlight></li></ul>
	or
		⚫	<ul>
	sudo yum install ~/tuflow-2026.0-2026.0.0-1.x86_64.rpm.
		⚫	<li>This installs a version-specific copy of the TUFLOW binaries and libraries under <code>/opt/tuflow/<version>/bin</code> and <code>/opt/tuflow/<version>/lib</code>. A symbolic link to the executable is created in <code>/usr/bin</code>, allowing the required version to be run with a versioned shortcut, e.g. <code>tuflow-2026.0-isp</code>.
	</ol>
		⚫	<li>There is also a launcher script in <code>/opt/tuflow/tuflow-<version>/bin/tuflow-<version>-idp.sh</code> for use cases where some environment variables needs to be set before execution. If you need to edit these, we recommend copying these into <code>/usr/local/bin</code>, as they will be overwritten if a patch release is installed.
⚫	<ol>
		⚫	<li>To uninstall run the preferred uninstaller command. For example:<syntaxhighlight lang="bash">
⚫	<li>This installs a version-specific copy of the TUFLOW binaries and libraries under <code>/opt/tuflow/<version>/bin</code> and <code>/opt/tuflow/<version>/lib</code>. ~~The~~ executable is ~~symlinked~~ to <code>/usr/bin</code>, allowing the required version to be run ~~directly~~ ~~from~~ ~~the~~ ~~command~~ ~~line~~.
		⚫	sudo dnf remove tuflow-2026.0
⚫	<li>There is also a launcher script in <code>/opt/tuflow/tuflow-<version>/bin/tuflow-<version>-idp.sh</code> for use cases where some environment variables needs to be set before execution. If you need to edit these, we recommend copying these into /usr/local/bin, as they will be overwritten if a patch release is installed.
		⚫	</syntaxhighlight></li><li>To return a list of previously installed versions and review the correct uninstall version use <code>dnf list installed</code>'', or <code>dnf list installed 'tuflow*'</code>''</li></ul>''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''
⚫	<li>To uninstall run the preferred uninstaller command. For example:<~~/li~~>
	sudo rpm -e tuflow-2026.0-2026.0.0-1.x86_64
	or
⚫	sudo ~~yum~~ remove tuflow-2026.0~~-2026.0.0-1.x86_64~~
	To return a list of previously installed versions and review the correct uninstall version run:
	rpm -qa \| grep tuflow
	or
	yum list installed \| grep tuflow
⚫	</ol>''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''

	== DEB Install ==		== DEB Install ==
Line 44:		Line 36:

	To install:		To install:
	sudo apt~~-get~~ install ./tuflow-2026.0_2026.0.0-1_amd64.deb		sudo apt install ./tuflow-2026.0_2026.0.0-1_amd64.deb

	To uninstall:		To uninstall:
Line 55:		Line 47:
	If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that works in WSL:		If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that works in WSL:
	export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH		export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH
	In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by Microsoft Windows.		In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by the Microsoft Windows driver.

	== Running A Model ==		== Running A Model ==
	For either Linux distribution TUFLOW can be run by calling <code>tuflow-2026.0-isp</code> (~~replace~~ ~~with~~ the ~~required~~ version and precision) or by passing it a configuration file name:		For either Linux distribution TUFLOW can be run by calling <code>tuflow-2026.0-isp</code> (this example would the currently installed patch for version 2026.0 and single precision) and by passing it a configuration file name:<syntaxhighlight lang="bash">

	tuflow-2026.0-isp my_run.tcf		tuflow-2026.0-isp my_run.tcf
		⚫	</syntaxhighlight>Model-specific commands such as the <code>export OMP_NUM_THREADS</code> environment variable can either be added via the command line, or in your own custom run script that calls the configuration file name, for example ''<code>run_model.sh</code>'':<syntaxhighlight lang="bash">

			#!/bin/bash
⚫	Model-specific commands such as the <code>export OMP_NUM_THREADS</code> environment variable can either be added via the command line, or in your own custom run script that calls the configuration file name, for example run_model.sh:
		⚫	export OMP_NUM_THREADS=8

	<nowiki>#</nowiki>!/bin/bash
⚫	export OMP_NUM_THREADS=8
	tuflow-2026.0-idp my_run.tfc		tuflow-2026.0-idp my_run.tfc

	Once saved the script ~~'run_model.sh'~~ will need to be configured to run as an executable as follows:		</syntaxhighlight>Once saved the script will need to be configured to run as an executable as follows:<syntaxhighlight lang="bash">
	chmod +x run_model.sh		chmod +x run_model.sh
			</syntaxhighlight>

	== Return To Home Page ==		== Return To Home Page ==

Tor.veimo at 07:23, 27 March 2026

2026-03-27T07:23:19Z

← Older revision		Revision as of 17:23, 27 March 2026
Line 28:		Line 28:
	</ol>		</ol>
	<ol>		<ol>
	<li ~~value="4"~~>This installs a version-specific copy of the TUFLOW binaries and libraries under <code>/opt/tuflow/<version>/bin</code> and <code>/opt/tuflow/<version>/lib</code>. The executable is symlinked to <code>/usr/bin</code>, allowing the required version to be run directly from the command line. There is also a launcher script in <code>/opt/tuflow/tuflow-<version>/bin/tuflow-<version>-idp.sh (or -isp for single precision) that one cane use in case some environment variables needs to be set before execution. We recommend copying these launch scripts into /usr/local/bin if you need to do modifications, as the they might otherwise be overwritten if a patch release is installed.		<li>This installs a version-specific copy of the TUFLOW binaries and libraries under <code>/opt/tuflow/<version>/bin</code> and <code>/opt/tuflow/<version>/lib</code>. The executable is symlinked to <code>/usr/bin</code>, allowing the required version to be run directly from the command line.
			<li>There is also a launcher script in <code>/opt/tuflow/tuflow-<version>/bin/tuflow-<version>-idp.sh</code> for use cases where some environment variables needs to be set before execution. If you need to edit these, we recommend copying these into /usr/local/bin, as they will be overwritten if a patch release is installed.
	<li>To uninstall run the preferred uninstaller command. For example:</li>		<li>To uninstall run the preferred uninstaller command. For example:</li>
	sudo rpm -e tuflow-2026.0-2026.0.0-1.x86_64		sudo rpm -e tuflow-2026.0-2026.0.0-1.x86_64

Tor.veimo: Installation instructions for TUFLOW on Linux

2026-03-27T07:10:56Z

Installation instructions for TUFLOW on Linux

New page

== Introduction ==
TUFLOW is installed on Linux using the <code>.rpm</code> and <code>.deb</code> installer packages, which can be [https://www.tuflow.com/downloads/#tuflow downloaded here]. There's also a tar.gz archive which can be downloaded from the same location.

The installers have been tested on Rocky Linux 9 and Ubuntu 22.04, but should work on other modern Red Hat and Debian distributions.

== Codemeter Configuration ==
To license TUFLOW on Linux install and configure CodeMeter User Runtime Package for Linux (.rpm or .deb options are available) https://www.wibu.com/support/user/user-software.html.

* If using a hardware based usb dongle (either network or local licenses) please follow the instructions within [[Installing_Wibu_CodeMeter_Linux | Installing Wibu Codemeter Linux]].
* If using a software lock (either network or local licenses please follow the instructions within [[WIBU_Software_Licence_Linux | Wibu Software License Linux]].

== TUFLOW Versioning ==
TUFLOW uses a year.minor.patch versioning convention as follows.

* The year corresponds to the major version number e.g. 2026.0.0. Major releases are the only releases that will admit the possibility of breaking changes (changing in defaults or features that may change model results between versions). There is one major release per year

* Minor releases contain new features and bug fixes, but no breaking changes and increment the minor version number, e.g. 2026.1.0
* Patch releases are bug fixes only and increment the patch version number, e.g. 2026.0.1

== RPM Install ==
<ol>
<li> Download the <code>.rpm</code> for the specific TUFLOW build from https://www.tuflow.com/downloads/#tuflow
<li> Save the <code>.rpm</code> locally. A common location is the home folder for the current user <code>~/</code>
<li> Run the preferred installation command. For example, if installing the TUFLOW 2026.0.0 release:</li>
sudo rpm -ivh ~/tuflow-2026.0-2026.0.0-1.x86_64.rpm
or
sudo yum install ~/tuflow-2026.0-2026.0.0-1.x86_64.rpm.
</ol>
<ol>
<li value="4">This installs a version-specific copy of the TUFLOW binaries and libraries under <code>/opt/tuflow/<version>/bin</code> and <code>/opt/tuflow/<version>/lib</code>. The executable is symlinked to <code>/usr/bin</code>, allowing the required version to be run directly from the command line. There is also a launcher script in <code>/opt/tuflow/tuflow-<version>/bin/tuflow-<version>-idp.sh (or -isp for single precision) that one cane use in case some environment variables needs to be set before execution. We recommend copying these launch scripts into /usr/local/bin if you need to do modifications, as the they might otherwise be overwritten if a patch release is installed.
<li>To uninstall run the preferred uninstaller command. For example:</li>
sudo rpm -e tuflow-2026.0-2026.0.0-1.x86_64
or
sudo yum remove tuflow-2026.0-2026.0.0-1.x86_64
To return a list of previously installed versions and review the correct uninstall version run:
rpm -qa | grep tuflow
or
yum list installed | grep tuflow
</ol>''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''

== DEB Install ==
The process for <code>.deb</code> is essentially the same as the <code>.rpm</code> steps 2-5. For steps 3 and 5, the install and uninstall command examples below are for Debian derivatives. For example (assuming TUFLOW 2026.0.0, modify for the specific version required):

To install:
sudo apt-get install ./tuflow-2026.0_2026.0.0-1_amd64.deb

To uninstall:
sudo apt remove tuflow-2026.0
If unsure about which versions you have previously installed you can return a list of all the installed versions via:
apt list --installed | grep tuflow
''Note: Major and minor releases are installed with a new directory under <code>/opt/tuflow</code>. For example, TUFLOW 2026.0.0 is installed under <code>/opt/tuflow/tuflow-2026.0</code>. Patch releases overwrite the existing installation that shares the same major and minor release number. For example, TUFLOW 2026.0.1 will update 2026.0.0 if present.''

== <span>Notes For Running Linux Under WSL</span> ==
If you are running a Linux installation with Microsoft Windows under WSL (Windows Subsystem for Linux), things should run as expected. If you want to use NVIDIA hardware with CUDA support with TUFLOW under WSL, you need to add the correct folder to the LD_LIBRARY_PATH environment variable, so that TUFLOW can find the correct CUDA shared libraries that works in WSL:
export LD_LIBRARY_PATH=/usr/lib/wsl/lib:$LD_LIBRARY_PATH
In that folder there's a utility <code>/usr/lib/wsl/lib/nvidia-smi</code> which will indicate if the Linux installation can connect to the NVIDIA hardware otherwise managed by Microsoft Windows.

== Running A Model ==
For either Linux distribution TUFLOW can be run by calling <code>tuflow-2026.0-isp</code> (replace with the required version and precision) or by passing it a configuration file name:

tuflow-2026.0-isp my_run.tcf

Model-specific commands such as the <code>export OMP_NUM_THREADS</code> environment variable can either be added via the command line, or in your own custom run script that calls the configuration file name, for example run_model.sh:

<nowiki>#</nowiki>!/bin/bash
export OMP_NUM_THREADS=8
tuflow-2026.0-idp my_run.tfc

Once saved the script 'run_model.sh' will need to be configured to run as an executable as follows:
chmod +x run_model.sh

== Return To Home Page ==
Return to [[Main_Page | Wiki Home Page]].