Refactor / Remove the Task Templating Mechanism

[popescu-v]

Description

Currently, the task templating mechanism allows khiops-python to instantiate Khiops scenarios based on input parameters specified through the khiops.core API.

In Khiops 11 there is a JSON-based templating mechanism which does essentially the same thing

Questions/Ideas

• The goal of this issue is to:

  • reduce the templating mechanism to providing a JSON file storing the scenario attributes and pairing it with a scenario template that Khiops Core can consume
  • outsource to Khiops core the template instantiation into scenarios (with all associated error checking).

• We need to see whether and how the scenario templates can be mutualized / centralized between Khiops Core and Khiops Python.

• We also need to see whether the Core API function argument preprocessing can be simplified (passage from None to different default values, etc).

[popescu-v]

Confirm that on the Khiops side the types of the fields are checked.
If not, use the Python type hints on the API side (the types module).

[popescu-v]

We can start by unregistring each task one by one (replace it with a bare-bones Python task dictionary).

[marcboulle]

Tenter de spécifier partout ou c’est possible une valeur par défaut, plutôt que None

A priori, c’est possible partout, sauf pour ‘max_cores’ et ‘memory_limit_mb’

Pour le cas ‘header_line’ et ’field_separator’, la documentation suivante me semble plus intuitive que la version actuelle :

detect_format : bool, default True
If True detects automatically whether the data table file has a header and its field separator. If it is set to False , header_line and field_separator are used
header_line : bool, default True
If True it uses the first line of the data as column names. Ignored if detect_format is True.
field_separator : str, default “\t”
A field separator character “” has the same effect as “\t”. Ignored if detect_format is True.
Avec la signature suivante dans les fonctions impactée
detect_format=True, header_line=True, field_separator=”\t”