Queue 226-frame CT-15 test
This commit is contained in:
@@ -109,6 +109,7 @@ Spectrum's `enabled=false` switch.
|
||||
| CT-B12 | Bypassed + EasyCache + clear VRAM | Best smoke prompt | 2 × 8 | 16s | Planned | — |
|
||||
| CT-B13 | Bypassed + EasyCache + clear VRAM | Best smoke prompt | 2 × 9 | 18s | Planned | — |
|
||||
| CT-B14 | Bypassed + EasyCache + clear VRAM | Longform 30s | 2 × 10 | 20s | Planned | — |
|
||||
| CT-15 | Spectrum + EasyCache + clear VRAM | 226-frame chunks | 2 × 9.4 | 18.8s | **Running** | Prompt `8cecdea2-3a6a-4693-a0df-fdbb399e32f9`; 226 H3 frames/chunk |
|
||||
|
||||
The CT-10–CT-14 sweep isolates individual chunk length: it holds the chunk
|
||||
count at two and increases `chunk_seconds` from 6 through 10. The bypass
|
||||
@@ -149,6 +150,13 @@ samplers, scheduler, upscale settings, tile geometry, and chunk plan. Only the
|
||||
Spectrum path changes. Results should be compared in pairs: CT-01 vs CT-B01,
|
||||
CT-02 vs CT-B02, and so on.
|
||||
|
||||
### CT-15 frame mapping
|
||||
|
||||
The H3 temporal grid requires frame counts of `17k + 5`. 226 is valid, and the
|
||||
node’s 0.1-second precision maps it to `chunk_seconds=9.4`:
|
||||
`round(9.4 × 24) = 226`. CT-15 therefore tests two 226-frame chunks with an
|
||||
expected assembled duration of approximately 18.8 seconds.
|
||||
|
||||
### CT-B01 measured relationship
|
||||
|
||||
CT-B01 was accepted with `dumas-continuum-character.png` and
|
||||
|
||||
Reference in New Issue
Block a user