-
Notifications
You must be signed in to change notification settings - Fork 26
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
Disable logging? #64
Comments
Hi @rgokulsm , Sorry for the delay in getting back to you. I'm afraid we currently don't have the option to turn off logging in HyperMapper. We'll keep this in mind for the future. In the meantime, is this preventing you from using HyperMapper or do you have a workaround that avoids these issues you mentioned? |
Apologies fo the delayed reply. I'm okay at my end since I disabled the logger in other tools. But I think it might help hypermapper compatibility in the future to have logging as optional (or some other work around). Another suggestion is to increase the limit on number of trials. The default is max set to 5000. I changed that manually to 1million at my end (I found useful improvements for up to ~50k trials at least). PS: Hypermapper (using random forests) is working great and producing some good results in our work! Thank you :) |
Hi @rgokulsm , Good point, we will remove that limit in the future. Glad to know that HyperMapper is working well for you! |
Hi @arturluis
Is it possible to disable the logging feature? Or is that required to produce all outputs?
It clashes with other libraries (which I use towards the objective function i.e. the one that hypermapper is optimizing). Also the stdout overwriting due to the logging causes some issues, especially in case of errors, requiring that the entire kernel be restarted.
This is not a showstopper though, but simply a nice to have if possible.
Thank you!
The text was updated successfully, but these errors were encountered: