Concepts
Tuning
The UI says tuning. Some routes and identifiers still use Tuning. One tuning is a workspace: you configure the problem, choose algorithms, start a run, and inspect those runs.
A blank create is an online tuning. A test tuning ships with a recognizable default name and can open a test report. Copy and import keep the original type.
Four closed-loop steps
- Plan: the algorithm proposes the next action.
- Execute: the action is written through the control API.
- Wait: the machine is judged stable and the parameters are judged in effect.
- Observe: machine state is read in the measurement window, then objectives and constraints are evaluated.
In the UI you configure, start, watch iterations, and read results.
Platform layer and site adaptation layer
The platform layer is the same general software at every site: orchestration, tuning, measurement, query, supervision, and the UI. It does not embed one site’s device list.
The site adaptation layer is the interface between the platform and that site. Driver writes device commands. DataTS collects time series into the store. Devices, point tables, and control entries are configured per site.
VirtualPlant is the built-in virtual plant for integration and test evaluation. The integration closed loop does not go through a field Driver.
Point table, product tree, site
A point table is the Driver or DataTS configuration and measurement points for one device at one site.
The product tree is the installed directory. The marker is the site file conf/sites/site.yml inside that tree.
A site here means the environment where that product tree is already installed. Do not move the product root after install.