Do not set --stopping-criterion entropy via CLI in autotune Python example

[oleksandr-pavlyk]

Use Benchmark.set_stopping_criterion("entropy") in the script instead.

This declares correct intent for benchmark to use entropy-criterion by default.

Closes #456

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 741312d1-4f20-4b91-8446-49b20a0dada9

📥 Commits

Reviewing files that changed from the base of the PR and between c184889 and fb56d73.

📒 Files selected for processing (1)

• python/examples/benchmark_result_autotune.py

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Updated benchmark configuration to apply the entropy stopping criterion consistently through the benchmarking API.
  • Removed the obsolete command-line option from subprocess benchmark launches.

Walkthrough

The Python autotuning example removes the entropy stopping criterion from subprocess arguments and configures it through the registered NVBench benchmark.

Changes

Benchmark autotuning

Layer / File(s)	Summary
Configure the benchmark stopping criterion python/examples/benchmark_result_autotune.py	The subprocess no longer receives --stopping-criterion entropy. The registered benchmark now calls set_stopping_criterion("entropy").

Assessment against linked issues

Objective	Addressed	Explanation
Remove the hard-coded --stopping-criterion option from the underlying benchmark invocation and configure entropy through the benchmark API [#456]	✅

Suggested reviewers: naderalawar

---

_{Comment @coderabbitai help to get the list of available commands.}