#TMC_RT_H          Начало файла задания
#STEP              Это первый шаг
   Данные для первой задачи
#END_STEP
#STEP              Это второй шаг
   Данные для второй задачи
#END_STEP
#EOF               Конец файла задания

#TMC_RT_H
#define L1 @ (   50.00)
#define L2 @ (   50.00)
#define L3 @ (   50.00)
#define W_freq @ (  10 )
#define W_eps @ ( 4.00 )
#define W_waveg @ (  6.00 )
#define W_input @ (  2.00 )
#define W_delta @ (    0.5 )
#define W_type @ MAGNETIC
#define a1 @ ( W_input )
#STEP
#PARM
 ANGLE_UNIT radian;
 FREQ_UNIT GHz;
 LONG_UNIT mm;
 TIME_UNIT ns;
 DELTA W_delta;
 TIME 0.; 5;
 X_MIN  0.0;
 X_MAX L1+L2+L3;
 Y_MIN  0.0;
 Y_MAX W_waveg;
 FREQ  10;
#END_PARM
#TOPOLOGY
 BLOCK 1;
  INPUT_X   W_type ; -a1/2; a1/2; 0; 200;
 END_B
 BLOCK 2;
  INPUT_X    W_type ; -a1/2; a1/2; 200; 201;
 END_B
 BLOCK 3;
  RECT_STAT W_type ; 0.0; L1+L2+L3; -a1/2-2*W_delta; -a1/2-1*W_delta;
 END_B
 BLOCK 4;
  RECT_STAT W_type ; 0.0;L1+L2+L3; a1/2; a1/2+W_delta;
 END_B
 BLOCK 5;
  RECT_STAT (W_eps-1); 0;L2; 0.0; W_waveg;
 END_B
#END_TOPOLOGY
#LINK_LIST
 T 1; 0.0; W_waveg/2;
 T 2; L1+L2+L3; W_waveg/2;
 T 3; 0.0; W_waveg/2;
 T 4; 0.0; W_waveg/2;
 T 5; L1; 0.0;
#END_LINK
#OUTPUT
 FILE test1;
 SMATRIX test1; 10; 4; 5;
 FIELDS;
 TOPOLOGY;
#END_OUTPUT
#END_STEP
#EOF

#PARM
    . . .
#END_PARM

ANGLE_UNIT <radian> | <gradus>;

FREQ_UNIT <GHz> | <MHz> | <kHz> | <Hz>;

LONG_UNIT <mm> | <cm> | <m>;

TIME_UNIT <s> | <ms> | <mks> | <ns> | <ps>;

DELTA <expression>;

TIME <expression>; <expression>;

X_MIN <expression>;
X_MAX <expression>;
Y_MIN <expression>;
Y_MAX <expression>;

FREQ <expression>;

#TOPOLOGY
    BLOCK 1;
        <тип примитива и его параметры>
    END_B
    . . .
    BLOCK <n>;
        . . .
    END_B
#END_TOPOLOGY

BLOCK <n>;
    RECT_STAT [[file_name]]<METAL> | <MAGNETIC> | <ABSORBER> | <expression(x,y,r,f)>;
    <X_min>; <X_max>;
    <Y_min>; <Y_max>;
END_B

BLOCK 1;
    RECT_STAT METAL; 0; 30; 0; 10;
END_B

BLOCK 1;
    RECT_STAT MAGNETIC; -29; 0; -8; 0;
END_B

BLOCK 1;
    RECT_STAT ABSORBER; 0; 27; 0; 9;
END_B

BLOCK 1;
    RECT_STAT 3; 0; 31; 0; 12;
END_B

BLOCK 1;
    RECT_STAT -1; 0; 31; 0; 12;
END_B

BLOCK 1;
    RECT_STAT -2*x/30; 0; 30; 0; 10;
END_B

BLOCK <n>;
    CIRCLE_STAT <METAL> | <MAGNETIC> | <ABSORBER> | <expression(x,y,r,f)>;
    <R_min>; <R_max>;
    <F_min>; <F_max>;
END_B

BLOCK 1;
    CIRCLE_STAT METAL; 0; 30; 0; 2*3.141592653589;
END_B

BLOCK 1;
    CIRCLE_STAT MAGNETIC; 28.9; 29; 3.141592653589/2; 3*3.141592653589/2;
END_B

BLOCK 1;
    CIRCLE_STAT ABSORBER; 0; 27; 0; 3.141592653589;
END_B

BLOCK 1;
    CIRCLE_STAT 8; 0; 30; 0; 2*3.141592653589;
END_B

BLOCK 1;
    CIRCLE_STAT -2; 10; 30; 3.141592653589/2; 3.141592653589;
END_B

BLOCK <n>;
    POLYGON_STAT <METAL> | <MAGNETIC> | <ABSORBER> | <expression(x,y,r,f)>;
        L <expression>; <expression>;
        L <expression>; <expression>;
        L <expression>; <expression>;
        [L <expression>; <expression>;]
        …
END_B

BLOCK 1;
    POLYGON_STAT METAL;
        L -10; 0;
        L 0; 10;
        L 10; 0;
        L 0; -10;
        L -10; 0;
END_B

BLOCK 1;
    POLYGON_STAT METAL;
        L -10; 0;
        L 0; 10;
        L 10; 0;
        L 0; -10;
END_B

BLOCK 1;
    POLYGON_STAT 3;
        L -10; 0;
        L 0; 10;
        L 10; 0;
        L 0; -10;
END_B

BLOCK 1;
    POLYGON_STAT MAGNETIC;
        L -10; 0;
        L 0; 10;
        L 10; 0;
END_B

BLOCK 1;
    POLYGON_STAT ABSORBER;
        L 10; 0;
        L 0; -10;
        L -10; 0;
END_B

BLOCK 1;
    POLYGON_STAT -0.75;
        L 10; 0;
        L 0; -10;
        L -10; 0;
END_B

BLOCK <n>;
    INPUT_X [<METAL> | <MAGNETIC>];
    <Y_min>; <Y_max>;
    <T_min>; <T_max>;
    [<Amplitude>]; [<Faza>];
    [<Eps>];
END_B

BLOCK <n>;
    INPUT_Y [<METAL> | <MAGNETIC>];
    <X_min>; <X_max>;
    <T_min>; <T_max>;
    [<Amplitude>]; [<Faza>];
    [<Eps>];
END_B

BLOCK 1;
    INPUT_X METAL; 0; 20; 0; 10;
END_B

BLOCK 1;
    INPUT_X MAGNETIC; 0; 2; 0; 100;
END_B

BLOCK 1;
    INPUT_Y ; 0; 20; 0; 10;
END_B

BLOCK 1;
    INPUT_Y MAGNETIC; 0; 2; 0; 100;
