mit-acl / mit-acl/dynus

Issue with multiagent setup

Open
#8 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
73
Forks
10
PR merge metrics
No merged PRs in 30d

Description

Hi developers, I've tried to run the tmux script for a multiagent setting just to try it out but unfortunately it does not work. More specifically after running the script, I am met up this error:

Image

For a more complete picture, here is the tmux script I ran. It has been modified to just spin up 2 agents for now. Commenting out the shell command for the second agent allows the sim to run just fine, so it is the introduction of the second agent that kills the sim. Commands that spin up more agents have been commented out.

Image

I've tried to the best of my abilities to inspect the urdfs and it seems like the namespacing has been done accurately to avoid any conflicts in gazebo but I might have missed out stuff. It would be great if the team can share how would a multiagent sim be ran. I have also been running this in Docker, following the README instructions and modifying stuff along the way to make things work. I have been successful in running the single agent simulation in easy_forest through both tmuxp and dynus.sh. Thank you for your help

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README instructions and the modified tmux script for two agents, then compare them with the working single-agent runs through tmuxp and dynus.sh. Reproduce the failure in Docker and inspect the reported error alongside the multiagent URDF namespacing. Done means the two-agent simulation starts successfully and the documented setup works without the reported failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.