Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Model Merging UI #144

Open
hipsterusername opened this issue Jul 7, 2024 · 0 comments
Open

Model Merging UI #144

hipsterusername opened this issue Jul 7, 2024 · 0 comments

Comments

@hipsterusername
Copy link
Member

Summary

Model merging (and related functions) allow users to manipulate the model weights of various models without directly training the model. This functionality is supported in Invoke-training with scripts, but does not have direct Interface elements to interact with these capabilities.

Supported capabilities:

  • Base Model Merging: Selecting two models to merge the weights. This includes merging mechanisms like TIES/DARE (task models)
  • LoRA + Base Model Merging: Selecting N LoRAs to merge with a Base Model
  • Model Extraction: This selects a trained model, as well as a base model, and extracts the training as a LoRA.

Related scripts can be found in src/invoke_training/model_merge/scripts.

Users should have a new interface in addition to datasets/training that allows the user to leverage the above. The interface from the training tabs can be used as a base for UI layout/reference.

There are a lot of UX improvement opportunities generally across the training application (better template management, file path usage, etc.), which could be incorporated.

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

No branches or pull requests

1 participant