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

Change map #3

Open
wants to merge 4 commits into
base: onr-transition
Choose a base branch
from
Open

Change map #3

wants to merge 4 commits into from

Conversation

schmerl
Copy link

@schmerl schmerl commented Aug 17, 2021

This PR is meant to be used for illustrative purposes to show what needs to be done to change various aspects of the mission for the mobile robot example.

==================DO NOT MERGE THIS PR===================

The PR has two example of how someone might change a mission:

  1. Slight tweaks to the map that that remove some of the edges
  2. An entirely different map and a new mission.

To run the new mission, you would need to rebuild the image and issue:

> docker run -v <your-gurobi-license>:/opt/gurobi/ --rm -it cmuable/xplanning -l 70 mobilerobot mission-weh.json

@@ -198,7 +198,6 @@
"y": 5.33
},
"connected-to": [
"L26",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing a connection in the map. Need to remove from 'connected-to' at both ends.

@@ -508,11 +506,6 @@
"to-id": "L31",
"from-id": "L29"
},
{
"occlusion": "PARTIALLY_OCCLUDED",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the occlusion data to add sparse obstacles between LX5 and L26,

@@ -0,0 +1,439 @@
{
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A completely new map (based on data we had for another building at CMU).

@@ -0,0 +1,27 @@
{
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A completely new mission.

"goal-id": "l35",
"preference-info": [
{
"scaling-const": 0.5,
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, the preference scaling is a bit more understandable. We say the relative weights between time, collision, and intrusiveness are 0.5, 0.4, 0.1. Meaning, we don't care too much in this mission about intrusiveness, and we care slightly more about time than collision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant