Qengineering / Qengineering/ByteTrack_with_labels
Why are the top and left coordinates swapped in Update
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
if (objects.size() > 0)
{
for(size_t i = 0; i < objects.size(); i++){
Ttlwh a;
a.t=objects[i].rect.x;
a.l=objects[i].rect.y;
a.w=objects[i].rect.width;
a.h=objects[i].rect.height;
float score = objects[i].prob;
int obj_id = objects[i].label;
STrack strack(a, score, obj_id, this);
if (score >= track_thresh) detections.push_back(strack);
else detections_low.push_back(strack);
}
}
More specifically
a.t=objects[i].rect.x;
a.l=objects[i].rect.y;
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 in the Update code containing the shown object-to-Ttlwh assignments and inspect the definitions of Ttlwh and objects[i].rect. Compare the coordinate conventions for x, y, top, and left, then verify the resulting tracking boxes with the repository's object-tracking behavior. Done means the assignments use the intended coordinate order and any correction is validated without swapping width or height.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100