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

Enable use of constructed Dataset in predict() methods #4546

Closed
jameslamb opened this issue Aug 22, 2021 · 4 comments
Closed

Enable use of constructed Dataset in predict() methods #4546

jameslamb opened this issue Aug 22, 2021 · 4 comments

Comments

@jameslamb
Copy link
Collaborator

Summary

It should be possible to call predict() on a constructed Dataset and get raw predictions.

Note that it is currently possible to get an evaluation (value of metrics) on a constructed dataset in LightGBM's public API. See #4034 (comment).

Motivation

Getting raw predictions can be useful for purposes other than evaluation of how a model performs on some set of metrics.

For example, in LightGBM the predict() method can be used for purposes like analyzing which leaf nodes each sample matches in each tree (pred_leaf). Without the ability to call predict() on a constructed Dataset, doing such analysis requires loading the raw data in memory.

Description

N/A

References

@jameslamb jameslamb changed the title Enable use of constructed dataset in predict() methods Enable use of constructed Dataset in predict() methods Aug 22, 2021
@jameslamb
Copy link
Collaborator Author

I opened this feature request in response to #4034 (comment).

Added it to #2302, per this project's standard practice. If you are interested in contributing this feature, please leave a comment here and maintainers can re-open the issue and answer any questions you have.

tagging @shiyu1994 and @StrikerRUS , in case you want to add any additional details.

@StrikerRUS
Copy link
Collaborator

This is duplicate of #1939.

@jameslamb
Copy link
Collaborator Author

This is duplicate of #1939.

oh! Forgot about that one. Since it isn't in #2302 I didn't think we already had a feature request for it.

I'll add a link to that to the existing item for this feature in #2302.

@github-actions

This comment was marked as off-topic.

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

2 participants