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

Key for metric doesn't seem to be correct #11320

Open
astro-kevin opened this issue Mar 10, 2025 · 3 comments
Open

Key for metric doesn't seem to be correct #11320

astro-kevin opened this issue Mar 10, 2025 · 3 comments

Comments

@astro-kevin
Copy link

I'm trying to use Ray to do a Hyperparameter search via the sklearn API. In there, one of the callback function RayTrainReportCallback requires the key of the XGBoost metric. Since I'm using XGBoostRegressor, I would think the key should be validation_0-rmse. But this, and all other variations of that throw a key error.

Can someone tell me what the correct key should be, or at least how to reveal the dictionary of metrics?

@trivialfis
Copy link
Member

Could you please open the issue in xgboost_ray? I'm not familiar with the ray interface.

@astro-kevin
Copy link
Author

I don't believe xgboost_ray is still supported. I have been having trouble using that package (which you'll see the latest issue being created by me too). I've since moved to use xgboost (with the sklearn API) with ray/ray-tune. Since that requires access to a key for a metric in xgboost, it should belong to the xgboost repo? I can open an issue in ray too, but I don't know if this belongs there more.

@trivialfis
Copy link
Member

Could you please share a snippet that I can run and debug? I need a starting point to see what's happening.

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