For consistency with the rest of the MLI codebase, we might want wrapper objects like RegressionTreeModel and RegressionTreeAlgorithm as well as DecisionTreeModel/DecisionTreeAlgorithm and put those in mli.ml.regression and classification respectively. They'd be thin wrappers around DecisionTree.train() (and the common 'tree' module is fine to live in its own area!)