Skip to content

update should_use_sparsity() to work with lightgbm - #290

Merged
hfrick merged 2 commits into
mainfrom
sparsity-update
Aug 11, 2025
Merged

hfrick merged 2 commits into
mainfrom
sparsity-update

Conversation

@EmilHvitfeldt

Copy link
Copy Markdown
Member

@hfrick hfrick left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to merge this (yay sparsity!) but wanted to check in with you on one thing: The NEWS entry just refers to lightgbm, but also some of the coefficients for the baseline and other engines change. That's what you want, right?

@EmilHvitfeldt

Copy link
Copy Markdown
Member Author

I'm not loving that the coefficients are different for other models, but that is what happens when we rerun the simulation. So i think it is fine

@hfrick
hfrick merged commit 3472508 into main Aug 11, 2025
14 checks passed
@hfrick
hfrick deleted the sparsity-update branch August 11, 2025 11:12
@github-actions

Copy link
Copy Markdown

This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.

@github-actions github-actions Bot locked and limited conversation to collaborators Aug 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants