-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
gblinear non-determinism #4919
Comments
Could you try providing a seed parameter? |
setting seed still ends up vastly different results for each run (i am updating the sample code) |
gblinear uses the shotgun algorithm by default which is strongly nondeterministic. Try setting "updater":"coord_descent". |
thanks that makes it deterministic, in case you consider gblinear with seed set indeterminism not a bug we cal close this issue |
Closing. I forgot that the shotgun is a thread sanitizer killer. |
@trivialfis imho this should not be closed without at least some fix - people expect the model will be reproducible if they set a seed - an improvement of documentation and perhaps a warning when gblinear is run with user defined seed seem appropriate in this case |
@michalkurka Good point. |
This is documented under xgboost parameters. @michalkurka where would you expect to see this?
|
@RAMitchell This is something I would ideally want to see in the python documentation, eg. here: https://xgboost.readthedocs.io/en/latest/python/python_api.html#xgboost.XGBClassifier I would certainly not expect the default is non-deterministic, IMHO a warning on this page would make sense. |
The last calls of the code below produce very different results for each call. This is not reproducible when using gbtree booster.
The text was updated successfully, but these errors were encountered: