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
Merge pull request #336 from bghira/feature/on-demand-vae-cache
by default, we now use the on demand vae cache | selective cache clear by using "image" or "text" as value to preserve the cache | aws: fix mps file loading | fix log level issue with metadata backend
Copy file name to clipboardExpand all lines: OPTIONS.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -41,10 +41,10 @@ This guide provides a user-friendly breakdown of the command-line options availa
41
41
-**What**: When provided, will allow SimpleTuner to ignore differences between the cached config inside the dataset and the current values.
42
42
-**Why**: When SimplerTuner is run for the first time on a dataset, it will create a cache document containing information about everything in that dataset. This includes the dataset config, including its "crop" and "resolution" related configuration values. Changing these arbitrarily or by accident could result in your training jobs crashing randomly, so it's highly recommended to not use this parameter, and instead resolve the differences you'd like to apply in your dataset some other way.
43
43
44
-
### `--vae_cache_behaviour`
44
+
### `--vae_cache_scan_behaviour`
45
45
46
46
-**What**: Configure the behaviour of the integrity scan check.
47
-
-**Why**: A dataset could have incorrect settings applied at multiple points of training, eg. if you accidentally delete the `.json` cache files from your dataset and switch the data backend config to use square images rather than aspect-crops. This will result in an inconsistent data cache, which can be corrected by setting `scan_for_errors` to `true` in your `multidatabackend.json` configuration file. When this scan runs, it relies on the setting of `--vae_cache_behaviour` to determine how to resolve the inconsistency: `recreate` (the default) will remove the offending cache entry so that it can be recreated, and `sync` will update the bucket metadata to reflect the reality of the real training sample. Recommended value: `recreate`.
47
+
-**Why**: A dataset could have incorrect settings applied at multiple points of training, eg. if you accidentally delete the `.json` cache files from your dataset and switch the data backend config to use square images rather than aspect-crops. This will result in an inconsistent data cache, which can be corrected by setting `scan_for_errors` to `true` in your `multidatabackend.json` configuration file. When this scan runs, it relies on the setting of `--vae_cache_scan_behaviour` to determine how to resolve the inconsistency: `recreate` (the default) will remove the offending cache entry so that it can be recreated, and `sync` will update the bucket metadata to reflect the reality of the real training sample. Recommended value: `recreate`.
0 commit comments