This guide gives a short introduction about Chemaxon's Trainer Engine.
Trainer Engine offers three interfaces:
The generic workflows of Trainer Engine are summarised in this page.
The GUI of Trainer Engine was built on the concept of the run. A run is a long process that requires several computational resources to yield a result. To create a new run in Trainer Engine, click on the New run button and choose a run type.
The following run types can be created.
Automated model building is a process of descriptor generation and model training runs that yields an array of models with the optimal model with high accuracy. The best model is selected from the generated array of models based on sorting using accuracy parameters.
To run an automated model building, follow the steps below.
1) Upload an input file. The supported file format is .sdf, with labeled data stored in a mandatory sdf field. Also, set the Observed value, Problem type and Target name fields.
2) Automated model building uses the Boruta algorithm for descriptor selection. You can override this manually by enabling the Use advanced configuration option.
3) Set the options of the Data processing and confidentiality section for selecting the best model.
4) Once you set up everything, you can simply run the automated model building by clicking on the Start button. You can also reset the default settings by clicking on the Reset button.
To build your own training models, follow the steps below.
1) Upload an input file. The supported file format is .sdf, with labeled data stored in a mandatory sdf field.
{primary} The list of previously uploaded sdf files are available by clicking on "Past Uploads".
You can also use a pre-generated descriptor set to run a new training. In this case the Description configuration window (see Step 5) remains blank.
2) Select the Observed value field. Please consider the followings when specifying the observed data in the input file.
3) Select the Problem type field. This can be Classification or Regression.
{primary} Trainer Engine is able to auto-detect the machine learning problem type in the input file. Choose Auto-detect to enable this.
4) Add Target name. Target name is used to tag or classify models. Target name can be typed in or selected from a pre-defined list of names. It is also used during automatic name generation.
5) Descriptor and training configurations
Choose the descriptor and training you want to apply from the lists of examples. The lists pop up after clicking on the Show examples part of the configuration windows.
You can also modify the chosen configurations. However, it is recommended to check the example configuration files first. Detailed descriptions are available in the Trainer configuration page.
{info} Earlier versions of Trainer Engine supported JSON as a format of configuration. From v. 3.0 configurations are defined in HJSON format.
6) Start the training
Once you set up everything, you can simply run the training by clicking on the Start training button. You can also reset the default settings by clicking on the Reset button.
To run a prediction on a set or to test a built training model, follow the steps below.
1) Select an input file for prediction. The supported file format is SDF.
{primary} The list of previously uploaded sdf files are available by clicking on "Past Uploads".
{primary} You can also specify the structure identifier of the molecule file. Indices are used as default identifiers.
2) Select the Observed value field.
{info} Selecting observed data is optional. If observed data is present and selected, evaluation metrics are automatically calculated for the prediction.
3) Select a model from the list of built training models.
{primary} Multiple training models can be selected and their runs be executed in one go!
4) Once you set up everything, you can simply run the prediction by clicking on the Start prediction or Start all predictions button.
To create a descriptor set (matrix), follow the steps below.
1) Select an input file for creating descriptors. The supported file format is SDF.
{primary} The list of previously uploaded sdf files are available by clicking on "Past Uploads".
{primary} You can also specify the structure identifier of the molecule file. Indices are used as default identifiers.
2) Select the Observed value field and the Problem type.
{primary} Trainer Engine is able to auto-detect the machine learning problem type in the input file. Choose Auto-detect to enable this.
3) Select the features to be used for descriptor generation. You can choose between automatic and manual feature selection.
{primary} Automatic feature selection uses the Boruta algorithm to choose the best performing descriptors.
{primary} Manual feature selection allows you to select the descriptors from a descriptor configuration file.
4) Name the descriptor set.
5) Once you set up everything, you can simply create the descriptor set by clicking on the Create descriptor set button.
The Runs page lists all previous runs in a table format. Selecting runs from the list add them to the Analyze page for further analysis.
The Columns menu lists all available parameters of a run that can be selected to appear in the table.
A simple text based search on the top of the menu can be used to narrow down the available parameters.
Sorting based on a column value can be run by clicking on the column header.
The Filters section allows different filters to be defined for the list of runs.
Runs can also be filtered based on their status. The following statuses are defined: Running, Waiting, Failed, Orphaned, Cancelled and Success. Only one training run can be in a Running state, all other training runs are put in a Waiting status until the running one finishes or gets cancelled. A run can be cancelled while being in a Waiting or Running state.
{primary} Runs can be archived. Archived runs are not visible, but they persist in the system.
{info} Runs are parallelised to utilise available CPU resources.
The 'Explore runs visually' section gives a plot of different statistical parameters of the runs in their order of appearance.
An underlined run name provides a link to its corresponding Details page. The Details page summarises all data of that run.
The Analyze page allows to compare selected runs and to analyse them in detail. It is a flexible and configurable view that supports visualization, comparison and assessment of model details and accuracy measures.
Trainer REST SWAGGER documentation is available at /swagger/swagger.html
The general documentation of Playground is available here: https://disco.chemaxon.com/calculators/playground/
The Integration tab of the About dialogue in Playground shows the state of the Trainer Engine connection.
If Trainer Engine is connected, production flagged models are shown in the list of calculators, marked with a cloud icon.
The Bulk Prediction icon opens a dialogue to select a Trainer Engine model and upload an sdf file.
The results are available for download after prediction.
Bulk predictions started from Playground are marked as "external runs" and are not listed on the Runs page of Trainer Engine.
The progress, the status and the corresponding log file are available by referencing the run id:
/trainer/#/run/{run id reference}