1. Background
examples/cityscapes/singletask_learning_bench benchmarks RFNet semantic segmentation under the singletasklearning paradigm on the Cityscapes dataset. All example files actually live under a semantic-segmentation/ subdirectory, but three config files reference each other without that path segment:
semantic-segmentation/benchmarkingjob.yaml → testenv: "./examples/cityscapes/singletask_learning_bench/testenv/testenv.yaml" (missing semantic-segmentation/)
- same file → algorithm
url: "./examples/cityscapes/singletask_learning_bench/testalgorithms/rfnet/rfnet_algorithm.yaml" (same problem)
semantic-segmentation/testenv/testenv.yaml → metric url: "./examples/cityscapes/singletask_learning_bench/testenv/map.py" (same problem)
Running it reproduces the crash immediately, before any model/data code executes:
RuntimeError: not found testenv config file(./examples/cityscapes/singletask_learning_bench/testenv/testenv.yaml) in local.
The example also has no README at all — unlike working examples (e.g. pcb-aoi), which document dataset source and quick-start steps.
2. Goals
- Fix the three path references so
ianvs -f gets past config loading.
- Add a README documenting the Cityscapes dataset source and how to run this example, matching the convention used by verified-runnable examples.
3. Scope
This is distinct from the hardcoded-developer-machine-path bugs already tracked in #440/#515/#436 — those are absolute paths baked in from someone's own machine (e.g. /home/xiebo/...). This is a structural bug in the repo's own relative paths (a missing directory segment), affecting every config file in this example. No open PR currently touches this example.
4. Detailed design
- Architecture: affects Ianvs's Test-Environment Manager (loads
testenv.yaml) and Test-Case Controller (loads the algorithm YAML) — both fail at config-parsing time, before reaching core's actual paradigm/model code.
- Module details: no core changes needed — purely fixing the
url/testenv string values in the three YAML files to include the semantic-segmentation/ segment, plus adding the missing README.
I'll follow this up with a PR shortly.
1. Background
examples/cityscapes/singletask_learning_benchbenchmarks RFNet semantic segmentation under thesingletasklearningparadigm on the Cityscapes dataset. All example files actually live under asemantic-segmentation/subdirectory, but three config files reference each other without that path segment:semantic-segmentation/benchmarkingjob.yaml→testenv: "./examples/cityscapes/singletask_learning_bench/testenv/testenv.yaml"(missingsemantic-segmentation/)url: "./examples/cityscapes/singletask_learning_bench/testalgorithms/rfnet/rfnet_algorithm.yaml"(same problem)semantic-segmentation/testenv/testenv.yaml→ metricurl: "./examples/cityscapes/singletask_learning_bench/testenv/map.py"(same problem)Running it reproduces the crash immediately, before any model/data code executes:
The example also has no README at all — unlike working examples (e.g.
pcb-aoi), which document dataset source and quick-start steps.2. Goals
ianvs -fgets past config loading.3. Scope
This is distinct from the hardcoded-developer-machine-path bugs already tracked in #440/#515/#436 — those are absolute paths baked in from someone's own machine (e.g.
/home/xiebo/...). This is a structural bug in the repo's own relative paths (a missing directory segment), affecting every config file in this example. No open PR currently touches this example.4. Detailed design
testenv.yaml) and Test-Case Controller (loads the algorithm YAML) — both fail at config-parsing time, before reachingcore's actual paradigm/model code.url/testenvstring values in the three YAML files to include thesemantic-segmentation/segment, plus adding the missing README.I'll follow this up with a PR shortly.