Add supported CPU/GPU operators to API docs and update docstrings #5239
Conversation
| @@ -341,6 +341,10 @@ class HDBSCAN(UniversalBase, ClusterMixin, CMajorInputTagMixin): | |||
| (and often will) lead to some points being assigned different | |||
| cluster labels between the two implementations. | |||
|
|
|||
| This estimator supports cuML's experimental device selection capabilities. | |||
There was a problem hiding this comment.
@beckernick I'll comment again just so it's in my "reviewed" list. Feel free to delete your comment after that.
Should we maybe automatically add this comment via a common decorator? Something like @device_interop_enabled ? This would also allow us to (maybe at a later stage) set some flag that helps with testing. This could of course be done in a follow-up to not block this PR.
There was a problem hiding this comment.
Thanks! I agree. Doc utilities for this kind of behavior is a great idea.
There was a problem hiding this comment.
It can be added to https://github.com/rapidsai/cuml/blob/branch-23.04/python/cuml/common/doc_utils.py, @beckernick could you open an issue to do it in a follow up? Thanks!
|
/merge |
This PR:
Module Configurationsection of the API documentation (next to the section on Verbosity Levels). As device selection capabilities can be configured, this feels like a reasonable locationThis closes #5143 and closes #5144
This is a replacement for #5150