Add codebook_dim attribute to DacVectorQuantize for DacResidualVectorQuantize.from_latents() #40665
+54
−0
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
…torQuantize.from_latents
|
[For maintainers] Suggested jobs to run (before merge) run-slow: dac |
|
run-slow: dac |
|
This comment contains run-slow, running the specified jobs: models: ['models/dac'] |
vasqu
approved these changes
Sep 4, 2025
There was a problem hiding this comment.
Thanks a lot @flavioialongo 🤗 gonna merge after docs have been built (nothing to be done on your side)
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This PR fixes an issue where DacResidualVectorQuantize.from_latents required an additional attribute from the DacVectorQuantize class.
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
Your PR will be replied to more quickly if you can figure out the right person to tag with @
@eustlb