tools: a viewer for the recurring-object ledger - #41
Closed
MateoLostanlen wants to merge 1 commit into
Closed
MateoLostanlen wants to merge 1 commit into
MateoLostanlen wants to merge 1 commit into
Conversation
Auditing the ledger meant reading JSON and guessing at images. This shows both at once: pick one of the recurring objects and get every alert it ever fired, the one sequence that entered the dataset badged and expanded first, the annotated boxes in red and the object's frozen anchor — the geometry the IoU match actually runs against — in green. Crops 3x around the anchor by default. These artefacts occupy a couple of percent of the frame, and a full view shows a landscape with no object in it. It reads data/raw/pyro-annotator/ rather than the built pools, so it needs no 17 GB pull: an object's ingested sequence is the folder the export already holds, byte for byte. A second view lists objects on one camera within 5 degrees of each other — nine pairs today. Matching demands azimuth equality, so one artefact filmed at a slightly different pan becomes two objects, each free to draw its own split. Worth seeing before the pool grows enough for that to matter.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A Streamlit app to audit the recurring-object ledger visually, instead of reading JSON and guessing at images.
Objets récurrents — pick one of the 104 artefacts (sidebar, sorted by sightings) and get:
DANS LE DATASETand expanded first, the rest collapsed below;Ledger.matchactually runs IoU against — and a 3x crop around it. Without the crop you get a landscape: these artefacts occupy a couple of percent of the frame.It makes
--max-per-objectconcrete. Onro_00001you see 56 firings of the same road and the single sequence that was kept.Doublons suspects — objects on one camera within 5° of each other, side by side with their splits. Matching demands azimuth equality, so one artefact filmed at a slightly different pan becomes two objects, each free to draw its own split. Nine pairs today; none across splits yet.
Reads
data/raw/pyro-annotator/rather than the built pools, so it works with no 17 GB pull — an object's ingested sequence is the folder the export already holds, byte for byte.Not included, and easy to add if it earns its place: search, filters by type or split, and a view over the 275 unlabelled annotator groups. This one audits the ledger; it does not drive annotation.