Feature Request: Option to disable automatic epoch display in ProgressBar
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- machine-learning
Research direction
Start at ignite.handlers.ProgressBar and trace how desc and bar_format are combined with the automatic epoch text. Compare the proposed show_epoch and description_format approaches against the alignment and dynamic-desc requirements; done means users can disable epoch text without losing desc customization.
Written by the indexing model from the issue text.
Description
Problem
Currently ignite.handlers.ProgressBar automatically appends epoch
information like [epoch/max_epochs] to the description when max_epochs > 1.
Example:
Training [1/4]
Training [2/4]
This behavior can make it difficult to align multiple progress bars
(e.g. trainer and evaluator) or customize the display layout.
Current Workaround
Users can redefine the entire bar_format, but this requires rewriting
the full format string even if they only want to remove the epoch display.
Also, removing {desc} from bar_format disables the dynamic desc
argument from tqdm.
Proposed Solution
Allow users to control how the description is formatted.
Possible approaches:
show_epochboolean flagdescription_formatparameter
Example:
ProgressBar(desc="Training", show_epoch=False)- Dominant language
- Python
- Stars
- 4.8k
- Forks
- 726
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pytorch/ignite
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Numerical stability across running-moment metrics — unified plan (tracking #3662 / #3672 / #3741) Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100