Enabling/disabling progress bars globally
See original GitHub issueDo you think it could make sense that all progress bars shown in sisl could be disabled/enabled with just one parameter?
E.g. with an env variable SISL_PROGRESSBARS
or some global switch like sisl.progress_bars()
.
Since the plots in sisl.viz
might be a bit of a black box I want to give the option to the user to show the progress bars for some calculations to understand if the code is working or infinitely stuck. However, I don’t want to create an extra setting just for that in every case where there may be a progress bar.
Therefore I thought a global switch could be a neat solution.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Turn off tqdm from application code · Issue #619 - GitHub
Seems very useful when I use this in Jupyter notebooks and want to sometimes disable progress bars globally. 1
Read more >Source code for datasets.utils.tqdm_utils - Hugging Face
[docs]def set_progress_bar_enabled(boolean: bool): """Enable/disable tqdm progress bars.""" global _active _active = bool(boolean).
Read more >How to disable progress bar in Pytorch Lightning
Use the command show_progress_bar=False in Trainer. Share. Share a link to this answer.
Read more >h2o.no_progress: Disable Progress Bar in h2o - Rdrr.io
When specified, disable progress bar only for the evaluation of the expr ... is to show the progress bar), otherwise disable it globally....
Read more >Utility — Ray 3.0.0.dev0 - the Ray documentation
Set whether progress bars are enabled. The default behavior is controlled by the RAY_DATA_DISABLE_PROGRESS_BARS environment variable. By default, it is set to “ ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sure, the only true proposal here was the concept, not the specifics. However you prefer to implement it is fine for me!
Also it sure seems better to include
SHOW
in the env variable name.SISL_SHOW_PROGRESS
sounds good to me!Yeah both efficiency, which shouldn’t do much since the routines having
eta
are heavy by them-selves. But rather making sure that users requests are obeyed. I don’t know… 😉