Correct the with_face_dpe note
Browse files
README.md
CHANGED
|
@@ -82,12 +82,13 @@ Three things fail quietly rather than loudly, so they are worth stating plainly:
|
|
| 82 |
2. **Give every capture its own `dataset.cache_dir`.** Decoded frames are named
|
| 83 |
`cam%02d/%08d.jpg` with no capture in the path, so a shared cache would serve P1C1's
|
| 84 |
frame 110 for P1C2's frame 110.
|
| 85 |
-
3. **For `P1_dpe`,
|
| 86 |
-
|
| 87 |
-
|
|
|
|
|
|
|
| 88 |
|
| 89 |
-
For `P1_dpe`, swap the face config to `configs/dreams/p1_face_A_dpe.yaml`
|
| 90 |
-
override.
|
| 91 |
|
| 92 |
## Training setup
|
| 93 |
|
|
|
|
| 82 |
2. **Give every capture its own `dataset.cache_dir`.** Decoded frames are named
|
| 83 |
`cam%02d/%08d.jpg` with no capture in the path, so a shared cache would serve P1C1's
|
| 84 |
frame 110 for P1C2's frame 110.
|
| 85 |
+
3. **For `P1_dpe`, `dataset.with_face_dpe` must point at the session you are driving
|
| 86 |
+
with**, not the one it was trained on. These avatars store it as the *relative* value
|
| 87 |
+
`dpe`, and the loader resolves relative paths against `dat_dir`, so they follow
|
| 88 |
+
`--dat_dir` on their own. A config saved by your own training run holds an absolute path
|
| 89 |
+
to the training session's codes instead, and there you must override it.
|
| 90 |
|
| 91 |
+
For `P1_dpe`, swap the face config to `configs/dreams/p1_face_A_dpe.yaml`.
|
|
|
|
| 92 |
|
| 93 |
## Training setup
|
| 94 |
|