Skip to content

Binary fast tree doesn't return tree predictor in pigsty #1307

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

Closed
Ivanidzo4ka opened this issue Oct 18, 2018 · 6 comments
Closed

Binary fast tree doesn't return tree predictor in pigsty #1307

Ivanidzo4ka opened this issue Oct 18, 2018 · 6 comments
Assignees
Labels
API Issues pertaining the friendly API bug Something isn't working
Milestone

Comments

@Ivanidzo4ka
Copy link
Contributor

Ivanidzo4ka commented Oct 18, 2018

Action<IPredictorWithFeatureWeights<float>> onFit = null)

It returns IPredictorWithFeatureWeights which I found weird since I expect tree predictor from fast tree.
Regression and Multiclass returns FastTreeRegressionPredictor and FastTreeRankingPredictor which is right.

@Ivanidzo4ka Ivanidzo4ka added bug Something isn't working API Issues pertaining the friendly API labels Oct 18, 2018
@Ivanidzo4ka
Copy link
Contributor Author

@sfilipi any chance you know why?

@sfilipi
Copy link
Member

sfilipi commented Oct 19, 2018

Because that's what the trainer produces...

Similar for LightGBM

I think it is this way because of inheritance. Does it need to get re-worked?

@Ivanidzo4ka
Copy link
Contributor Author

Ivanidzo4ka commented Oct 19, 2018

I don't see any reason to train Tree predictor and get weights object, but maybe I'm just silly. Let's hear our druid.
@TomFinley can you share with us the wisdom of centennial oaks?

@shauheen
Copy link
Contributor

shauheen commented Dec 6, 2018

Poking the druid, @TomFinley

@wschin wschin self-assigned this Feb 1, 2019
@wschin
Copy link
Member

wschin commented Feb 1, 2019

This was rediscovered in #2319. I will fix it. Note that fixing #2378 also fixes this issue.

@TomFinley
Copy link
Contributor

TomFinley commented Feb 4, 2019

I had missed that I was being poked. I have related a distinct but nonetheless related issue of #2378. @wschin brought this issue to my attention, I believe but am not certain that he will write there.

Anyway, I think the idea, which I think @yaeldekel also may have had some thoughts on, was a generic class on the type of model parameters, combined with an (optional) calibration object. Indeed this issue is mightily interfering with my ability to resolve #2251.

@shauheen shauheen added this to the 0219 milestone Feb 8, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Mar 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
API Issues pertaining the friendly API bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants