huawei-noah/SMARTS

[Help Request] A map source for road surface generation can not be resolved from the given reference: `scenarios/sumo/loop/build`.

Open

#2,173 opened on Mar 6, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (220 forks)auto 404
help wanted

Repository metrics

Stars
 (1,129 stars)
PR merge metrics
 (PR metrics pending)

Description

High Level Description

I passed the make sanity test when I tried to run "scl run --envision examples/e3_multi_agent.py scenarios/sumo/loop"

An error occurred: /home/kemove/SMARTS/smarts/core/default_map_builder.py:159: UserWarning: A map source for road surface generation can not be resolved from the given reference: scenarios/sumo/loop/build.

warnings.warn(/home/kemove/SMARTS/smarts/core/default_map_builder.py:159: UserWarning: A map source for road surface generation can not be resolved from the given reference: scenarios/sumo/loop/build/map.

warnings.warn(/home/kemove/SMARTS/smarts/core/default_map_builder.py:159: UserWarning: A map source for road surface generation can not be resolved from the given reference: scenarios/sumo/loop/build/traffic.

warnings.warn(/home/kemove/SMARTS/smarts/core/default_map_builder.py:159: UserWarning: A map source for road surface generation can not be resolved from the given reference: scenarios/sumo/loop/build/social_agents.

I couldn't find the cause and asked for help!!!

Version

SMARTS: 2.0.1 sumo: 1.22.0 lastest

Operating System

No response

Problems

No response

Contributor guide

Research direction
Check the scenario directory structure and ensure that the map source files are generated correctly. Verify that the build directory contains the expected 'map', 'traffic', and 'social agents' subdirectories. Inspect the default map builder.py logic to understand how it resolves references.
Tech stack
python
Domain
aibackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65