Decision tree work page

Decision tree page looks very complex. However, essential part of its functionality has strong back-end support, so the the Front End complexity is not so hard as one can expect. Essential portion of real difficulties in Front End application support focuses on the same issue as in other work pages: :doc:<status_report>.

The page provides the following functionality issues for work with with all datasets, xl- and ws-<ws-dataset> ones

• Decision tree complex representation with possibility to select any applicable point

• Delayed report of point counts, actual for xl-datasets where count evaluations might be heavy

• Complex of visualization of properties state, in context of current decision point selection, see Status report mechanism (with delays)

• Auxiliary viewing regime, in context of current decision point

• Interactive modification of decision tree, see full reference in Decision Tree modifying actions. Operations of this layer are split onto three categories of operations:

  • INSTR: manipulations with logical structure of the code

  • POINT: creation of new atomic conditions in context of available properties state, and placement of them into the code of decision tree

  • ATOM: tuning atomic conditions in decision tree code

• Operation support:

  • manual edition of decision tree code

  • support decision trees as Solution items in work

  • creation of secondary workspace

In case of ws-dataset the page uses transcript variants as filtration items, otherwise in case of xl-dataset DNA variants are used.

Decision trees are powerful tool of Filtration procedures, they are integrated with other parts of the system by two ways:

• there is always a possibility to create secondary workspace to save result of filtration workspace

• for ws-datasets only: filtration results of all decision trees that are registered as solution items are available in Filtering regime as values of special property Rules.

Interactive modification level (see Decision Tree modifying actions for reference) forms complete functionality to make any meaningful change in decision tree. So there is no need for the user to direct change of Python code of decision tree. It might be useful only for control complex cases of boolean operations.

REST API requests

For support Decision Tree work page:

• dsinfo

  Dataset information

• dtree_set

  Decision tree page setup

• dtree_counts

  Delayed evaluations of item counts for decision tree points

• dtree_stat

  Filtering properties status report for decision tree page

• dtree_check

  Decision tree code check (used for validation of manual code edition)

• dtree_cmp

  Comparison of decision trees

• ds2ws

  Creation of secondary workspace

• see also Status report mechanism (with delays)