Commit c9e8542c authored by Mitar's avatar Mitar

Language.

parent 7ad08c10
Pipeline #129042062 failed with stage
in 3 minutes and 57 seconds
## vNEXT
* Added `use_default_values_for_free_hyperparams` flag to `SearchSolutionsRequest`
to precisely the control behavior when a search template contains no placeholders
to precisely control the behavior when a search template contains no placeholders
but free hyper-parameters.
[!168](https://gitlab.com/datadrivendiscovery/ta3ta2-api/-/merge_requests/168)
* Fixed URL validation in Python utils when an allowed directory path
......
......@@ -175,7 +175,7 @@ primitive is used.
Relaxation: Individual systems can relax those restrictions. For example, they might allow
a placeholder step to have postprocessing primitive steps after it. In this case postprocessing
primitives can only transform predictions from a placeholder step into transformed predictions.
Or individual systems might allow primitve steps to have free hyper-parameters a TA2 system
Or individual systems might allow primitive steps to have free hyper-parameters a TA2 system
should tune.
### Fully specified pipelines
......@@ -194,7 +194,7 @@ to convert input value to closest container type value, e.g., GRPC `RAW` list va
be converted to `d3m.container.List` with generated metadata, CSV file read as Pandas
DataFrame should be converted to `d3m.container.DataFrame` with generated metadata.
Individual systems can support also pipelines with all primitives specified,
Individual systems can also support pipelines with all primitives specified,
but with free (available for tuning) hyper-parameters. In this case, TA2 will only tune
hyper-parameters and resulting pipelines will have the same structure as given pipeline,
but hyper-parameter configuration will differ. If such potential behavior of a system is
......
......@@ -199,11 +199,11 @@ message SearchSolutionsRequest {
// always using seed of 0.
int32 random_seed = 11;
// If set to true, during search TA2 is suggested to not do hyper-parameter tuning
// but use their default values. It might be that TA2 operates searches for both
// the pipeline and hyper-parameter values at the same time and flag cannot be easily
// respected, in that case this flag can be ignored by TA2.
// of free hyper-parameters but use their default values. It might be that TA2
// operates searches for both the pipeline and hyper-parameter values at the same
// time and flag cannot be easily respected, in that case this flag can be ignored by TA2.
// When template is provided and contains free hyper-parameters but no placeholders,
// then setting this flag to true means that all for all free hyper-parameters in the
// then setting this flag to true means that for all free hyper-parameters in the
// template default values should be used. This allows TA3 to not have to fix
// values for all free hyper-parameters in the template itself, to obtain a
// fully specified pipelines without free hyper-parameters.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment