This issue is aimed at keeping track of requested features.
Note to developers and contributors: If you plan to actively work to implement a requested feature, re-open the linked issue. Everyone is welcome to work on any of the issues below. For specifics, read the linked issues.
Note to maintainers: All issues with feature requests should be consolidated to this document. Close all new issues with feature requests and create corresponding new entries in the following checklist. (Don't forget to create a link to the closed issue.) This is so that the number of open issues is kept manageable. Also make sure to attach feature-request
label when closing feature requests
min_child_weight
parameter (#2714)feature_names
when slicing DMatrix with slice()
(#3124)ntree_limit = best_ntree_limit
for predictions in scikit-learn API (#3053)sklearn.tree.export_graphviz
(#2981)booster
parameter to XGBoost-Spark (#3209)Single instance prediction was added to JVM package by #3464.
Hello @hcho3 in the forum the ability to define the probability of each feature being selected when col_sample
is being used has been requested a few times recently [1].
If we want to add this as a feature request I could create an issue to track it, and take it up since it doesn't seem too complicated once we agree on a design.
[1] https://discuss.xgboost.ai/t/sampsize-by-strata-in-subsample/281
@thvasilo That would be great. Thanks!
Opened https://github.com/dmlc/xgboost/issues/3754 to track this.
+1 for Multiple output regression
Most helpful comment
+1 for Multiple output regression