You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently testing the glm algorithm. Particularly, I am validating the output of the dglm function. When it is being run, it prints a lot of information. For example:
DEBUG [18:57:00.948] Initializing...
INFO [18:57:00.951]
INFO [18:57:00.953] ###############################################
INFO [18:57:00.956] # Starting iteration 0
INFO [18:57:00.958] ###############################################
INFO [18:57:00.960]
INFO [18:57:00.963] 0.1 - RPC Node Beta
DEBUG [18:57:00.966] ** Mocking call to "node_beta" **
DEBUG [18:57:00.969] Regular call
DEBUG [18:57:00.972] there are 3 datasets ..
...
Usually such output is very useful. However, it would be nice to have an additional parameterverbose that could allow hiding such information. This would be particularly useful when testing, since not all the time I want to see such a long output.
I would suggest that it defaults to True. Such functionality could also be added to all algorithms.
The text was updated successfully, but these errors were encountered:
I am currently testing the
glm
algorithm. Particularly, I am validating the output of thedglm
function. When it is being run, it prints a lot of information. For example:Usually such output is very useful. However, it would be nice to have an additional parameter
verbose
that could allow hiding such information. This would be particularly useful when testing, since not all the time I want to see such a long output.I would suggest that it defaults to
True
. Such functionality could also be added to all algorithms.The text was updated successfully, but these errors were encountered: