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

Multi-output (multi-target) problems #30

Open
steffiel opened this issue May 11, 2016 · 3 comments
Open

Multi-output (multi-target) problems #30

steffiel opened this issue May 11, 2016 · 3 comments

Comments

@steffiel
Copy link

Hi, is it possible to do something like the multi-output from scikit-learn in Julia? Cause my input matrix has 3 features, and I have 12 different outputs per example.
I tried to train 12 separate trees, but this didn't work.

@ablaom
Copy link
Member

ablaom commented Mar 29, 2023

Multitarget regression is not possible - for regression currently the target must have Float64 type.

@ablaom ablaom changed the title Multi-Output problems Multi-output (multi-target) problems Mar 29, 2023
@ablaom
Copy link
Member

ablaom commented Mar 29, 2023

Copying post of @fipelle from another thread:


Also, it seems that loss is only available for classification trees - not regression trees.

Is it possible to repurpose the existing code for classification trees to run regression tasks? It would be convenient both for

regression tasks with one target and a custom loss, and

multi-target problems (the current implementation for regression trees does not allow for labels that are not Float64 - i.e., single targets).

@ablaom
Copy link
Member

ablaom commented Mar 29, 2023

This is an question here and I have wondered before why classification and regression have separate implementations. I diff'ed the two tree.jl files and found quite a few differences. For example, in classification there are array pre-allocations based on the total number of target classes, something you won't want to do in regression.

My initial guess is that generalizing regression.jl would be more useful than re-purposing classification.jl.

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

No branches or pull requests

2 participants