pyronear / pyronear/pyro-annotator

BBox drawing tool stroke is too thick/opaque, reducing annotation accuracy

Open Beginner friendly
#349 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
1d 2h
Merged PRs (30d)
2

Description

Context & Problem

In the Localize section, when annotating a specific alert using the bbox drawing tool, the stroke thickness and/or opacity is too high.

This makes it difficult to accurately draw the bounding box, especially for small/complex smoks, as the stroke can hide parts of the target area and lead to imprecise box placement.

The issue is not always visible immediately. It can only be noticed later when reviewing the full sequence view, which requires going back and adjusting the annotation.

Impact
  • Creates unnecessary back-and-forth between views to correct annotations.
  • Increases annotation time.
  • Could lead to lower-quality annotations if inaccuracies are not detected.
Expected behavior

The bbox drawing tool should use a thinner and/or more transparent stroke so that the underlying content remains clearly visible while drawing, allowing more precise annotations.

Happy to discuss it :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Localize section at the bbox drawing tool implementation and inspect how its stroke thickness and opacity are configured. Adjust the visual settings so the underlying alert remains visible while drawing, then verify annotations on small or complex smoke targets and in the full sequence view.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.