-
Notifications
You must be signed in to change notification settings - Fork 549
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
[REVIEW] add logger in cuML C++ #1867
Conversation
…ea-ext-add-logger
… a given level. Useful to cull log-message construction
…d control over logging in dbscan algo
@@ -165,6 +165,14 @@ class Base: | |||
""" | |||
self.handle = cuml.common.handle.Handle() if handle is None else handle | |||
self.verbose = verbose | |||
# NOTE: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue #2052 has been filed for this.
Dbscan looks good to me. |
Great. Since you're ok with this approach, I'll resolve the remaining 2 conversations on this logging thingy and will soon be updating all other algos currently using 'verbose' flag too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is the main PR for all logger-related issues in cuML:
spdlog
-based logging capability in cuML (issue [TASK] [DEBT] Use GLOG in the cuML's back-end #100).*_NO_THROW
macros (issue [FEA] [DEBT] support for CUDA_CHECK_NO_THROW macro #229) using these logging methods. In this process, it also fixes theexit
issue with the cublas/cusolver macros (issue [FEA] [DEBT] Improve CUBLAS_CHECK and CUSOLVER_CHECK macros #240) as well as issue [DEBT] there are 2 cusparse_wrappers.h header files inside ml-prims #1691, as a by-product.*_NO_THROW
macros. This also means it fixes issue [FEA] [DEBT] Move CUBLAS_CHECK and CUSOLVER_CHECK to a headers that can be used in cpp files #239 .Tagging @cjnolet, @dantegd and @JohnZed for discussions. (Guys, needless to say, this can certainly wait until 0.13 release!) Please note that even though the number of files touched is large, not the number of changes aren't, as this only updates the portions of these sources needing logging infra.
PS: Currently, I'm keeping the target branch as 0.13, but will update it to 0.14 once it becomes default.