Requirements
Complete the Telemac steady 2d tutorial (or similar).
The
MASS-BALANCE : YESand/orPRINTING CUMULATED FLOWRATES : YESkeywords must have been used in the steering (.cas) file to print mass fluxes across liquid boundaries in the Terminal.The Telemac simulation must have been running with the
sflag (more details below):
telemac2d.py [STUDY-NAME].cas -sAn installation of Python along with the
numpy,pandas, andmatplotliblibraries (see the Python installation guide), even thoughflusstoolsis not required).
All required simulation files for this tutorial can be downloaded from the hydro-informatics/telemac repository on GitHub (see details below).
This chapter uses the simulation files from the Telemac steady 2d tutorial, but with a slightly different definition of timesteps and printout periods:
/ steady2d-conv.cas
TIME STEP : 1.
NUMBER OF TIME STEPS : 10000
GRAPHIC PRINTOUT PERIOD : 50
LISTING PRINTOUT PERIOD : 50Additionally, the simulation was rerun with the -s flag, which saves the simulation state in a file called similar to [FILE-NAME].cas_YEAR-MM-DD-HHhMMminSSs.sortie.
telemac2d.py steady2d-conv.cas -sBoth the steering .cas and .sortie files can be downloaded from the hydro
Extract and Check Flux Data¶
The Telemac jupyter notebook templates (HOMETEL/notebooks/ > data_manip/extraction/*.ipynb or workshops/exo_fluxes.ipynb) provide some guidance for extracting data from simulation results, which can be tweaked into a generally applicable framework for observing mass convergence at the boundaries as a function of the defined NUMBER OF TIME STEPS. However, the notebook templates do not work straightforwardly, which is why the following paragraphs describe a simple, minimalist Python tweak called pythomac, developed by hydronumpy, pandas, and matplotlib libraries (see the Python installation guide):
Pip-install the pythomac package:
pip install pythomacClone the pythomac repository from GitHub:
git clone https://github.com/hydro-informatics/pythomac.gitCopy-paste the folder pythomac/pythomac/ into your simulation directory. That is, make sure that the Python script /HOME/pythomac/extract_fluxes.py (among others) is correctly located, next to /HOME/your-simulation-dir/steady2d.cas.
Download a zipped archive of the pythomac repository from GitHub (right-click here > save as...). Open the zip archive > open pythomac-main, and extract the contents of the pythomac folder (i.e., pythomac-main/pythomac/) next to your simulation directory. That is, make sure that the Python script /HOME/pythomac/extract_fluxes.py (among others) is correctly located, next to /HOME/your-simulation-dir/steady2d.cas.
Expand to see the code in the extract_fluxes.py Python script:
""" Extract data from a Telemac simulation that has already been running.
The codes are inspired by the following jupyter notebook:
HOMETEL/notebooks/data_manip/extraction/output_file_extraction.ipynb
which uses the following example case:
/examples/telemac2d/bump/t2d_bump_FE.cas
"""
# retrieve file paths - this script must be stored in the directory where the simulation lives
import sys
import os
# data processing
import pandas as pd
import numpy as np
# plotting
import matplotlib
import matplotlib.pyplot as plt
sys.path.insert(0, os.path.dirname(os.path.realpath(__file__)))
# Telemac stuff
from parser_output import get_latest_output_files
from parser_output import OutputFileData
def extract_fluxes(
model_directory="",
cas_name="steady2d.cas",
plotting=True
):
"""This function writes a .csv file and an x-y plot of fluxes across the boundaries of a Telemac2d model. It auto-
matically place the .csv and .png plot files into the simulation directory (i.e., where the .cas file is).
Notes:
* The Telemac simulation must have been running with the '-s' flag (``telemac2d.py my.cas -s``).
* Make sure to activate the .cas keyword ``PRINTING CUMULATED FLOWRATES : YES``
* This script skips volume errors (search tags are not implemented).
* Read more about this script at
https://hydro-informatics.com/numerics/telemac/telemac2d-steady.html#verify-steady-tm2d
:param str model_directory: the file directory where the simulation lives
:param str cas_name: name of the .cas steering file (without directory)
:param bool plotting: default (True) will place a figure called flux-convergence.png in the simulation directory
:return pandas.DataFrame: time series of fluxes across boundaries (if Error int: -1)
"""
# assign cas file name in the folder
file_name = get_latest_output_files(
os.path.join(model_directory, # os.path.dirname(os.path.realpath(__file__))
cas_name
)
)
# go to working directory
try:
os.chdir(model_directory)
except Exception as problem:
print("ERROR: the provided directory {0} does not exist:\n{1}".format(str(model_directory), str(problem)))
return -1
try:
out_file = OutputFileData(file_name[0])
except Exception as e:
print("CAS name: " + str(os.path.join(os.path.dirname(os.path.realpath(__file__)), cas_name)))
print("ERROR in file {0}:\n{1}".format(str(file_name), str(e)))
print("Recall: the simulation must run with the -s flags")
return -1
print("Found study with name: {}".format(out_file.get_name_of_study()))
print("The simulation took: {} seconds".format(out_file.get_exec_time()))
# extract total volume, fluxes, and volume error
out_fluxes = out_file.get_value_history_output("voltotal;volfluxes;volerror")
out_fluxes_dict = {}
for e in out_fluxes:
try:
# differentiate between Time and Flux series with nested lists
if not isinstance(e[0], tuple):
out_fluxes_dict.update({e[0]: np.array(e[1])})
else:
for sub_e in e:
try:
if "volume" in str(sub_e[0]).lower():
# go here if ('Volumes (m3/s)', [volume(t)])
out_fluxes_dict.update({sub_e[0]: np.array(sub_e[1])})
if "fluxes" in str(sub_e[0]).lower():
for bound_i, bound_e in enumerate(sub_e[1]):
out_fluxes_dict.update({
"Fluxes {}".format(str(bound_e)): np.array(sub_e[2][bound_i])
})
except Exception as problem:
print("ERROR in intended VOLUME tuple " + str(sub_e[0]) + ":\n" + str(problem))
except Exception as problem:
print("ERROR in " + str(e[0]) + ":\n" + str(problem))
print("WARNING: Flux series seem empty. Verify:")
print(" - did you run telemac2d.py sim.cas with the -s flag?")
print(" - did your define all required VARIABLES FOR GRAPHIC PRINTOUTS (U,V,S,B,Q,F,H)?")
try:
df = pd.DataFrame.from_dict(out_fluxes_dict)
df.set_index(list(df)[0], inplace=True)
except Exception as problem:
print("ERROR: could not convert dict to DataFrame because:\n" + str(problem))
return -1
export_fn = "extracted_fluxes.csv"
print("* Exporting to {}".format(str(os.path.join(model_directory, export_fn))))
df.to_csv(os.path.join(model_directory, export_fn))
if plotting:
font = {'size': 9}
matplotlib.rc('font', **font)
fig = plt.figure(figsize=(6, 3), dpi=400)
axes = fig.add_subplot()
colors = plt.cm.Blues(np.linspace(0, 1, len(df.columns)))
markers = ("x", "o", "s", "+", "1", "D", "*", "CARETDOWN", "3", "^", "p", "2")
for i, y in enumerate(list(df)):
if "flux" in str(y).lower():
axes.plot(df.index.values, df[y].abs(), color=colors[i], markersize=2, marker=markers[i], markerfacecolor='none',
markeredgecolor=colors[i], linestyle='-', linewidth=1.0, alpha=0.6, label=y)
axes.set_xlim((np.nanmin(df.index.values), np.nanmax(df.index.values)))
axes.set_ylim(bottom=0)
axes.set_xlabel("Time (s)")
axes.set_ylabel("Fluxes (m$^3$/s)")
axes.legend(loc="best", facecolor="white", edgecolor="gray", framealpha=0.5)
fig.tight_layout()
fig.savefig(os.path.join(model_directory, "flux-convergence.png"))
print("* Saved plot as " + str(os.path.join(model_directory, "flux-convergence.png")))
return dfDetailed instructions for using the extract_fluxes() function through pythomac and its dependencies (numpy, pandas, and matplotlib) can be found at https://
To use the functions defined in pythomac, copy the following code into a new Python script called, for instance, example_flux_convergence.py in the directory where the dry-initialized steady2d simulation ran (or download example_flux_convergence.py):
# example_flux_convergence.py
from pathlib import Path
from pythomac import extract_fluxes
simulation_dir = str(Path(__file__).parents[1])
telemac_cas = "steady2d.cas"
fluxes_df = extract_fluxes(
model_directory=simulation_dir,
cas_name=telemac_cas,
plotting=True
)Run the Python script from Terminal (or Anaconda Prompt) as follows (make sure to cd into the simulation directory):
python example_flux_convergence.pyThe script will have placed in the simulation folder:
a CSV file called extracted_fluxes.csv (download), and
a plot of flux convergences (flux-convergence.png) across the model boundaries (see Fig. 1) showing qualitatively that the fluxes reached convergence after approximately 6000-7000 timesteps.

Figure 1:Flux convergence plot across the two boundaries of the dry-initialized steady Telemac2d simulation with a total simulation time of timesteps seconds, created with the pythomac.extract_fluxes() function.
Identify Convergence¶
To test if and when the fluxes converged, we can calculate the differences between fluxes for every timestep as:
where and are the sum of the outflow and inflow fluxes across the model boundaries at timestep , respectively. In a stable steady simulation, the ratio of inflows and outflows should converge toward a convergence constant c_{\varepsilon} equal to unity with increasing time:
The combination of the convergence rate (or order) , and the convergence constant indicate:
linear convergence if = 1 and
slow sublinear convergence if = 1 and = 1
fast superlinear convergence if > 1 and
divergence convergence if = 1 and > 1; or < 1
To determine the timestep at which a steady simulation can be considered to have reached a stable state, we want to observe when = 1 and = 1 indicate sublinear convergence. That is, we look for the timestep above which each additional timestep only insignificantly improves the model precision (read more on the term insignificant in the below section). Thus, assuming that the model convergences in any form, we can set = 1 to compute as a function of and :
This equation can be implemented in a Python function as follows:
import numpy as np
import pandas as pd
def calculate_convergence(Q_in, Q_out, conv_constant=1.):
# calculate the error epsilon between two flux series
epsilon = np.array(abs(Q_in - Q_out))
# derive epsilon at t and t+1
epsilon_t0 = epsilon[:-1] # cut off last element
epsilon_t1 = epsilon[1:] # cut off element zero
# return convergence rate as pandas DataFrame
return pd.DataFrame({"Convergence rate": np.emath.logn(epsilon_t0, epsilon_t1) / conv_constant })To calculate (Python variable name: iota_t) with the above function, amend the example_flux_convergence.py Python script:
# example_flux_convergence.py
# ...
# add to header (alternatively copy-paste the above function into this script):
from pythomac import calculate_convergence
# calculate fluxes_df (see above code block)
fluxes_df = [...]
# calculate iota (t) with the calculate_convergence function
iota_t = calculate_convergence(
fluxes_df["Fluxes Boundary 1"][1:], # remove first zero-entry
fluxes_df["Fluxes Boundary 2"][1:], # remove first zero-entry
)The resulting convergence rate is plotted in Fig. 2 for the steady 2d tutorial, with the modified printout periods of 50 seconds and a total simulation time of 10000 seconds.

Figure 2:The convergence rate as a function 10000 simulation timesteps of the steady 2d simulation.
Derive Optimum Simulation Time¶
To save computing time, we are interested in the timestep at which the inflow and outflow fluxes converged. The fluxes plotted in Fig. 1, and the convergence rate in Fig. 2 qualitatively suggest that the simulation was stable after approximately 6000 seconds (timesteps). The bumps in both figures after 4000 timesteps well indicate the “encounter” of the flux “waves” coming from the upstream and downstream boundaries (see the animation in the steady 2d tutorial). Only afterward, did convergence set in.
The definition of when convergence is reached (i.e., being insignificant) can be subjective. Most modelers would agree that fluctuations of the convergence rate of more than 0.1 to 0.01 are unacceptably high, but, depending on the problem considered, -fluctuations in the order of 10 to 10 might be considered acceptable. To investigate at which simulation timestep a target convergence rate was achieved, we can analyze the vector of resulting from the above Equation. Specifically, we want to know after which timestep the targeted convergence fluctuation is not exceeded anymore. Note that plotted in Fig. 2 achieved a possibly desired target convergence rate of = 10 already after approximately 3000 timesteps, but jumped up again after 4000 timesteps when the upstream “wave” rolled over the downstream boundary. Therefore, we want an algorithmic implementation that detects the last > in the vector of . To this end, we can add to the above-started example_flux_convergence.py Python script the following code:
# example_flux_convergence.py
# ...
# calculate fluxes_df (see above code block)
fluxes_df = [...]
# calculate iota (t) with the calculate_convergence function
iota_t = [...]
# define a desired target convergence precision (delta iota_tar)
target_convergence_precision = 1.0E-6
# calculate the differences in the convergence rates
convergence_diff = np.diff(iota_t)
# find the index of the last element in the convergence differences that is larger than
# the desired target convergence precision and add +1 (i.e., the first element being
# permanently smaller than the desired precision)
idx = np.flatnonzero(abs(convergence_diff) > target_convergence_precision)[-1] + 1
# print the timestep at which the desired convergence was achieve to the console
printout_period_in_cas = 50 # the printout period defined in the cas file
print("The simulation converged after {0} simulation seconds ({1}th printout).".format(
str(printout_period_in_cas * idx), str(idx)))The simulation converged after 8050 simulation seconds (161th printout).Now that you know when your Telemac simulation converges satisfactorily, you can reduce the NUMBER OF TIME STEPS parameter in the .cas steering file, for example:
/ steady2d-conv.cas
TIME STEP : 1.
NUMBER OF TIME STEPS : 8050
GRAPHIC PRINTOUT PERIOD : 50
LISTING PRINTOUT PERIOD : 50Troubleshoot Instabilities & Divergence¶
If a steady simulation never reaches stability of fluxes or even flux divergence, make sure that all boundaries are robustly defined according to the spotlight section on boundary conditions, and have a look at the workflow in the next section on mass conservation.