Skip to content

Support model merging #110

Description

@psychedelicious

Model merging was removed from the main UI with plans to move that functionality to this repo. It was removed because it wasn't a super popular feature and maintaining the routes and fairly complex form UI didn't make sense given the low demand.

The merging logic itself is pretty straightforward: https://github.com/invoke-ai/InvokeAI/blob/main/invokeai/backend/model_manager/merge.py

I imagine/hope it will be pretty straightforward to add a simple Gradio UI for it.

Related issue from main UI repo: invoke-ai/InvokeAI#6241

@RyanJDick Please correct me if I am wrong, but I think we would be happy to review a PR that adds this functionality to the training app.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions