Unify the Progress classes #1668
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
cyrjano
force-pushed
the
export-D87560189
branch
from
e2164f6 to
420952e
Compare
cyrjano
added a commit
to cyrjano/captum
that referenced
this pull request
Nov 20, 2025
Summary: This diff aims to unify the Progress classes used in Captum. The changes include updating the dependencies and adding a new protocol for the base progress bar interface. The diff also includes changes to the feature_ablation.py file to use the new progress class. Differential Revision: D87560189
cyrjano
added a commit
to cyrjano/captum
that referenced
this pull request
Nov 24, 2025
Summary: This diff aims to unify the Progress classes used in Captum. The changes include updating the dependencies and adding a new protocol for the base progress bar interface. The diff also includes changes to the feature_ablation.py file to use the new progress class. Reviewed By: craymichael Differential Revision: D87560189
cyrjano
force-pushed
the
export-D87560189
branch
from
420952e to
7815609
Compare
cyrjano
added a commit
to cyrjano/captum
that referenced
this pull request
Nov 24, 2025
Summary: This diff aims to unify the Progress classes used in Captum. The changes include updating the dependencies and adding a new protocol for the base progress bar interface. The diff also includes changes to the feature_ablation.py file to use the new progress class. Reviewed By: craymichael Differential Revision: D87560189
cyrjano
force-pushed
the
export-D87560189
branch
from
7815609 to
448d241
Compare
Summary: This diff aims to unify the Progress classes used in Captum. The changes include updating the dependencies and adding a new protocol for the base progress bar interface. The diff also includes changes to the feature_ablation.py file to use the new progress class. Reviewed By: craymichael Differential Revision: D87560189
cyrjano
force-pushed
the
export-D87560189
branch
from
448d241 to
6d1f0a7
Compare
Contributor
|
This pull request has been merged in daad127. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary: This diff aims to unify the Progress classes used in Captum. The changes include updating the dependencies and adding a new protocol for the base progress bar interface. The diff also includes changes to the feature_ablation.py file to use the new progress class.
Differential Revision: D87560189