krites reset frame¶
What krites reset frame does¶
Return one frame to its post-ingest (unjudged) state: clear its verdict and
any manual override, and discard its develop edits — straighten, crop, look and
object removals. Use it to undo a
krites verdict override, throw away a frame's edits, or drop
its verdict so the next krites cull re-judges it from scratch.
Usage¶
<name> is the frame's filename as it appears in the shoot manifest (for example
IMG_2043.CR2), not a path.
Flags¶
| Flag | Description | Default |
|---|---|---|
--shoot |
Shoot directory | the current directory |
Plus the global --output text|json.
What it changes on disk¶
| Path | Effect |
|---|---|
.krites/verdicts.yaml |
the frame's entry is removed; the file is rewritten |
.krites/edits/<frame>.yaml |
deleted |
.krites/removals/<frame>/ |
the whole directory is deleted |
Nothing else changes. The original frame, the manifest, the analysis cache, any
saved review and anything already in export/ are all untouched.
What happens when it goes wrong¶
| Situation | Result |
|---|---|
| The frame is not in the shoot manifest | fails with an error naming the frame; nothing is written |
| The frame has no verdict and no edits | succeeds and reports zero changes — a clean no-op |
The current directory is not a shoot and --shoot is omitted |
fails with no krites shoot at … — run 'krites ingest' first |
The removal patches go with it¶
Resetting a frame deletes its cached object-removal patches. Those patches are the
only copies of a generative fill — krites cannot regenerate one from the edit
record, because the record only points at the patch file. Recovering a removal
after a frame reset means running krites remove against the model
again, which needs the removal provider configured and will not reproduce the
previous fill exactly.