You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Invoke abstracts the loading of a model's state dict and metadata in a class called [`ModelOnDisk`](../invokeai/backend/model_manager/model_on_disk.py). This class loads real model weights. We use it to inspect models and identify them.
26
+
Invoke abstracts the loading of a model's state dict and metadata in a class called [`ModelOnDisk`](../../invokeai/backend/model_manager/model_on_disk.py). This class loads real model weights. We use it to inspect models and identify them.
27
27
28
28
For testing purposes, we create a stripped-down version of model weights that contain only the model structure and metadata for each key, without the actual tensor data. The state dict structure is typically all we need to identify models; the tensors themselves are not needed. This allows us to store test cases in the repo without adding many gigabytes of data.
29
29
@@ -85,7 +85,7 @@ A string indicating the source of the model (e.g. a Hugging Face repo ID or URL)
85
85
- Example HF Repo ID: `"RunDiffusion/Juggernaut-XL-v9"`
86
86
- Example URL: `"https://huggingface.co/XpucT/Deliberate/resolve/main/Deliberate_v5.safetensors"`
87
87
88
-
### `"file_name"`
88
+
####`"file_name"`
89
89
90
90
If the model is a single file (e.g. a `.safetensors` file), this is the name of that file. The test suite will look for this file in the test case directory.
91
91
@@ -95,7 +95,7 @@ If the model is multi-file (e.g. diffusers-style), omit this key or set it to a
95
95
96
96
> The `strip_model.py` script will automatically fill this field in for single-file models.
97
97
98
-
### `"expected_config_attrs"`
98
+
####`"expected_config_attrs"`
99
99
100
100
This field is a dict of expected configuration attributes for the model. It is required for all test cases.
101
101
@@ -112,7 +112,7 @@ Depending on the kind of model, these additional keys may be useful:
112
112
-`"prediction_type"`: The prediction type used by the model. This is the value of the `SchedulerPredictionType` enum.
113
113
-`"variant"`: The variant of the model, if applicable. This is the value of the `ModelVariantType` enum.
114
114
115
-
To see all possible values for these enums, check out their definitions in [`invokeai/backend/model_manager/taxonomy.py`](../invokeai/backend/model_manager/taxonomy.py).
115
+
To see all possible values for these enums, check out their definitions in [`invokeai/backend/model_manager/taxonomy.py`](../../invokeai/backend/model_manager/taxonomy.py).
116
116
117
117
For example, for a SD1.5 main (pipeline) inpainting model in diffusers format, you might have:
118
118
@@ -128,11 +128,11 @@ For example, for a SD1.5 main (pipeline) inpainting model in diffusers format, y
128
128
}
129
129
```
130
130
131
-
### `"notes"`
131
+
####`"notes"`
132
132
133
133
This is an optional string field where you can add any notes or comments about the test case. It can be useful for providing context or explaining any special considerations.
134
134
135
-
### `"override_fields"`
135
+
####`"override_fields"`
136
136
137
137
In some rare cases, we may need to provide additional hints to the identification system to help it identify the model correctly.
0 commit comments