Sooner-Rover-Team/auto_ros2

Add a parameter for marker missed count

Open

#158 opened on Feb 20, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)Rust (7 forks)auto 404
configurationgood first issuesrc/navigator

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently we have a constant to decide how many times a marker is missed before we decide that us seeing it was a false positive and stop trying to track it. It would be nice to make this a parameter so we can adjust it on run rather than in the code itself.

Constant is called MARKER_MISSED_THRESHOLD

Originally posted by @onkoe in https://github.com/Sooner-Rover-Team/auto_ros2/pull/156#discussion_r2831388615

Contributor guide

Research direction
Find the constant MARKER MISSED THRESHOLD in the codebase and replace it with a configurable parameter.
Tech stack
rust
Domain
autonomous driving
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85