Description
The MOT17 example is currently non‑functional because multiple internal paths still reference a non‑existent pedestrian_tracking directory. It appears the example directory was renamed to MOT17, but the internal configuration and code files were never updated to reflect this change.
Because Ianvs cannot locate the testenv configurations, algorithm configurations, or metric files, both the tracking and ReID benchmarking jobs will fail immediately upon startup with FileNotFoundError or an equivalent error.
Expected Behavior
All internal paths within examples/MOT17/ should point to ./examples/MOT17/ so the example can run locally.
Steps to Reproduce
- Attempt to run the tracking benchmark job from the root directory:
ianvs -f ./examples/MOT17/multiedge_inference_bench/pedestrian_tracking/tracking_job.yaml
- Or attempt to run the ReID benchmark job:
ianvs -f ./examples/MOT17/multiedge_inference_bench/pedestrian_tracking/reid_job.yaml
- Observe the failure as Ianvs attempts to resolve
./examples/pedestrian_tracking/... and throws a FileNotFoundError or similar.
Affected Files
At least 14 references across the following 8 files need to be updated:
tracking_job.yaml (lines 9, 22)
reid_job.yaml (lines 9, 22)
testenv/reid/testenv.yaml (lines 14, 17, 20, 23, 26)
testenv/tracking/testenv.yaml (lines 14, 17, 20, 23, 26, 29)
testalgorithms/reid/m3l/m3l_algorithm.yaml (line 20)
testalgorithms/tracking/byte_track/byte_track_algorithm.yaml (line 20)
generate_reports.py (line 93)
testenv/reid/cmc.py (line 48)
Proposed Solution
Perform a global find‑and‑replace across examples/MOT17/ to change all instances of:
./examples/pedestrian_tracking/
to:
This will ensure all internal references correctly resolve to the current example directory, allowing both tracking and ReID benchmark jobs to run without path errors.
Let me know if you would like me to go ahead and run the commands to solve this issue on your new fix/update-pedestrian-tracking-paths-to-mot17 branch!
Description
The MOT17 example is currently non‑functional because multiple internal paths still reference a non‑existent
pedestrian_trackingdirectory. It appears the example directory was renamed toMOT17, but the internal configuration and code files were never updated to reflect this change.Because Ianvs cannot locate the
testenvconfigurations, algorithm configurations, or metric files, both the tracking and ReID benchmarking jobs will fail immediately upon startup withFileNotFoundErroror an equivalent error.Expected Behavior
All internal paths within
examples/MOT17/should point to./examples/MOT17/so the example can run locally.Steps to Reproduce
./examples/pedestrian_tracking/...and throws aFileNotFoundErroror similar.Affected Files
At least 14 references across the following 8 files need to be updated:
tracking_job.yaml(lines 9, 22)reid_job.yaml(lines 9, 22)testenv/reid/testenv.yaml(lines 14, 17, 20, 23, 26)testenv/tracking/testenv.yaml(lines 14, 17, 20, 23, 26, 29)testalgorithms/reid/m3l/m3l_algorithm.yaml(line 20)testalgorithms/tracking/byte_track/byte_track_algorithm.yaml(line 20)generate_reports.py(line 93)testenv/reid/cmc.py(line 48)Proposed Solution
Perform a global find‑and‑replace across
examples/MOT17/to change all instances of:to:
This will ensure all internal references correctly resolve to the current example directory, allowing both tracking and ReID benchmark jobs to run without path errors.
Let me know if you would like me to go ahead and run the commands to solve this issue on your new
fix/update-pedestrian-tracking-paths-to-mot17branch!