Upload extensions/example/config/config.example.yaml with huggingface_hub
Browse files
extensions/example/config/config.example.yaml
ADDED
|
@@ -0,0 +1,48 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
# Always include at least one example config file to show how to use your extension.
|
| 3 |
+
# use plenty of comments so users know how to use it and what everything does
|
| 4 |
+
|
| 5 |
+
# all extensions will use this job name
|
| 6 |
+
job: extension
|
| 7 |
+
config:
|
| 8 |
+
name: 'my_awesome_merge'
|
| 9 |
+
process:
|
| 10 |
+
# Put your example processes here. This will be passed
|
| 11 |
+
# to your extension process in the config argument.
|
| 12 |
+
# the type MUST match your extension uid
|
| 13 |
+
- type: "example_merge_extension"
|
| 14 |
+
# save path for the merged model
|
| 15 |
+
save_path: "output/merge/[name].safetensors"
|
| 16 |
+
# save type
|
| 17 |
+
dtype: fp16
|
| 18 |
+
# device to run it on
|
| 19 |
+
device: cuda:0
|
| 20 |
+
# input models can only be SD1.x and SD2.x models for this example (currently)
|
| 21 |
+
models_to_merge:
|
| 22 |
+
# weights are relative, total weights will be normalized
|
| 23 |
+
# for example. If you have 2 models with weight 1.0, they will
|
| 24 |
+
# both be weighted 0.5. If you have 1 model with weight 1.0 and
|
| 25 |
+
# another with weight 2.0, the first will be weighted 1/3 and the
|
| 26 |
+
# second will be weighted 2/3
|
| 27 |
+
- name_or_path: "input/model1.safetensors"
|
| 28 |
+
weight: 1.0
|
| 29 |
+
- name_or_path: "input/model2.safetensors"
|
| 30 |
+
weight: 1.0
|
| 31 |
+
- name_or_path: "input/model3.safetensors"
|
| 32 |
+
weight: 0.3
|
| 33 |
+
- name_or_path: "input/model4.safetensors"
|
| 34 |
+
weight: 1.0
|
| 35 |
+
|
| 36 |
+
|
| 37 |
+
# you can put any information you want here, and it will be saved in the model
|
| 38 |
+
# the below is an example. I recommend doing trigger words at a minimum
|
| 39 |
+
# in the metadata. The software will include this plus some other information
|
| 40 |
+
meta:
|
| 41 |
+
name: "[name]" # [name] gets replaced with the name above
|
| 42 |
+
description: A short description of your model
|
| 43 |
+
version: '0.1'
|
| 44 |
+
creator:
|
| 45 |
+
name: Your Name
|
| 46 |
+
email: your@email.com
|
| 47 |
+
website: https://yourwebsite.com
|
| 48 |
+
any: All meta data above is arbitrary, it can be whatever you want.
|