Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Functionality #53

Closed
18 tasks
schalkdaniel opened this issue Oct 12, 2018 · 10 comments
Closed
18 tasks

Missing Functionality #53

schalkdaniel opened this issue Oct 12, 2018 · 10 comments

Comments

@schalkdaniel
Copy link

schalkdaniel commented Oct 12, 2018

  • Dimension reduction
    • Feature selection
    • Filtering
    • Ensemble filters
  • Plots:
    • ROC/Threshold
    • Benchmark Plots
    • Learner Prediction
    • Calibration
    • Learning Curves
  • Tasks:
    • Cost sensitive
    • Anomaly
    • Multi Output
    • Stacking
    • FDA
    • Survival
    • Clustering
    • Forecasting
    • Spatial (i.e. coordinates)
  • Resampling
    • Spatial CV
@mllg
Copy link
Sponsor Member

mllg commented Oct 17, 2018

I guess most of this should go into extra packages.

@berndbischl
Copy link
Sponsor Member

berndbischl commented Oct 17, 2018

I guess most of this should go into extra packages.

yes of course. but at least I wanted to collect an overview for now what the initial release of mlr3 would not cover. so we can plan ahead

@AtharKharal
Copy link

Deep Feature Synthesis may also be added. We have featuretoolsR package/repo on github now.

@AtharKharal
Copy link

DFS => FeatureSelection => mlrCPO => (mlr+mlrHyperopt) => iml

add data.table as topping

@berndbischl
Copy link
Sponsor Member

DFS => FeatureSelection => mlrCPO => (mlr+mlrHyperopt) => iml

i am not sure what this post means exactly, can you please elaborate? also what is your interest here?

@AtharKharal
Copy link

this is how i m working these days i.e. my workflow. i wrote this to propose an ideal/complete workflow. i use data.table for pre-DFS munging and cleaning as well. Out of my liking for mlr, i wish this is how mlr3 should be developed, if possible.
use of iml (and other likes) may enrich general human knowledge itself by providing much needed insights. Mere prediction, to me, is a half benefit of ML. For any field enrichment and advancement may be helped by iml-like insights returned back to theoreticians of the field; the fuller benefit of ML.

@berndbischl
Copy link
Sponsor Member

Ok 😀 but you have to add some text, in general to explain this to us. But this kind of "package combination" is exactly what we envision too

@pat-s
Copy link
Member

pat-s commented Nov 15, 2018

@mllg I just added spatial CV to the list. I currently try to bring all people that created spatial resampling methods in science together with the aim of implementing all of the existing methods in mlr3.

How can we get the coordinates into the task in mlr3? Should I guess I should open a separate issue for it.

@mllg
Copy link
Sponsor Member

mllg commented Nov 16, 2018

How can we get the coordinates into the task in mlr3? Should I guess I should open a separate issue for it.

You need to explain to me what exactly you need. I hope that you can just specialize a task and set column roles accordingly. We should arrange a call to talk about this.

I guess it would be best to put the spatial stuff in an extra package? mlr3spatial? This could include the specialized task, extra resampling measures, learners and performance measures.

@mllg
Copy link
Sponsor Member

mllg commented Nov 16, 2018

I've created a wiki page to organize extensions as I don't think that this issue is very well suited for this.

https://github.com/mlr-org/mlr3/wiki/Extension-Packages

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants