Linux Install
Introduction
TUFLOW FV provides .rpm and .deb installer package options. The installers have currently been tested on CentOS and Ubuntu (They should also work on other Red Hat and Debian distributions but testing is recommended). If you would like an rpm or deb built for commercial releases prior to 2020 please contact support@tuflow.com.
Codemeter Configuration
To license TUFLOW FV 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.
- If using a software lock (either network or local licenses please follow the instructions within Wibu Software License Linux.
TUFLOW Versioning
TUFLOW FV uses a year.minor.patch versioning convention as follows.
- The year corresponds to the major version number e.g. 2025.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. 2025.1.0
- Patch releases are bug fixes only and increment the patch version number, e.g. 2025.0.1
RPM Install
- Download the .rpm for the specific TUFLOW FV build from https://www.tuflow.com/downloads/#tuflow_fv
- Save the rpm locally. A common location is the home folder for the current user ~/
- Run the preferred installation command. For example if installing the TUFLOW FV 2025.2.0 release: sudo rpm -ivh ~/tuflowfv-2025.2-2025.2.0-1A.el7.x86_64.rpm or yum install ~/tuflowfv-2025.2-2025.2.0-1A.el7.x86_64.rpm
- This installs a version specific copy of the libraries the specific version of TUFLOW FV needs to run to /usr/local/lib and the executable and version configuration script to /usr/local/bin. The configuration script contains the following commands: #!/bin/bash export SCRIPT_DIR=$(dirname "$0") export LD_LIBRARY_PATH=$SCRIPT_DIR/../lib/tuflowfv-2025.2:$LD_LIBRARY_PATH ulimit -s unlimited > /dev/null $SCRIPT_DIR/tuflowfv-2025.2/tuflowfv-2025.2 "$@" Note: The contents of these scripts should not be modified as they are part of the installation setup.
- To uninstall run the preferred uninstaller command. For example: sudo rpm -e tuflowfv-2025.2-2025.2.0-1A.x86_64 or sudo yum remove tuflowfv-2025.2-2025.2.0-1A.x86_64. To return a list of previously installed versions to review the correct uninstall version run: rpm -qa | grep fv or yum list installed | grep fv
Note: Major and minor releases are installed with a new bin and lib directory. For example, installing 2025.0.0 will appear as tuflowfv_2025.0 with binaries installed to /usr/local/bin/tuflowfv_2025.0 and /usr/local/lib/tuflowfv_2025.0, 2025.1.0 as tuflowfv_2025.1 etc. When installing a patch release, the patch will overwrite existing binary and lib directories that share the same major and minor release number. For example TUFLOW FV 2025.1.1 will update 2025.1.0 if present.
DEB Install
The process for .deb essentially the same for the .rpm steps 2-5. For step 3 and 5 the install and uninstall command examples below are for Debian derivatives. For example (assuming TUFLOW FV 2025.2.0, modify for the specific version required):
To install:
sudo apt-get install ./tuflowfv-2025.2_2025.2.0-1A_amd64.deb
To uninstall:
sudo apt remove tuflowfv-2025.2 (to remove the program)
If unsure about which versions you have previously installed you can return a list of all the installed versions via:
apt list --installed | grep fv
Note: Major and minor releases are installed with a new bin and lib directory. For example, installing 2025.0.0 will appear as tuflowfv_2025.0 with binaries installed to /usr/local/bin/tuflowfv_2025.0 and /usr/local/lib/tuflowfv_2025.0, 2025.1.0 as tuflowfv_2025.1 etc. When installing a patch release, the patch will overwrite existing binary and lib directories that share the same major and minor release number. For example TUFLOW FV 2025.1.1 will update 2025.1.0 if present.
Running A Model
For either Linux distributions TUFLOW FV can be run by calling tuflowfv_2025.2 (replace with the required version) or by passing it a configuration file name:
tuflowfv_2025.2 my_run.fvc
Model specific commands such as the export OMP_NUM_THREADS environment variable can either be added via the command line, or in your own custom run script that call the configuration file name, for example run_model.sh:
#!/bin/bash export OMP_NUM_THREADS=8 tuflowfv_2025.2 my_run.fvc
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 Wiki Home Page.