You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenarios that should have a specific duration of time to complete should be able to declare that amount of time in the definition of the scenario. This should either be possible through the scenario or the agent missions.
I believe that the agent interface should be able to choose if to respect the scenario time limit or not.
Proposal
I would propose the following for a mission-related ending:
For the agent interface I would propose the following solution:
# Default to 10.5 seconds if not defined in scenarioagent_interface=AgentInterface.from_type(AgentType.Buddha, simulation_time_limit=TimeLimitSec(default=10.5))
# Always 10.5 seconds.agent_interface=AgentInterface.from_type(AgentType.Buddha, simulation_time_limit=TimeLimitSec(10.5, use_scenario=False))
# Go for 1000 steps instead (existing)agent_interface=AgentInterface.from_type(AgentType.Buddha, max_episode_steps=1000, simulation_time_limit=False)
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Gamenot
changed the title
[Feature request] Define terminal time condition in scenario definition
[Feature request] [SStudio] Define terminal scenario time condition
Apr 28, 2023
Motivation
Scenarios that should have a specific duration of time to complete should be able to declare that amount of time in the definition of the scenario. This should either be possible through the scenario or the agent missions.
I believe that the agent interface should be able to choose if to respect the scenario time limit or not.
Proposal
I would propose the following for a mission-related ending:
scenarios/sumo/figure_eight/scenario.py
examples/control/laner.py
For the agent interface I would propose the following solution:
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: