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
Since many Python users use Jupyter as their IDE, the logging info should be redirected to stdout so the logs don't show up with red background. You can do so by configuring the logger, for example, as follows:
Also, the model is unnecessarily verbose by default. It might not matter much when you run the code via command-line but when you run it via Jupyter it causes issues. A much better approach is to use tqdm. I think a quick fix can be reducing the verbosity by default.
I think if you go with tqdm daily is fine. Otherwise, I think monthly or yearly works better as you said. I wonder if you tested the impact of logging on the performance? Since IO can sometimes affect the performance significantly, depending on the time each time-step takes.
Since many Python users use Jupyter as their IDE, the logging info should be redirected to
stdout
so the logs don't show up with red background. You can do so by configuring the logger, for example, as follows:Also, the model is unnecessarily verbose by default. It might not matter much when you run the code via command-line but when you run it via Jupyter it causes issues. A much better approach is to use
tqdm
. I think a quick fix can be reducing the verbosity by default.EDIT: Reference to openjournals/joss-reviews#3221
The text was updated successfully, but these errors were encountered: