handle NULL
objective in xgb_predict()
#875
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR ought not to be merged before the upcoming 1.0.4 release.
Closes #873!
This PR:
NULL
objectives inxgb_predict()
The reason we need to be able to handle
NULL
objectives is because thexgb.Booster
object will not carry along theobjective
argument in itsparams
slot if's not one of the pre-defined options. Using the example fit and custom objective fn from thexgb.train()
examples:The
objective
parameter is retained, usually:The "more minimal" reprex from the original issue, with this PR installed:
Created on 2023-02-21 with reprex v2.0.2