Skip to content

krites dedup

Description

List the near-duplicate / burst clusters krites grouped while culling the shoot — each cluster's kept frame (★) and its demoted siblings (0002 R-DUP-1). It's the inspection view of the burst handling that krites cull applies: bursts are detected by perceptual hash, the best frame of each is kept, and the rest are demoted to maybe and tagged with the burst they belong to.

The clustering itself is deterministic (R-DUP-2) and runs during cull, so the shoot must be culled first; dedup reads the result and reports it. Re-running cull after a manual override keeps your pick as the cluster keeper (R-DUP-3).

Usage

krites dedup [flags]

The shoot is taken from --shoot, or the current working directory if omitted (R-SCOPE-1).

Flags

Flag Description Default
--shoot Shoot directory to scope to the current directory
--profile Assert the shoot's cull profile by name the shoot's profile
--output Output format: text or json text

Examples

krites dedup --shoot ~/shoots/smith-wedding
Shoot "smith-wedding" — 1 burst(s)

  burst of 2 — kept burst-01.jpg
      ★ burst-01.jpg
        burst-02.jpg

Running before krites cull fails cleanly (there are no clusters to report yet).

Notes & current limits

  • dedup reports the clusters from the last cull; it does not re-cluster at a different aggressiveness on its own. Re-clustering on demand (independent of a full cull) arrives with the cached-analysis work (R-GLOBAL-6).

See also

  • krites cull — judges the shoot and forms the bursts.