resolve NameError in generate_reports caused by undefined config_file variable

[ARYANPATEL-BIT]

Description

This PR fixes a bug in the generate_reports.py script for the MOT17 tracking benchmark where a missing configuration file would cause an opaque NameError crash rather than exiting cleanly with the intended error message.

Motivation and Context

Currently, if a user has a misconfigured environment or missing paths, the error handling attempts to print a helpful error message and exit the script. However, the f-string referenced an undefined config_file variable, causing Python to crash with NameError: name 'config_file' is not defined. This makes debugging difficult for users trying to setup the example.

What has been changed

• Replaced the undefined config_file variable with the correct locally scoped variables:
  • Line 77: config_file → tracking_config_file
  • Line 86: config_file → reid_config_file
• Reworded the f-string error messages to make them more natural and clear, explicitly stating which configuration file could not be found locally.

File changed:
examples/MOT17/multiedge_inference_bench/pedestrian_tracking/generate_reports.py

How Has This Been Tested?

• Verified static variable names now correctly reference the instantiated args parameters
• Ensured the script now correctly catches the if not utils.is_local_file(...) condition and triggers a SystemExit with the safe string
• Tested with missing config files - now prints clear error messages and exits gracefully

Notes for Reviewers

This bug was completely blocking error-handling and debugging for the MOT17 multiedge-inference-bench example. The fix is localized to a single file with minimal risk of regressions.

---

Before:

# Line 77
print(f"Could not find tracking config at ({config_file})")  # NameError!
# Line 86  
print(f"Could not find reid config at ({config_file})")     # NameError!

After:

# Line 77
print(f"Could not find tracking config at ({tracking_config_file})")
# Line 86
print(f"Could not find reid config at ({reid_config_file})")

Fixes: #399

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ARYANPATEL-BIT
To complete the pull request process, please assign moorezheng after the PR has been reviewed.
You can assign the PR to them by writing /assign @moorezheng in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ARYANPATEL-BIT]

/assign @MooreZheng

[gemini-code-assist]

Code Review

This pull request fixes NameError exceptions in generate_reports.py by correcting the variable names used in error messages for tracking and ReID benchmarking configuration files. Review feedback indicates that while the NameError is resolved, the script may still encounter a TypeError if the configuration file arguments are missing (None), as the current existence check does not handle null values. It is recommended to explicitly verify that these arguments are provided before checking the filesystem.

[gemini-code-assist]

While this change correctly resolves the NameError, the script will still crash with a TypeError on line 76 if the --tracking_benchmarking_config_file argument is not provided (i.e., it is None). This is because utils.is_local_file(None) calls os.path.isfile(None), which is invalid. This TypeError is then caught by the generic exception handler on line 96, resulting in a confusing error message for the user. Consider adding a check to ensure the argument is provided before verifying its existence on the local filesystem.