alteryx / decision_tree

Decision Tree Tool

Decision_Tree Plugin

This repo contains the Decision_Tree tool in Alteryx. Shown below is a brief description of the contents.

File	Description
Decision_TreeConfig.xml	Configuration for plugin (auto generated)
app.css	Custom style sheet for Gui.html
Macros/	Macro backend
Extras/	Gui, Tests, Samples and Help

Development

Use branches to work on features and bug fixes. Commit often. Send a PR to the upstream repo to merge your changes back in. Make sure to sync your clone with the upstream repo before sending a PR, so that merge conflicts are avoided.

The source files that will be modified directly include

1. Macros/Decision_Tree.yxmc (backend)
2. Macros/Decision_Tree1.R (backend)
3. Extras/Gui/overrides.yaml (gui)
4. Extras/Gui/layout.html (gui)
5. Extras/Gui/App/src/* (gui)

Whenever you manipulate one of these source files, you can run the createPluginFromMacro() function shown below to update the plugin and then run copyHtmlPlugin to install it in Alteryx. Make sure that your working directory is the plugin directory and also remember to set options(alterx.path = <path to alteryx directory>) before the install.

library(AlteryxRhelper)
options(alteryx.path = <path to alteryx>)
createPluginFromMacro()
copyHtmlPlugin()

decision_tree's Issues

UI Enhancements

CheckList

• Replace radio buttons with toggle bars wherever appropriate.
• Style accordion panels to be consistent with the formula tool.
• Persist page, tab and accordion selected.
• Replace multi-field selector widget with a list-box based multi-field selector.
• Update ui to indicate to user that they can click on a label to get help.
• Add intro.js based on-demand help.

Incorrect cp value reported in static report.

Noticed a rather obscure bug in the static report. When, the user sets the tuning parameter cp to auto, it is given an initial value of 1e-5 so that a very bushy tree is grown. Subsequently, the value of cp used is the one that results in the lowest cross validation error. This update is not reflected in the model call reported in the static output.

Refresh UI

There are several ways to go about refreshing this UI. Some components to think about include:

1. Tabs
2. Accordions
3. Popovers

This is a moderately complex UI for us to use as the basis to come up with a set of ideas that we can reuse.

Redesign cost parameter UI

I was thinking of a more elegant interface for the cost parameter. The idea is to add a checkbox that would allow the user to set a parameter.

This would necessitate the addition of some extra logic in the backend.

config <- list(
  cp = ...,               # existing cost parameter 
  set_cp = ...          # value of the new checkbox added
)
config$cp = if (config$set_cp) config$cp else 'Auto'

@piguy314159265 What do you think about this?