(relauncher_tmaster)=
# TMaster

The object inheriting from the `TMaster` class has a supervisor role: it defines items to be 
evaluated, and treats these evaluations. Usually, it is created with a `TDataServer`, and a `TRun` 
(`TEval` implicitly) that is used for evaluations. The `TMaster` retrieves information both:

- from `TDataServer`, it extracts the declaration of the input variables.

- from `TEval`, it extracts extra parameters that will be computed for each item.

We could distinguish two cases depending of the `TDataServer` data:

- if it contains a header and data, the `TMaster` will complete items data by adding information 
(columns). This happens most of the time when considering the pure launching aspect, meaning when 
using the `TLauncher2` object, briefly defined below.

- if it contains only a header, it will be used as items definition parameters. The `TMaster` will 
fill it with its own items (lines and columns). This case happens both for pure the launching aspect, 
given that a {{doe}} will be constructed at some point, but also for optimisation issues.

Disregarding the case, `TMaster` interface defines an abstract method, `solverLoop`, that runs the 
evaluation loop and completes or fills the `TDataServer` data. This method is the one to properly 
start the analysis.

```{toctree}
tmaster/dealing_attributes
tmaster/tlauncher2
```