Skip to content

Refactor FNet and CVT output tracing - #43996

Closed
beelapranay wants to merge 1 commit into
huggingface:mainfrom
beelapranay:fnet-cvt-output-tracing
Closed

beelapranay wants to merge 1 commit into
huggingface:mainfrom
beelapranay:fnet-cvt-output-tracing

Conversation

@beelapranay

Copy link
Copy Markdown

What does this PR do?

Refactors FNet and CVT output tracing to use the standardized decorators where appropriate.

  1. FNet now uses @capture_outputs with _can_record_outputs to collect hidden states.
  2. CVT keeps manual hidden-state collection to preserve vision-model semantics.
  3. Wrapper heads use @can_return_tuple to simplify return_dict handling.

Fixes #43979

Before submitting

Who can review?

@molbap @ArthurZucker

@github-actions

Copy link
Copy Markdown
Contributor

[For maintainers] Suggested jobs to run (before merge)

run-slow: cvt, fnet

@ArthurZucker

Copy link
Copy Markdown
Collaborator

Thanks for the refactor, @beelapranay! The #43979 call to contributions was closed shortly after this was opened and we couldn't review the many PRs it produced, so I'm closing this one. Sorry it didn't get looked at in time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Call to contributions: refactor output tracing in transformers

2 participants