Use the same additive LFS rules as main to resolve the shared-file conflict; preserve raw/data content and pending human review. Regression-tested fixes and truthful evidence provenance.
fix(arctic): address review findings and reconcile LFS rules
Regression-tested tools and evidence safeguards; preserve data bytes and pending human review. Reconcile current main LFS rules without changing unrelated dataset content.
Re-derive the candidate .gitattributes from this PR's base commit
The pre-merge check compares this file's non-ARCTIC lines with the base commit's -- what this PR changes -- not with live `main`, which other datasets move while a release stages. An earlier repair had rewritten them from live main to satisfy the older live-main comparison; this restores the base's lines byte for byte and keeps ARCTIC's own paths as the shared-v1.1 glob block. No other dataset's tracking is changed by this.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Authorized by yhl.
28 days ago
Sync the candidate .gitattributes' non-ARCTIC lines with main
The pre-merge check compares this file's non-ARCTIC lines with the live ones; the branch carried a snapshot of main as it was when the candidate PR was opened, and other datasets have since globbed their per-path lines. Non-ARCTIC lines are now byte-identical to main's and ARCTIC's own paths are the glob block. No other dataset's tracking is changed by this.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Authorized by yhl.
Resolve actual file-count limit: replace old ARCTIC candidate tree
Candidate PR: publish the ARCTIC `shared-v1.1` release. **Please review before merging.**
Full local migration: 2973 sequences / 3051 views, validated and audited locally. Nothing
outside `ARCTIC/shared-v1.1` is touched -- `ARCTIC/raw` and `ARCTIC/shared-v1.0` bytes are
unchanged, and no other dataset's files or LFS tracking lines are modified (both checked on
the candidate branch before this PR was opened).
Pushed under yhl's authorization; merging is left to the reviewer.
Two conventions this release carries deliberately, called out here because
`doc/PUBLICATION_PLAN.md` is a hashed file inside the release and could not be edited
without re-validating the 737 GiB tree:
- `doc/validation/` holds 54 sampled per-view review pages (6 sequences x 9 cameras, seed
20261014) plus `index.html` and `V1_1_VALIDATION.json`. They are acceptance evidence,
not training input. The published H2O and dex-ycb releases ship the same kind of pages.
- The release tree ships **no upload script**, p…
