Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Goal-condition/mission of social/hijacked agents #257

Closed
2 tasks done
Nickniyihan opened this issue Dec 2, 2020 · 2 comments
Closed
2 tasks done

Goal-condition/mission of social/hijacked agents #257

Nickniyihan opened this issue Dec 2, 2020 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@Nickniyihan
Copy link
Collaborator

Nickniyihan commented Dec 2, 2020

  • Does hijacked bubble agents have mission or goal of each vehicle like social_agent_mission?
  • Does individual sumo vehicle have mission or goal that expose to user? What's the relationship with traffic definition?
  • How does sumo vehicle redefine a goal or mission when the vehicle is moved out of original planned path?

A potential feature request: To expose goal condition or mission through social agent API, aka. policy observation.

AC:

  • Answer @Nickniyihan 's questions
  • Spin out goal condition feature request
@Gamenot Gamenot self-assigned this Dec 8, 2020
@Gamenot Gamenot added this to the 0.5 milestone Dec 8, 2020
@Gamenot Gamenot added the question Further information is requested label Dec 9, 2020
@Gamenot
Copy link
Collaborator

Gamenot commented Jan 13, 2021

@Nickniyihan Answers to questions are as follows:

  • Does hijacked bubble agents have mission or goal of each vehicle like social_agent_mission?

Currently the social agent constructed by the bubble gets a mission plan that defaults to a goal halfway on the last edge of the route that the traffic vehicle had.

  • Does individual sumo vehicle have mission or goal that expose to user? What's the relationship with traffic definition?

If you have access to the traffic sim you are able to get the goal of the SUMO vehicle, however that should generally not be the case. So the current exposed interface for it is only through scenario studio (sstudio.) The traffic currently formats in the following way:

doc.stag(
"flow",
id="{}-{}-{}-{}".format(
actor.name, flow.id, flow_idx, actor_idx
),
type=actor.id,
route=route.id,
vehsPerHour=flow.rate * (weight / total_weight),
departLane=route.begin[1],
departPos=route.begin[2],
departSpeed=actor.depart_speed,
arrivalLane=route.end[1],
arrivalPos=route.end[2],
begin=flow.begin,
end=flow.end,
)

with the definition of terms here:
https://sumo.dlr.de/docs/Definition_of_Vehicles,_Vehicle_Types,_and_Routes.html

Currently the sstudio API is very heavily influenced by the sumo net.xml traffic and flow specifications.

  • How does sumo vehicle redefine a goal or mission when the vehicle is moved out of original planned path?

SUMO can take a number of actions depending on the setting. As applies to us SUMO can try to take one of two actions: if the original destination is available it may reroute to reach that destination, otherwise it attempts to remove the vehicle. We override by giving a new mission if there is no way to route to its destination.

@Gamenot
Copy link
Collaborator

Gamenot commented Jan 13, 2021

Spun out issue #419.

@Gamenot Gamenot modified the milestones: 0.5, Backlog Jan 27, 2021
@Gamenot Gamenot closed this as completed Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants