Skip to content

libreyolo label – Navigating Radar results with N skips flagged images #958

Closed

Description

@derdobner

Description

After running Label-Error Radar and selecting a flagged image from the results dialog, pressing N navigates through only some of the flagged images. After a few presses, it jumps back to the first result instead of visiting all flagged images.

The results dialog closes when an image is selected, and the Radar button starts a new scan rather than reopening the previous results. This makes reviewing the remaining images inconvenient, especially with large datasets where scanning takes time.

Steps to reproduce

  1. Open a dataset in libreyolo label and run Radar.
  2. Select a flagged image from the results dialog.
  3. Repeatedly press N to navigate to the next flagged image.

Expected behavior

N visits all flagged images in the order shown in the Radar results before wrapping back to the first one. It should also be possible to reopen the results dialog without running another scan.

Actual behavior

Some flagged images are skipped, and navigation can wrap back to the first result after only a few presses.

Possible cause

In commit 89efbe8, Radar sorts the deck by descending score in radar.py. However, nextFlagged() searches that score-sorted deck for the first image ID greater than the current ID. If none is found, it returns to the first deck entry.

For example, given IDs [7, 25, 3, 12, 30, 5] in deck order, navigation starting at 7 follows 7 → 25 → 30 → 7, skipping 3, 12 and 5.

Navigating by the current image's position in the deck instead of comparing numeric IDs should resolve this. A regression test with a deck whose IDs are not in ascending order would help verify the behavior.

Workaround

Run openRadar() in the browser's developer console to reopen the results dialog without rescanning. The dialog displays at most the first 80 entries.

Activity

  1. EHxuban11 commented on Oct 28, 2026

    @EHxuban11
    Contributor

    Hello @derdobner , thank you for these two detailed reports!

    You were right about the cause: N was looking for the next image ID in a list sorted by score, so it skipped images. Now it goes through all the flagged images in the order Radar shows them, worst first, and goes back to the first one at the end.

    All of this is in dev and here is the merged PR #961 . It will ship in the next version (v1.7.0). Let me know if this works for you.

    Thank you again!

  2. added
    awaiting responseFix or answer given; waiting for the reporter to confirm
    and removed on Oct 28, 2026
  3. derdobner commented on Oct 29, 2026

    @derdobner
    Author

    Thanks a lot @EHxuban11. Sounds great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting responseFix or answer given; waiting for the reporter to confirm

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions