Reset is currently being called when instantiating problems, which causes weird behaviors. Also, users are not aware that you should, in general, call reset in between optimizations/simulations.
I believe we should improve the current documentation to make this clear and remove the call to reset in __init__
Also, update the paper before it's too late :)
Reset is currently being called when instantiating problems, which causes weird behaviors. Also, users are not aware that you should, in general, call reset in between optimizations/simulations.
I believe we should improve the current documentation to make this clear and remove the call to reset in
__init__Also, update the paper before it's too late :)