Add support for WAN 2.2 #278
Merged
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.
Add support for WAN 2.2 model
This PR introduces support for the WAN 2.2 model and refactors the existing pipeline to dynamically handle multiple model versions.
New Model Support (WAN 2.2)
The core logic, configuration, and checkpointing for the WAN 2.2 model are added:
base_wan_27b.yml: New configuration file for the WAN 2.2 (27B) model.wan_pipeline2_2.py: The dedicated processing pipeline for WAN 2.2.wan_checkpointer2_2.py: Handles checkpoint loading/saving specific to the v2.2 architecture.wan_checkpointer2_2_test.py: Tests for wan_checkpointer2_2.pyRefactoring for Multi-Model Support
To allow the system to select between WAN 2.1 and 2.2, several core files were modified:
generate_wan.py: Adds a --model_name flag. This flag is now used to dynamically load the correct configuration file (e.g.,base_wan_14b.ymlorbase_wan_27b.yml).wan_utils.py: Updated all transformer loading functions to include a subfolder parameter.base_wan_14b.yml: Added the model_name parameter to conform to the new configuration standard.Note on Future Work
As a follow-up to this PR, the separate
wan_pipeline.py/wan_pipeline2_2.pyandwan_checkpointer.py/wan_checkpointer2_2.pyfiles will be merged. This current separation is a temporary step to land WAN 2.2 support.We tested the above pipeline for both WAN 2.1 and WAN 2.2 with exact same configurations, and the numbers for both the cases are similar.