END_B

BLOCK <n>;
    FILE <file_name>;
    <X_min>; <X_max>;
    <Y_min>; <Y_max>;
END_B

BLOCK 1;
    RECT_STAT [distr]-(2*x/30)^2+(2*y/10)^3; 2; 30; 1; 10;
END_B

BLOCK 1;
    FILE distr; 2; 30; 1; 10;
END_B

#LINK_LIST
    T <n>; <X0>; <Y0>;
    . . .
#END_LINK

#OUTPUT
    . . .
#END_OUTPUT

FILE <file_name>;

TOPOLOGY;

FIELDS;

SMATRIX <Sfile>; <expression>; <T_min>; <T_max>;

FIELD_DISTRIBUTION <file_name>; <freq>; <T_min>; <T_max>;
FIELD_DISTRIBUTION_M <file_name>; <freq>; <T_min>; <T_max>;

#define <имя>  [par1; par2; ... ; par32;] @ text1(par1 - par32)\\
                                            text2(par1 - par32)\\
                                            text3(par1 - par32)

#define  Length @ 38+12
#define  Width @ Length/2
 . . .
    RECT_STAT 3; 0; Length; 0; Width;

    RECT_STAT 3; 0; 38+12; 0; 38+12/2;

#define  Length @ (38+12)
#define  Width @ Length/2

#define  Stp  name1; name2; @ name1+name2
#define  Stm  param; @ param*param
. . .
    RECT_STAT 3; 0; (Stm  (Stp 10; 2;);); 0; 40;

    RECT_STAT 3; 0; 10+2*10+2; 0; 40;

#include <file_name>

#include parm.h
 . . .
    BLOCK 1;
        RECT_STAT 3; 0; Length; 0; Width;

#define  Length @ (38+12)
#define  Width @ Length/2

#define step1 Freq__; File__; SFile__; Tmin__; Tmax__; @\\
#STEP\\
#PARM\\
 ANGLE_UNIT radian;\\
 FREQ_UNIT GHz;\\
 LONG_UNIT mm;\\
 TIME_UNIT ns;\\
 DELTA W_delta;\\
 TIME 0.; 5;\\
 X_MIN  0.0;\\
 X_MAX L1+L2+L3;\\
 Y_MIN  0.0;\\
 Y_MAX W_waveg;\\
 FREQ  Freq__ ;\\
#END_PARM\\
#TOPOLOGY\\
 BLOCK 1;\\
  INPUT_X   W_type ; -a1/2; a1/2; 0; 200;\\
 END_B\\
 BLOCK 7;\\
  INPUT_X    W_type ; -a1/2; a1/2; 200; 201;\\
 END_B\\
 BLOCK 2;\\
  RECT_STAT W_type ; 0.0; L1+L2+L3; -a1/2-2*W_delta; -a1/2-1*W_delta;\\
 END_B\\
 BLOCK 3;\\
  RECT_STAT W_type ; 0.0;L1+L2+L3; a1/2; a1/2+W_delta;\\
 END_B\\
 BLOCK 5;\\
  RECT_STAT [epsil1](W_eps-1); 0;L2; 0.0; W_waveg;\\
 END_B\\
#END_TOPOLOGY\\
#LINK_LIST\\
 T 1; 0.0; W_waveg/2;\\
 T 2; 0.0; W_waveg/2;\\
 T 3; 0.0; W_waveg/2;\\
 T 5; L1; 0.0;\\
 T 7; L1+L2+L3; W_waveg/2;\\
#END_LINK\\
#OUTPUT\\
 FILE File__;\\
 SMATRIX SFile__; Freq__; Tmin__; Tmax__;\\
! FIELDS;\\
! TOPOLOGY;\\
#END_OUTPUT\\
#END_STEP\\

#TMC_RT_H
#define L1 @ (   50.00)
#define L2 @ (   50.00)
#define L3 @ (   50.00)
#define W_eps @ ( 4.00 )
#define W_waveg @ (  400.00 )
#define W_input @ (  2.00 )
#define W_delta @ (    0.5 )
!#define W_type @ METAL
#define W_type @ MAGNETIC
#define file_S @ test101
#define a1 @ ( W_input )
#include step1.h
step1 10.0; test100; file_S; 4; 5;
step1 10.1; test101; file_S; 4; 5;
step1 10.2; test102; file_S; 4; 5;
…
step1 12.0; test120; file_S; 4; 5;
#EOF

#define W_eps @ ( -4 + 4*r/(W_waveg/2)+1 )
…
 BLOCK 104;
  CIRCLE_STAT (W_eps-1); 0; W_waveg/2; 0; 2*3.1415;
 END_B
…
 BLOCK 8;
  RECT_STAT ABSORBER; L_waveg-5*W_delta; L_waveg - 1*W_delta+0.00; 0.0; W_waveg-2*W_delta;
 END_B

The .tpl template file — how to create it. A complete reference of the input language

Applies to the compute kernels PlanarRT_H (tmc_rth.exe) and PlanarRT_X (tmc_rtx.exe).

The document has been reconstructed from the author's manual "TAMIC-Rt H. A program for the electrodynamic analysis of planar structures with inhomogeneous dielectric filling in the H-plane, version 2.0p" (TAMIC_soft group, 2000) and checked against the current source code of TMC Suite. Places where the current code diverges from the 2000 manual are marked explicitly — in case of a discrepancy, the code is considered correct.

---

1. What the template file is

The input data of a compute kernel is the geometry of the device under analysis, which is described in a text template file with the .tpl extension. The kernel reads the .tpl, performs the computation and produces results as files of several types, which are then viewed with the package's viewers.

