pyronear / pyronear/pyro-annotator
Local↔remote sync for DB-native detection review (pull/push)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 2
Description
Extracted as an orthogonal feature from the DB-native model-assisted detection-review design (docs/specs/2026-07-17-detection-review-db-native-design.md).
Goal
Feed a local pyro-annotator instance from the remote and push reviewed results back, so the DB-native review capability can replace the FiftyOne loop end-to-end. Auto-annotate itself is independent of this (it runs against whatever DB the API points at).
Scope
- Pull: bring
seq_annotation_donesequences into the local DB in a reviewable state (detection annotations present). ReuseREAD_ONLY_SOURCEto leave the remote untouched. - Push: DB→remote, mirroring
apply_fiftyone_reviewsemantics — clean →annotated; issue frames →needs_manual/bbox_annotation. Support--dry-run.
Open detail
Exact pull mechanism to create local detection annotations: clone + locally set the sequence annotation to annotated (triggering PR #150's server-side auto-create), or a dedicated pull path.
Relation
- Prerequisite for fully retiring FiftyOne (the review-capability spec covers provenance + auto-annotate + review UI; this issue covers getting data in/out).
- May graduate to its own design doc if it grows.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/specs/2026-07-17-detection-review-db-native-design.md and trace the existing apply_fiftyone_review flow, including READ_ONLY_SOURCE and PR #150's server-side auto-create behavior. Decide the pull mechanism, then define pull and push behavior for reviewable sequences, dry-run support, and the clean versus issue-frame outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100