Skip to content
This repository was archived by the owner on Jun 22, 2022. It is now read-only.

planning 2018.05.07

Kamil A. Kaczmarek edited this page May 14, 2018 · 17 revisions

notebooks

scope for steps 0.1 (Jun 1st)

  • API design
  • docstrings (all in steps dir) and readthedocs page
  • pip package
  • assertions

in writing

  • Steps Use Cases
  • desired logic of Step behavior and its interface

Questions

data = {'input':
          {
               'X': X_train,
               'y': y_train,
           }
        }

Development

Bugs

Notes

Installation remove graphviz from the projects -> use plotly (refactor) steps-core only few dependencies

API-design nested dicts in input -> simplify interface -> DataStep should merge input_step and input_data into one API piece.

Write down difference and relation between Step and transformer (part of Step) You add input that is never used -> you see it on the graph.

cache_transformer -> persisted_transformer

Do Not transform twice!!!

Question: add single step as input to ensembling.

Clone this wiki locally