Block diagram of the package (fig. 2.1 of the author's manual).

Discrepancy with the figure. In the 2000 diagram the field file is labelled File.ft, while the text of the same manual calls it File.tf. In the current code the field is written to the files .ex / .ey / .hz / .em / .ef (see section 8). The .tf extension survives only in the list of formats FieldView can open.

This separation (computing on one side, viewing on the other) makes the system more flexible and minimises the computer resources required to run a computation.

---

2. General structure of the template file

Every line of the file starts with a unique descriptor that defines the data following it.

The template file always begins with the line #TMC_RT_H and ends with the line #EOF.

The whole template is divided into steps. Each step may describe an independent microwave device or a part of one; a step begins with the line #STEP and ends with #END_STEP:

#TMC_RT_H          Start of the template file
#STEP              This is the first step
   Data for the first problem
#END_STEP
#STEP              This is the second step
   Data for the second problem
#END_STEP
#EOF               End of the template file

The #TMC_RT_H signature is common to both kernels. The X-kernel (tmc_rtx.exe) reads files with the same first line #TMC_RT_H; there is no separate #TMC_RT_X signature in the code.

Each step consists of four sections, which are best placed in this order:

The parameter section may be omitted in the steps that follow the first one — then the parameters are taken to be the same as in the previous step.

2.1. Syntax

• All operators carrying the # symbol must start at the first position of the line.
• The other operators must have at least one space in the first position of the line.
• A comment is any line, or part of a line, starting with the ! symbol.
• Empty lines and lines of spaces only are allowed.
• Parameters are separated from the line identifier by at least one space, and from each other by the ; symbol.

The formalised format notations below use the following conventions:

---

3. Method: how to write a template from scratch

This is the very order of actions the author used. Let us go through it on the problem from the author's manual: the scattering of a plane wave on a plane-parallel plate with ε = 4 at a frequency of 10 GHz.

Step 1. Draw the topology in the H-plane

You start with a drawing of the real device in the H-plane, with all its dimensions.

The placement of the plane-parallel plate in the H-plane (fig. 3.1). All dimensions are in millimetres.

Step 2. Fit the device into a "box"

The whole device must fit inside a rectangle — it is called the "box". The position of the box is given in the parameter section by the values X_MIN, X_MAX, Y_MIN, Y_MAX.

The boundary of the box is metal or the inputs of the device. This matters: the box boundary itself is always metal, unless an input stands on it.

The placement of the plate inside the "box" and the values of the constant expressions to be set (fig. 3.2).

Note the notation ε⁺ = 3 inside the plate: this is not the permittivity itself but the increment over the permittivity of vacuum. A plate with ε = 4 corresponds to an increment of ε⁺ = 3 (see section 5.1).

Step 3. Decompose the geometry into primitives

The resulting geometry is decomposed into blocks — the graphic primitives of the input language.

The decomposition of the given geometry using graphic primitives (fig. 3.3).

For our problem this gives five blocks:

Step 4. Choose the grid step Δ

The grid step DELTA determines the accuracy. The rules for choosing it are in section 4.5. In short: roughly 1/20 of the wavelength in the waveguide at the maximum frequency of the range gives an accuracy of about 3 %.

Step 5. Write the template

Each block is described in the #TOPOLOGY section in its own local coordinate system, and is then placed inside the box by a T line in the #LINK_LIST section.

The full text of the template (the file samples/SAMPLE_R/TEST_MAG/EPS4/TEST0.TPL, quoted after the author's manual — the file in the repository has been changed since, see the note below):

#TMC_RT_H
#define L1 @ (   50.00)
#define L2 @ (   50.00)
#define L3 @ (   50.00)
#define W_freq @ (  10 )
#define W_eps @ ( 4.00 )
#define W_waveg @ (  6.00 )
#define W_input @ (  2.00 )
#define W_delta @ (    0.5 )
#define W_type @ MAGNETIC
#define a1 @ ( W_input )
#STEP
#PARM
 ANGLE_UNIT radian;
 FREQ_UNIT GHz;
 LONG_UNIT mm;
 TIME_UNIT ns;
 DELTA W_delta;
 TIME 0.; 5;
 X_MIN  0.0;
 X_MAX L1+L2+L3;
 Y_MIN  0.0;
 Y_MAX W_waveg;
 FREQ  10;
#END_PARM
#TOPOLOGY
 BLOCK 1;
  INPUT_X   W_type ; -a1/2; a1/2; 0; 200;
 END_B
 BLOCK 2;
  INPUT_X    W_type ; -a1/2; a1/2; 200; 201;
 END_B
 BLOCK 3;
  RECT_STAT W_type ; 0.0; L1+L2+L3; -a1/2-2*W_delta; -a1/2-1*W_delta;
 END_B
 BLOCK 4;
  RECT_STAT W_type ; 0.0;L1+L2+L3; a1/2; a1/2+W_delta;
 END_B
 BLOCK 5;
  RECT_STAT (W_eps-1); 0;L2; 0.0; W_waveg;
 END_B
#END_TOPOLOGY
#LINK_LIST
 T 1; 0.0; W_waveg/2;
 T 2; L1+L2+L3; W_waveg/2;
 T 3; 0.0; W_waveg/2;
 T 4; 0.0; W_waveg/2;
 T 5; L1; 0.0;
#END_LINK
#OUTPUT
 FILE test1;
 SMATRIX test1; 10; 4; 5;
 FIELDS;
 TOPOLOGY;
#END_OUTPUT
#END_STEP
#EOF

A walk-through of the key places:

• #define W_eps @ ( 4.00 ) — the permittivity of the plate, ε = 4;
• RECT_STAT (W_eps-1); … — the block is passed the increment ε⁺ = ε − 1 = 3. Hence the -1;
• INPUT_X W_type; -a1/2; a1/2; 0; 200; — an input of width a1, an RF pulse from 0 to 200 ns;
• the second input (Block 2) has T_min = 200, which is greater than the analysis time (TIME 0.; 5;) — this is how you define an input that has no incident wave, only reception;
• SMATRIX test1; 10; 4; 5; — write the S-matrix for the frequency of 10 GHz, averaged from 4 to 5 ns.

The file in the repository differs from the manual. In samples/SAMPLE_R/TEST_MAG/EPS4/TEST0.TPL the values L1=100, L2=600, L3=100, W_eps=-0.01, W_delta=0.1, TIME 0.; 200; have been changed since 2000, and the first input has gained extra parameters (… 0; 200; 1.; ; — amplitude and phase, see section 6.4). The text above is the one from the manual; it shows the original intent.

Step 6. Check and run

1. Open the .tpl in the kernel (File → Open).
2. Parsing errors are reported with the line number — the language is checked strictly.
3. Run the computation and look at the results with the viewers (section 8).

---

4. The parameter section #PARM

#PARM
    . . .
#END_PARM

#PARM or #PARMS? In the author's manual of 2000 the "Input format" parts of items 4.1.x are written with #PARMS / #END_PARMS (11 places), while all the real examples and the table of contents use #PARM / #END_PARM. This is a trace of the related product TAMIC-E/H, where the section really is called #PARMS.

Both variants work. The canonical names in the code are #PARM and #END_PARM (src/Include/TmcRTH_Indan.h, line 23), but sections are searched for by comparing prefixes (strncmp(csCh, csSection, csSection.GetLength()) in TmcRTH_Indan.cpp, lines 435 and 460), so #PARMS and #END_PARMS match as well. Writing #PARM / #END_PARM is recommended.

The units of angle, frequency, length and time must be set before the frequencies and the parameters that have the dimension of length and time are defined.

The section must be present in the first step. If it is absent in the other steps, the parameters are the same as in the previous step.

4.1. ANGLE_UNIT — the unit of angle

ANGLE_UNIT <radian> | <gradus>;

Fixes the unit of the angle arguments of trigonometric functions.

The default is the same as in the previous step; if this is the first step — radian.

4.2. FREQ_UNIT — the unit of frequency

FREQ_UNIT <GHz> | <MHz> | <kHz> | <Hz>;

Entered before the FREQ line. The default in the first step is GHz.

4.3. LONG_UNIT — the unit of length

LONG_UNIT <mm> | <cm> | <m>;

Entered before the DELTA, X_MIN, X_MAX, Y_MIN, Y_MAX lines. The default in the first step is mm.

4.4. TIME_UNIT — the unit of time

TIME_UNIT <s> | <ms> | <mks> | <ns> | <ps>;

Entered before the TIME line.

According to the author's manual, the default value in the first step is seconds (s), not ns. It is better to set the time unit explicitly.

4.5. DELTA — the grid step (accuracy of the analysis)

DELTA <expression>;

Its physical meaning is the size of the spatial sample, the step of the square grid the whole device is split into. This is the main accuracy parameter.

The author's recommendations:

1. For an accuracy of about 3 % the value should be about 1/20 of the wavelength in the waveguide at the maximum frequency of the range. More precisely — it is determined by a series of convergence computations.
2. As the step decreases, the analysis time grows as its cube. For this reason the initial work on a device is done at low accuracy, which is raised at the final stage.
3. Choose the step and the geometry so that the geometry fits a whole number of samples. If the metal thickness is 1, 2, 3, 4 mm — take DELTA = 1 mm or 0.5 mm, not 1.02 mm or 0.47 mm.
4. The computation time is at its minimum when a whole number of samples fits into the "box" along X and Y.

The parameter is required in the first step.

4.6. TIME — the analysis time

TIME <expression>; <expression>;

The first parameter is the start time of the analysis, the second is the end time. Required in the first step.

4.7. X_MIN, X_MAX, Y_MIN, Y_MAX — the boundaries of the "box"

X_MIN <expression>;
X_MAX <expression>;
Y_MIN <expression>;
Y_MAX <expression>;

They define the rectangle the topology under analysis is placed into. Required in the first step.

4.8. FREQ — the frequency of the excitation signals

FREQ <expression>;

The frequency of the excitation signals at the inputs of the device. Required in the first step.

4.9. Parameters accepted by the code but not affecting the computation

These lines are parsed and their values stored, but no kernel reads them. Verified against the sources: the corresponding getters (dGetHeight, GetDeltaT, IsDeltaTDefine) are not called from kernels/, from fieldview/ or from viewers/; the rNUnit / rBUnit fields are not read outside the parsing module.

Practical consequence: the plasma concentration N in *_STAT_N blocks is always treated as m⁻³, and the induction B in *_STAT_B blocks is always in Tesla, regardless of what is written in N_UNIT / B_UNIT.

To be clarified with the author (K. N. Klimov): were HEIGHT and DELTA_T_MECHANICAL meant to be working parameters? At present they are not connected to the computation.

Defect (a candidate for ISSUES.md): the ReadNUnit function in src/libs/TMCIndan/TmcRTH_IndanParam.cpp (lines ~1211–1224) writes its result into the csBUnit / rBUnit fields instead of csNUnit / rNUnit — an obvious copy-paste error. It is harmless at present (neither field is used), but it will become a bug if the units are connected to the computation. Besides, the N_UNIT multipliers raise a question: cm3 → 0.000001, whereas 1 cm⁻³ = 10⁶ m⁻³.

---

5. The topology section #TOPOLOGY

#TOPOLOGY
    BLOCK 1;
        <the primitive type and its parameters>
    END_B
    . . .
    BLOCK <n>;
        . . .
    END_B
#END_TOPOLOGY

Every block is given a unique number <n> — an integer greater than zero. The numbers do not have to be in order and do not have to be contiguous (the author's example with horns uses the numbers 1, 2, 5, 6, 7, 12, 14, 21, 22, 25, 26, 41…46, 104).

The parameters of every primitive are described in its own local coordinate system. The position of a block inside the box is defined in #LINK_LIST — therefore every block must have exactly one matching line in #LINK_LIST.

All primitives except the inputs (INPUT_X, INPUT_Y) may overlap and intersect each other. The inputs must be placed only on the boundary of the "box".

5.1. The material or the ε distribution

The first parameter of a primitive defines either the material or the distribution of the permittivity increment:

The key convention: it is the increment that is given, not the permittivity itself.

An important difference in the meaning of a primitive — a material defines the CONTOUR, not the fill. If a material is given, the primitive defines a boundary (a contour, a polyline). If an expression is given, the primitive defines an area filled with a medium. This is clearly visible in the figures below: with RECT_STAT METAL only the contour of the rectangle is metal, while with RECT_STAT 8 the whole area is filled.

Confirmed by the code: SetRectMetal (src/kernels/PlanarRT_H/TmcRTHNodeDiel.cpp:2419) allocates nNumNode = 2*nX + 2*(nY-1) nodes — this is the perimeter, not nX*nY (a fill) — and fills them in four loops: the bottom edge (y = dYmin), the top one (y = dYmax), the left one (x = dXmin) and the right one (x = dXmax).

Practical consequence. To get a solid metal object, define it by its contour: the field does not penetrate inside a closed contour. And to get a solid dielectric insert — give an expression, it fills the area.

Careful, METAL and MAGNETIC swap places. In src/Include/Tmcgrviw.h (lines 159–165) the definitions depend on the _MODEL_RTE__ macro: when it is present, METAL and MAGNETIC swap roles (the E-plane model). In the regular H and X builds this macro is not defined, and the words mean what they say.

5.2. RECT_STAT — a fixed rectangle

BLOCK <n>;
    RECT_STAT [[file_name]]<METAL> | <MAGNETIC> | <ABSORBER> | <expression(x,y,r,f)>;
    <X_min>; <X_max>;
    <Y_min>; <Y_max>;
END_B

The optional [file_name] in square brackets before the expression means save the computed ε distribution into the file file_name.eps, so that it can later be reused by the FILE primitive (section 5.6). It is needed to improve efficiency when computations over large areas are repeated.

Two additional conditions for MAGNETIC and ABSORBER:

1. The differences X_max − X_min and Y_max − Y_min must exceed 2*DELTA — the thickness and the height must be greater than two spatial samples.
2. The whole rectangle must be inside the box, and its boundary must be at least one grid step away from the boundary of the box.

Examples

Fig. 4.1. A fixed rectangle of 30×10 mm bounded by metal.

BLOCK 1;
    RECT_STAT METAL; 0; 30; 0; 10;
END_B

Fig. 4.2. A rectangle of 29×8 mm with open-circuit walls (a magnetic).

BLOCK 1;
    RECT_STAT MAGNETIC; -29; 0; -8; 0;
END_B

Fig. 4.3. A rectangle of 27×9 mm with absorbing walls.

BLOCK 1;
    RECT_STAT ABSORBER; 0; 27; 0; 9;
END_B

Fig. 4.4. A rectangle of 31×12 mm with ε = 4 (the increment ε⁺ = 3).

BLOCK 1;
    RECT_STAT 3; 0; 31; 0; 12;
END_B

Fig. 4.5. A rectangle of 31×12 mm with ε = 0 (the increment ε⁺ = −1).

BLOCK 1;
    RECT_STAT -1; 0; 31; 0; 12;
END_B

Fig. 4.6. A rectangle of 30×10 mm; ε falls linearly along X from 1 at the left boundary to −1 at the right one (the increment changes from 0 to −2).

BLOCK 1;
    RECT_STAT -2*x/30; 0; 30; 0; 10;
END_B

5.3. CIRCLE_STAT — a fixed sector

BLOCK <n>;
    CIRCLE_STAT <METAL> | <MAGNETIC> | <ABSORBER> | <expression(x,y,r,f)>;
    <R_min>; <R_max>;
    <F_min>; <F_max>;
END_B

R_min, R_max are in LONG_UNIT units; F_min, F_max are in ANGLE_UNIT units.

Examples

Fig. 4.7. A metal circle with a radius of 30 mm.

BLOCK 1;
    CIRCLE_STAT METAL; 0; 30; 0; 2*3.141592653589;
END_B

Fig. 4.8. A semicircle made of a magnetic with a radius of 29 mm.

BLOCK 1;
    CIRCLE_STAT MAGNETIC; 28.9; 29; 3.141592653589/2; 3*3.141592653589/2;
END_B

Fig. 4.9. A half-disc made of an absorber with a radius of 27 mm.

BLOCK 1;
    CIRCLE_STAT ABSORBER; 0; 27; 0; 3.141592653589;
END_B

Fig. 4.10. A circle with a radius of 30 mm and ε = 9 (the increment ε⁺ = 8).

BLOCK 1;
    CIRCLE_STAT 8; 0; 30; 0; 2*3.141592653589;
END_B

Fig. 4.11. A sector with ε = −1 (the increment ε⁺ = −2).

BLOCK 1;
    CIRCLE_STAT -2; 10; 30; 3.141592653589/2; 3.141592653589;
END_B

5.4. POLYGON_STAT — a fixed polygon

BLOCK <n>;
    POLYGON_STAT <METAL> | <MAGNETIC> | <ABSORBER> | <expression(x,y,r,f)>;
        L <expression>; <expression>;
        L <expression>; <expression>;
        L <expression>; <expression>;
        [L <expression>; <expression>;]
        …
END_B

The first line carries the material or the expression. In the following lines, after the L symbol, the abscissa and the ordinate of a vertex are entered in the local coordinate system of the block.

The behaviour depends on the first parameter — this matters:

The program does not check whether the area is closed and simply connected, nor whether the vertices are traversed in the right direction. An error here is not diagnosed — it will show up as a wrong result.

Examples

Fig. 4.12. A metal quadrangle (closed explicitly — the first point is repeated at the end).

BLOCK 1;
    POLYGON_STAT METAL;
        L -10; 0;
        L 0; 10;
        L 10; 0;
        L 0; -10;
        L -10; 0;
END_B

Fig. 4.13. A metal polyline (the same text without repeating the first point).

BLOCK 1;
    POLYGON_STAT METAL;
        L -10; 0;
        L 0; 10;
        L 10; 0;
        L 0; -10;
END_B

Fig. 4.14. A dielectric quadrangle with ε = 4 (the increment ε⁺ = 3) — the area closes itself.

BLOCK 1;
    POLYGON_STAT 3;
        L -10; 0;
        L 0; 10;
        L 10; 0;
        L 0; -10;
END_B

Fig. 4.15. A polyline made of a magnetic wall.

BLOCK 1;
    POLYGON_STAT MAGNETIC;
        L -10; 0;
        L 0; 10;
        L 10; 0;
END_B

Fig. 4.16. A polyline made of an absorber.

BLOCK 1;
    POLYGON_STAT ABSORBER;
        L 10; 0;
        L 0; -10;
        L -10; 0;
END_B

Fig. 4.17. A dielectric triangle with ε = 0.25 (the increment ε⁺ = −0.75).

BLOCK 1;
    POLYGON_STAT -0.75;
        L 10; 0;
        L 0; -10;
        L -10; 0;
END_B

5.5. INPUT_X and INPUT_Y — the inputs (excitation transformers)

By their functional purpose the blocks fall into two types: excitation transformers and internal areas. All the primitives above are internal areas.

Careful with the names — they do not mean what they seem to. INPUT_X is an input along the Y axis; it is placed on the left or right boundary of the box, and its dimensions are given along Y. INPUT_Y is an input along the X axis; it is placed on the bottom or top boundary of the box, and its dimensions are given along X. Which boundary an input actually ends up on is determined by the coordinates in #LINK_LIST.

BLOCK <n>;
    INPUT_X [<METAL> | <MAGNETIC>];
    <Y_min>; <Y_max>;
    <T_min>; <T_max>;
    [<Amplitude>]; [<Faza>];
    [<Eps>];
END_B

BLOCK <n>;
    INPUT_Y [<METAL> | <MAGNETIC>];
    <X_min>; <X_max>;
    <T_min>; <T_max>;
    [<Amplitude>]; [<Faza>];
    [<Eps>];
END_B

Parameters 1–5 (documented in the 2000 manual):

The excitation mode is given by the first parameter:

These conditions must be met so that a single-mode regime of excitation and matching is realised in the input cross-section. The mode the reflected signal is observed in matches the incident one.

The frequency of the RF pulse is set by the FREQ parameter from the parameter section.

How to define an input with no incident wave (receive-only). If there is no incident wave at an input, T_min must be greater than the analysis time from the parameter section (TIME). This is exactly how the second input in the example of section 3 is made: TIME 0.; 5; with INPUT_X …; 200; 201;.

Parameters 6–8 are an extension that is not in the 2000 manual.

Established from the source code (ReadInputX / ReadInputY in src/libs/TMCIndan/TmcRTH_BolckList.cpp; the computation — dAmplitude, dFaza, CalculateYForInput in src/kernels/PlanarRT_H/TmcRTHNodeDiel.cpp):

All three are optional, but parameter 7 is required if parameter 6 is given (otherwise you get the error "Missing separator ';'"). An empty value is allowed: … 0; 200; 1.; ; means an amplitude of 1.0 and the default phase — this is exactly how the first input is written in the current samples/SAMPLE_R/TEST_MAG/EPS4/TEST0.TPL.

The variables t and f make it possible to define the envelope of the pulse instead of a rectangular RF pulse — a Gaussian one, for example.

The code fields that hold these parameters (csVx, csVy, csW) mean something entirely different for moving blocks (RECT_MOVE and the like) — the linear and angular velocities. The comment in src/Include/TmcRTH_BolckList.h (lines 139–141) records both meanings.

To be clarified with the author (K. N. Klimov): parameter 8 (Eps) — is it the ε⁺ increment or ε itself that is given? The check in the code reads (r + 1.0) <= 0.0, which corresponds to the increment (ε = r + 1 > 0).

Examples

Fig. 4.18. A waveguide input (H₁₀) 20 mm wide; it excites the system with an RF pulse 10 ns long.

BLOCK 1;
    INPUT_X METAL; 0; 20; 0; 10;
END_B

Fig. 4.19. An input for a plane wave 2 mm wide, an RF pulse 100 ns long.

BLOCK 1;
    INPUT_X MAGNETIC; 0; 2; 0; 100;
END_B

Fig. 4.20. A waveguide input (H₁₀) 20 mm wide along the X axis. The type is not given — the equivalent of METAL.

BLOCK 1;
    INPUT_Y ; 0; 20; 0; 10;
END_B

Fig. 4.21. An input for a plane wave 2 mm wide along the X axis.

BLOCK 1;
    INPUT_Y MAGNETIC; 0; 2; 0; 100;
END_B

5.6. FILE — reading an ε distribution from a file

BLOCK <n>;
    FILE <file_name>;
    <X_min>; <X_max>;
    <Y_min>; <Y_max>;
END_B

When the ε distribution is computed for large areas of rectangles, evaluating the formula at every node takes a noticeable amount of time. It can be done once, saving the result into a file (the [file_name] parameter of RECT_STAT, section 5.2), and the ready distribution can then be substituted.

The values of X_min, X_max, Y_min, Y_max must be the same as those of the RECT_STAT the file was produced from.

Fig. 4.22. A rectangle of 30×10 mm; the ε⁺ increment is given by a function of the Cartesian coordinates.

First we save the distribution (the first step of the template):

BLOCK 1;
    RECT_STAT [distr]-(2*x/30)^2+(2*y/10)^3; 2; 30; 1; 10;
END_B

Then we use the result from distr.eps:

BLOCK 1;
    FILE distr; 2; 30; 1; 10;
END_B

5.7. The X-mode primitives (plasma)

Besides the ones listed above, the code accepts plasma variants of the primitives. They are not in the 2000 manual; they belong to the X-mode (tmc_rtx.exe) and define the parameters of a magnetised plasma. The full list is defined in src/Include/Tmcgrviw.h (lines 136–157):

The parameters (the coordinates) are the same as those of the corresponding base primitives.

B and Y only take effect together with an overlapping N block — the plasma branch of the computation is switched on when N ≠ 0.

The units are always m⁻³ and Tesla regardless of N_UNIT / B_UNIT — see section 4.9.

A known defect. In the dispatcher src/libs/TMCIndan/TmcRTH_BolckList.cpp the CIRCLE_STAT_N / _B variants are compared by the length of the string CIRCLE_STAT instead of the full length of the tag. For RECT_STAT_* this defect has been fixed (bug #15); for CIRCLE_STAT_* and POLYGON_STAT_* it has not been fixed. For now, use RECT_STAT_*. See ISSUES.md.

The code also defines the primitives of moving blocks — RECT_MOVE, CIRCLE_MOVE, POLYGON_MOVE.

To be clarified with the author (K. N. Klimov): the purpose and syntax of *_MOVE and of the Y parameter (*_STAT_Y). They are not described in the 2000 manual, and there are no working examples for *_MOVE in samples/.

---

6. The link graph section #LINK_LIST

#LINK_LIST
    T <n>; <X0>; <Y0>;
    . . .
#END_LINK

The section serves to specify the geometric position of all the blocks inside the "box". The device, "broken down" into blocks in #TOPOLOGY, is assembled from them here — that is, the procedure of recomposition (joining) of the base elements is performed.

The line T <n>; <X0>; <Y0>; means: place the origin of block <n> at the point of the "box" with the abscissa <X0> and the ordinate <Y0>.

The section is required, and every block from #TOPOLOGY must have exactly one matching line.

The rules for overlapping blocks:

1. Blocks may overlap and intersect each other.
2. Inputs must not intersect (INPUT_X, INPUT_Y). The inputs must be on the boundary of the box.
3. If two or more blocks with an ε distribution overlap, the resulting increment in the overlap area is the sum of the increments from each block.
4. METAL, MAGNETIC and ABSORBER areas may overlap areas filled with a dielectric.
5. When metal, a magnetic and an absorber intersect each other, the priority is determined by the order in which the blocks follow in the topology section.

---

7. The output section #OUTPUT

#OUTPUT
    . . .
#END_OUTPUT

Only the name of the output signal file (FILE) is required.

7.1. FILE — the name of the signal file (required, comes first)

FILE <file_name>;

Sets the name of the file the incident and reflected waves are written into for every time sample. The file gets the .t extension and is written into the directory of the template file.

The line is required and must come first in the section. The name must not contain a dot — the code checks this explicitly and reports the error Unresolved simbol '.' in filename.

All the other output files of the step are built from this name (see section 8).

7.2. TOPOLOGY — outputting the geometry

TOPOLOGY;

Optional. If absent, the geometry file is not produced. The file gets the .tt extension.

When the field output (FIELDS) is switched on, TOPOLOGY must be switched on as well — otherwise FieldView will not be able to show the picture.

7.3. FIELDS — outputting the field distribution

FIELDS;

Optional. Switches on the output of the field intensity distribution.

It slows the analysis down considerably. When running a series of computations it is better to switch this flag off.

If the field output mode is on and the synchronisation flag is set, the compute kernel will not compute the next time tick until FieldView has drawn the current field distribution.

The field distribution written into the file is the one for a single time tick (the current one). This matters if you process the file with third-party programs.

7.4. SMATRIX — outputting the scattering matrix

SMATRIX <Sfile>; <expression>; <T_min>; <T_max>;

The scattering matrix is computed by averaging over the time interval T_min … T_max. The interval should be chosen on the steady-state part of the transient.

Example: SMATRIX test1; 10; 4; 5; — write the S-matrix for the frequency of 10 GHz, averaged from 4 to 5 ns.

One point per step. Every #STEP yields one frequency point in the .s. To obtain a frequency response you need a sweep — many steps with different FREQ values writing into the same Sfile (see section 9). If you make a SMATRIX at a single frequency, the .s will contain one point and no curve will be drawn in TMCGROUT — this is not a bug in the program.

7.5. FIELD_DISTRIBUTION and FIELD_DISTRIBUTION_M

FIELD_DISTRIBUTION <file_name>; <freq>; <T_min>; <T_max>;
FIELD_DISTRIBUTION_M <file_name>; <freq>; <T_min>; <T_max>;

An extension that is not in the 2000 manual. They are defined in src/Include/TmcRTH_IndanOutput.h (lines 14–15) and parsed in src/libs/TMCIndan/TmcRTH_IndanOutput.cpp. They save the complex field distribution at a given frequency (the magnitude → .em, the phase → .ef). FIELD_DISTRIBUTION_M is the variant that accumulates in memory (ReadFileDistrInMemory).

It is used, for example, in samples/SAMPLE_R/1/TEST.TPL.

To be clarified with the author (K. N. Klimov): the exact meaning of the difference between FIELD_DISTRIBUTION and FIELD_DISTRIBUTION_M, and the meaning of the 3rd/4th parameters (an averaging interval or step numbers?).

---

8. Which files the kernel creates

The names are built from the base name given by FILE in the #OUTPUT section. The list has been verified against the code (src/libs/TMCIndan/TmcRTH_IndanOutput.cpp, lines 194–204):

FieldView opens the formats *.tf, *.AMP, *.FAZ, *.ex (the IDR_FLDVIETYPE string in the resources). The .tf extension is historical (version 2.0p); the current code does not write it.

To be clarified with the author (K. N. Klimov): the purpose of the .q, .ix and .iy files.

---

9. The preprocessor of the input language

The preprocessor works immediately before the data is read and makes it possible to write macro definitions and macro substitutions, to include the contents of other files and to write data as mathematical expressions. Its functions are similar to those of the C and FORTRAN preprocessors.

Above all it is needed to structure and parametrise the input data — which helps avoid mistakes when entering and modifying it.

9.1. Mathematical expressions

Any numeric parameters may be written as expressions. Expressions may contain integer and real numbers, the names of macro definitions, parentheses, operation signs and functions.

Arithmetic operations:

Mathematical functions:

The arguments of the trigonometric functions are in degrees or radians, depending on ANGLE_UNIT.

The 2000 manual describes the priority of the operations like this: "raising to a power, division, multiplication, subtraction and summation". Note that division is listed before multiplication, and subtraction before addition, which diverges from the commonly accepted equal priority. Do not rely on priority — put the parentheses in explicitly. The expression in the innermost parentheses is evaluated first.

The coordinate variables. When the distribution of the ε increment is defined, the expression may contain:

The program substitutes the values of these variables for the points of the plane by itself.

The input variables. In the Amplitude and Faza parameters of the INPUT_X / INPUT_Y primitives the variables t (the current time) and f (the frequency) are available — see section 5.5.

Note that f means the polar angle in the expressions for ε, but the frequency in the expressions for the amplitude and the phase of an input.

9.2. Macro definitions #define

#define <name>  [par1; par2; ... ; par32;] @ text1(par1 - par32)\\
                                            text2(par1 - par32)\\
                                            text3(par1 - par32)

The naming rules. The name is separated by spaces on both sides and may contain up to 32 characters from the set: the Latin letters A-Z, a-z, the digits 0-9 and the underscore _. All the macro definitions in one template must have unique names.

The replacement text is separated from the name (or the parameters) by a space, the @ sign and one more space. If the text contains several lines, the pair of symbols \\ is added at the end of every line except the last one. The text following \\ is treated as a comment and ignored.

All macro definitions must be placed before the place where they are used.

The main pitfall: a macro is substituted as text

#define  Length @ 38+12
#define  Width @ Length/2
 . . .
    RECT_STAT 3; 0; Length; 0; Width;

The result of the preprocessor's work:

    RECT_STAT 3; 0; 38+12; 0; 38+12/2;

The length will be 50, and the width — 44, not 25! Because 38+12/2 = 38+6 = 44.

The right way is to put the value in parentheses:

#define  Length @ (38+12)
#define  Width @ Length/2

Then Width expands to (38+12)/2 = 25. This is exactly why in all of the author's templates the macro definitions are written as #define L1 @ ( 50.00 ) — with parentheses.

Macros with parameters

#define  Stp  name1; name2; @ name1+name2
#define  Stm  param; @ param*param
. . .
    RECT_STAT 3; 0; (Stm  (Stp 10; 2;);); 0; 40;

The result:

    RECT_STAT 3; 0; 10+2*10+2; 0; 40;

That is, the length will be 32, not 144. This happens because the first and the last parentheses enclosing an actual parameter are replaced by spaces.

If a macro definition used as an actual parameter has actual parameters of its own, it must be enclosed in parentheses.

9.3. Including a file with #include

#include <file_name>

Inserts the contents of the file <file_name> into the text of the template. The included file must be in the directory of the input template.

This is the main structuring technique: the constants are moved into one .h, the description of a step into another.

#include parm.h
 . . .
    BLOCK 1;
        RECT_STAT 3; 0; Length; 0; Width;

where parm.h contains:

#define  Length @ (38+12)
#define  Width @ Length/2

---

10. A frequency sweep: computing at several frequencies

To analyse a system at several frequencies you need to repeat the procedure at every frequency of interest — this is done by adding new #STEP steps. It is most convenient to use macro definitions with parameters for this.

The author's technique: the whole step is wrapped into a macro in a separate .h file, and the .tpl consists of calls of that macro.

The file STEP1.H — the macro of a single step:

#define step1 Freq__; File__; SFile__; Tmin__; Tmax__; @\\
#STEP\\
#PARM\\
 ANGLE_UNIT radian;\\
 FREQ_UNIT GHz;\\
 LONG_UNIT mm;\\
 TIME_UNIT ns;\\
 DELTA W_delta;\\
 TIME 0.; 5;\\
 X_MIN  0.0;\\
 X_MAX L1+L2+L3;\\
 Y_MIN  0.0;\\
 Y_MAX W_waveg;\\
 FREQ  Freq__ ;\\
#END_PARM\\
#TOPOLOGY\\
 BLOCK 1;\\
  INPUT_X   W_type ; -a1/2; a1/2; 0; 200;\\
 END_B\\
 BLOCK 7;\\
  INPUT_X    W_type ; -a1/2; a1/2; 200; 201;\\
 END_B\\
 BLOCK 2;\\
  RECT_STAT W_type ; 0.0; L1+L2+L3; -a1/2-2*W_delta; -a1/2-1*W_delta;\\
 END_B\\
 BLOCK 3;\\
  RECT_STAT W_type ; 0.0;L1+L2+L3; a1/2; a1/2+W_delta;\\
 END_B\\
 BLOCK 5;\\
  RECT_STAT [epsil1](W_eps-1); 0;L2; 0.0; W_waveg;\\
 END_B\\
#END_TOPOLOGY\\
#LINK_LIST\\
 T 1; 0.0; W_waveg/2;\\
 T 2; 0.0; W_waveg/2;\\
 T 3; 0.0; W_waveg/2;\\
 T 5; L1; 0.0;\\
 T 7; L1+L2+L3; W_waveg/2;\\
#END_LINK\\
#OUTPUT\\
 FILE File__;\\
 SMATRIX SFile__; Freq__; Tmin__; Tmax__;\\
! FIELDS;\\
! TOPOLOGY;\\
#END_OUTPUT\\
#END_STEP\\

The template file — a sweep from 10 to 12 GHz with a step of 0.1 GHz:

#TMC_RT_H
#define L1 @ (   50.00)
#define L2 @ (   50.00)
#define L3 @ (   50.00)
#define W_eps @ ( 4.00 )
#define W_waveg @ (  400.00 )
#define W_input @ (  2.00 )
#define W_delta @ (    0.5 )
!#define W_type @ METAL
#define W_type @ MAGNETIC
#define file_S @ test101
#define a1 @ ( W_input )
#include step1.h
step1 10.0; test100; file_S; 4; 5;
step1 10.1; test101; file_S; 4; 5;
step1 10.2; test102; file_S; 4; 5;
…
step1 12.0; test120; file_S; 4; 5;
#EOF

Note the techniques used:

• all the steps write the S-matrix into a single file file_S — this is how the frequency response is accumulated;
• the signal file name is different for every step (test100, test101, …) — otherwise the steps would overwrite each other's files;
• FIELDS and TOPOLOGY are commented out with the ! symbol — during a sweep the field output slows the computation down sharply;
• RECT_STAT [epsil1](W_eps-1) — the ε distribution is computed once and saved into epsil1.eps;
• the line !#define W_type @ METAL is a commented-out alternative; this is how spare variants are kept.

An expected divergence from the analytics. A frequency response computed on a grid is shifted with respect to the exact analytical solution, because the wavelength in the grid differs from the exact value. The program prints this error in the statistics window, and the shift matches it. This is a property of the method, not a bug.

---

11. A worked example: scattering on an inhomogeneous cylinder

The template is in samples/SAMPLE_R/METAL/CIRCLE/RUPOR.TPL.

Fig. 6.1. A system of three horns for studying the scattering on an inhomogeneous dielectric cylinder with a radius of 250 mm. The permittivity of the cylinder depends on the radius: at the boundary it equals 1, at the centre −5.

The central horn radiates the signal, the two side ones receive.

The key places of the template:

#define W_eps @ ( -4 + 4*r/(W_waveg/2)+1 )
…
 BLOCK 104;
  CIRCLE_STAT (W_eps-1); 0; W_waveg/2; 0; 2*3.1415;
 END_B
…
 BLOCK 8;
  RECT_STAT ABSORBER; L_waveg-5*W_delta; L_waveg - 1*W_delta+0.00; 0.0; W_waveg-2*W_delta;
 END_B

Here:

• W_eps is a function of the polar radius r: at the boundary (r = W_waveg/2) it gives 1, at the centre (r = 0) it gives −4 + 1 = −3;
• the block is passed (W_eps-1) — the increment again;
• blocks 8, 9, 10 are the absorbers along the edges of the box, so that the wave is not reflected from the walls. Note how their boundaries are set back from the boundaries of the box by several W_delta — this fulfils the requirement from section 5.2;
• the horns are assembled from RECT_STAT METAL (the walls) and POLYGON_STAT METAL (the apertures), and the same group of blocks is repeated three times with different numbers and placed in #LINK_LIST at different heights (W_waveg/2, W_waveg/4, 3*W_waveg/4).

Fig. 6.2. The distribution of the permittivity as FieldView shows it.

---

12. The table of keywords

Notation: expression — a mathematical expression; expression(x,y,r,f) — an expression in the Cartesian or polar coordinates; n — an integer; < > — a required parameter; [ ] — an optional one.

---

13. Common mistakes

---

14. Sources

The document has been reconstructed from the author's materials in the archive I:\Python Project\Tamic\data Tamic\ and checked against the source code of TMC Suite.

Used:

The figures have been extracted from rt_hplanar.doc (vector WMF → PNG) and live in docs/screenshots/tpl/.

Checked and rejected as not related to TMC Suite:

---

15. Related documents

• docs/user-manual/planar_rt_h.md — the user manual of the H kernel
• docs/user-manual/planar_rt_x.md — the user manual of the X kernel
• docs/user-manual/fieldview.md — viewing the fields and the topology
• docs/user-manual/tmcros.md — viewing the .t signals
• docs/user-manual/tmcgrout.md — viewing the .s S-matrices
• docs/api/libs/prepr.md — the preprocessor API
• docs/api/libs/tmcindan.md — the API of the input language parsing
• ISSUES.md — the known defects

---

16. The "to be clarified with the author (K. N. Klimov)" checklist

1. HEIGHT — was it meant to be a working parameter? At present it is parsed but does not affect the computation (section 4.9). HWVGD_1.TPL contains HEIGHT 0.1;.
2. DELTA_T_MECHANICAL — the same: it calls SetDeltaT(), but the result is not read anywhere.
3. N_UNIT / B_UNIT — the multipliers are not applied. Should they be connected? And are the multipliers themselves correct: cm3 → 0.000001, whereas 1 cm⁻³ = 10⁶ m⁻³ (section 4.9).
4. ReadNUnit writes into csBUnit/rBUnit instead of csNUnit/rNUnit — should it be fixed (section 4.9)?
5. Parameter 8 (Eps) of INPUT_X/INPUT_Y — is it the ε⁺ increment or ε itself? The code checks (r + 1.0) <= 0.0, which points to the increment (section 5.5).
6. FIELD_DISTRIBUTION vs FIELD_DISTRIBUTION_M — what is the difference in meaning, and what do the 3rd and 4th parameters mean (section 7.5)?
7. *_MOVE (the moving blocks) — the syntax and the purpose; there are no working examples (section 5.7).
8. The Y parameter (*_STAT_Y) — its physical meaning (section 5.7).
9. The .q, .ix and .iy files — their purpose (section 8).
10. The priority of the operations in the preprocessor — is division really of a higher priority than multiplication, as the 2000 manual says (section 9.1)?
11. CIRCLE_STAT_* / POLYGON_STAT_* — should the dispatcher be fixed by analogy with bug #15 (section 5.7)?