file produced by TCFDSource
has mostly the *.tcfd
extension. It is a human-readable plain text file where every line falls into one of the following categories:
- Empty line.
- Comment, introduced by a hash sign (`#’).
- Keyword-values pair.
The keywords are strings uninterrupted by a whitespace character. They contain only alphanumerical characters, numbers, dashes and underscores. Every keyword can be generally set to an arbitrary number of values. A value is a string uninterrupted by a whitespace character. Some keywords have a special structure “N
something”, where “N” is a positive number. These are used to assign properties to individual components, speedlines, working points, post-processing modes etc. This nest to deeper levels, resulting in keywords like “X
keywd3”. A complete list of recognized keywords, together with some sample values and explanation, is presented in the table at the end of this chapter.
Both the UNIX-like (LF) and Windows (CR+LF) line endings are supported on both UNIX-like and Windows operating systems.
Some numerical values in the TCFD file can bear a user-selectable physical unit. This is always indicated in the keyword table as “Selectable unit”. Table
summarizes the available units. The unit is appended to the numerical value using an underscore. So, for instance, one millimeter is denoted as 1mm
. While the temperature quantities allow the use of the degree symbol, e.g. 100C
, it is recognized in UTF-8 encoding only (degree symbol is not part of ASCII). This is natural in modern Unix-like operating systems, but we recommend sticking to 1C
in Windows. When a number is used without unit suffix, it is assumed that it is in SI (i.e. the metric system).