Generate the next set of candidates for a Single Objective model

Three values are required for the request body, with additional optional parameters:

1. beta: value balancing exploration (3-5) and exploitation of known good areas (0). Recommend 3
2. opt_sel: binary value defining direction of optimisation. 1 = maximisation, 2 = minimisation
3. data: string of an array of JSON objects defining the model table, including headers
4. config [Optional]: Model table headers as JSON. If config is used, data contains only the data rows without headers, following the same format as described below.
5. explore_mode [Optional, default = True]: Specify if this iteration is to be run in explore mode or not. Explore mode forces suggested candidates to be more than 1% different (when normalised) from existing data points in all input parameter axes.

data detailed definition:

When not using the config parameter to handle the model headers, the data field contains a table, defined row by row, which contains two sections: the headers, defining the model, and the previous trials data. Both the headers and the previous trials data are provided to the API call as a single string.

The table column names are used as the keys to define each row as a JSON object. These JSON objects are then inserted into an array, and the array is converted to a string. This can be achieved in python by converting a Pandas DataFrame to a JSON using record-wise orientation, i.e., df.to_json(orient='records').

The columns names are: Model Name, Input 1, Input 2, ... , Input N, Output 1 The header rows, in order, are: Type, Min, Max, Step, Weight

Every cell within the table must have a value. For Min, Max, and Step, the default value should be 0. For Weight, the default value should be 1. Weight is not used for single objective optimisation requests, but must be included in the table regardless. For the Type fields, the values must be "Input", "Output" or "Output Constraint" (max 1 Output Constraint, unlimited Inputs and Outputs).

Double quotation marks (") should be used within the string, escaped (\") to ensure correct processing in the API. Previous trial data values should be provided as strings, as shown in the example (although providing them as numbers may work fine).

The table below converts into the string shown in the Example section. There are the column titles, followed by 5 rows of headers, followed by a single row of previous trial data. There are two inputs and one output for this particular example model.

200 response