Skip to content

Enable Rich Progress Bar/Model Summary if Rich is available #9580

@SeanNaren

Description

@SeanNaren
Contributor

🚀 Feature

Currently we have the Rich Progress Bar/Summary in Lightning. However, we only enable it if the user passes the Rich Progress Bar Callback to the Trainer manually.

I see a few options, based on what we'd like to go for in the future:

  1. Enable the Rich Progress Bar/Model Summary if Rich is available (@ananthsub mentioned that we might need to check for Rich 10+ Add RichModelSummary callback #9546 (comment))
  2. Put the Rich Progress Bar/Summary in Bolts. This means we can only enable the Rich Progress Bar if Bolts is installed (and a version that contains the progress bar)
  3. Keep as is

Personally I'm a big fan of 1 as it gives users a nice new progress bar/model summary to look at, which would be nice for a new release! All the user needs to do is pip install rich -U.

If you have other alternatives please put below! Also please let me know which options you'd like

cc @Borda @justusschock @kaushikb11 @rohitgr7

Activity

self-assigned this
on Sep 17, 2021
awaelchli

awaelchli commented on Sep 17, 2021

@awaelchli
Contributor

I have the impression that the Lightning team is very pleased with the rich progress and visualizations and it would be a shame if it went unnoticed by users. Therefore I want to vote for 1 and 2 and I have no preference for either.

kaushikb11

kaushikb11 commented on Sep 17, 2021

@kaushikb11
Contributor

Option 1 ftw! I vote for 1. Also, we should raise a warning if the installed Rich version is < 10.
And we need to ramp up our tests for RichProgressBar as we are planning to have it as default. Could start by getting inspired by this.

rohitgr7

rohitgr7 commented on Sep 17, 2021

@rohitgr7
Contributor

+1 for 1

rohitgr7

rohitgr7 commented on Sep 18, 2021

@rohitgr7
Contributor

also, why not do a small poll on #general for this? let's see what users want. you can put some screenshots over there for convenience. Also rich might be a better solution to fix some issues like this one

deleted a comment from stale on Apr 17, 2023
reopened this on Apr 17, 2023
added and removed on Apr 17, 2023
added a commit that references this issue on Jun 12, 2025
2ce0191
added 2 commits that reference this issue on Jun 12, 2025
f27f263
de27bfe
added a commit that references this issue on Jul 19, 2025
6bccd9d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureIs an improvement or enhancementgood first issueGood for newcomersplGeneric label for PyTorch Lightning packageprogress bar: rich

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @awaelchli@Borda@SeanNaren@carmocca@rohitgr7

      Issue actions

        Enable Rich Progress Bar/Model Summary if Rich is available · Issue #9580 · Lightning-AI/pytorch-lightning