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

Some suggestions for useful UI enhancements #130

Closed
osrf-migration opened this issue Jul 24, 2019 · 10 comments
Closed

Some suggestions for useful UI enhancements #130

osrf-migration opened this issue Jul 24, 2019 · 10 comments
Labels
enhancement New feature or request minor

Comments

@osrf-migration
Copy link

Original report (archived issue) by Sarah Kitchen (Bitbucket: snkitche).


Some Gazebo 9 things that were helpful for development that we’d like reproduced in the ignition UI (and if they’re already in there, please advise on how to access them):

  • Follow model option to have the view follow a moving robot
  • Go to model, e.g. by double clicking on the name in the entity tree
  • The ability to build our own environments from the subt tiles

Some things that may or may not be in the Gazebo version but would also be useful for exploring performance of our controllers:

  • The ability to toggle on/off “ambient lighting” in the tunnel so we can see the robot body and environment around it. A declaration that it will always be “off” for the tunnel circuit competition would also be appreciated
  • A “reset view” button to whatever the original viewing configuration was, independent of the current robots' states.

Being able to build our own environments, including placing artifacts, may be the closest thing to path critical, since it takes a really long time to test things in the large competition environments. Everything else would just help streamline workflow.

@osrf-migration
Copy link
Author

Original comment by Alfredo Bencomo (Bitbucket: bencomo).


  • set assignee_account_id to "557058:6ff86fcb-b7ab-44a5-b8a6-f6d9cae8b6e8"
  • set assignee to "chapulina (Bitbucket: chapulina, GitHub: chapulina)"

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


Thank you for all the feedback! I've ticketed issues on other repositories so we can keep track of these feature requests. Feel free to vote for the issues 😉

Follow model option to have the view follow a moving robot

https://bitbucket.org/ignitionrobotics/ign-gazebo/issues/29/follow-model-on-the-gui

Go to model, e.g. by double clicking on the name in the entity tree

https://bitbucket.org/ignitionrobotics/ign-gazebo/issues/30/move-user-camera-to-model

The ability to build our own environments from the subt tiles

I'm curious, how were you building custom worlds in Gazebo 9?

This is for a more manual approach:

https://bitbucket.org/ignitionrobotics/ign-gazebo/issues/31/insert-model-from-the-gui

For a more automated approach specific to SubT, it could be convenient to provide teams with a script that generates random SubT worlds.

The ability to toggle on/off “ambient lighting”

https://bitbucket.org/ignitionrobotics/ign-gazebo/issues/32/expose-scene-properties-through-the-ui

A “reset view” button to whatever the original viewing configuration was

https://bitbucket.org/ignitionrobotics/ign-gazebo/issues/33/widget-to-choose-reset-camera-angles


If those issues look reasonable to you, feel free to close this one. You're also welcome to make other feature requests, either here, or directly to ign-gazebo.

Just a heads up, we're not planning on addressing any of these during the current cycle.

@osrf-migration
Copy link
Author

Original comment by Sarah Kitchen (Bitbucket: snkitche).


Thanks! I will check those issues out.

To make a Gazebo 9 tunnel world, I edited the world file manually to place tunnel tiles and artifacts from the subt repo where I wanted them. I was not inserting models directly in the Gazebo GUI to do this. If we don’t care about dynamic loading of tiles, can we do the same now and launch it with a .ign file? Do we need the .dat, .dot, and .tsv files in the subt_ign/worlds directory as well? We’d only use subt fuel models.

Random world generation would also be nice to reproduce for ignition within the next year, but at the moment are most concerned with being able to test specific capabilities of our controller and generate training data for our object classifier efficiently.

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


I edited the world file manually

Got it.

Do we need the .dat, .dot, and .tsv files in the subt_ign/worlds directory as well?

Yes, you need them.

@osrf-migration
Copy link
Author

Original comment by Sarah Kitchen (Bitbucket: snkitche).


@chapulina , which tile models in the SubT Tech Repo are deprecated vs. which will be used for the competition? Are the numbered tiles (e.g. Tunnel Tile 1) all deprecated? I’m experimenting with building an sdf file now and the tiles are not as regularly sized as they were before, so they don’t always fit together particularly cleanly. I’m also able to launch the world with ign gazebo .sdf without those other 3 files. Why do I need them? Again, I’m not interested in doing dynamic loading/levels for my local testing.

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


which tile models in the SubT Tech Repo are deprecated vs. which will be used for the competition?

These are all the tunnel tiles for the practice worlds:

  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 1
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 2
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 3
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 4
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 5
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 6
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile 7
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Tunnel Tile Blocker
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Constrained Tunnel Tile Short
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Constrained Tunnel Tile Tall
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Rough Tunnel Tile 4-way Intersection
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Rough Tunnel Tile 90-degree Turn
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Rough Tunnel Tile Straight
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Rough Tunnel Tile Ramp
  • https://fuel.ignitionrobotics.org/1.0/openrobotics/models/Rough Tunnel Tile Vertical Shaft

Note that the competition worlds may use different patterns.

Beware that the tiles are versioned, so you can clean up your current cache to be sure you get the latest tiles. Clean up like this:

rm -rf ~/.ignition/fuel

Are the numbered tiles (e.g. Tunnel Tile 1) all deprecated?

No, but you may be using an old version. Cleaning up your cache should solve this.

the tiles are not as regularly sized as they were before, so they don’t always fit together particularly cleanly

Could also be a problem with cached models

I’m also able to launch the world with ign gazebo .sdf without those other 3 files. Why do I need them?

You don't need the TSV, but the DOT and DAT are needed for the CommsClient. If you are not testing communications, you should be ok with just the SDF.

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


Sarah Kitchen (snkitche) , can we close this issue?

@osrf-migration
Copy link
Author

Original comment by Sarah Kitchen (Bitbucket: snkitche).


Yes, go ahead, thanks.

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


  • changed state from "new" to "resolved"

@osrf-migration
Copy link
Author

Original comment by Alfredo Bencomo (Bitbucket: bencomo).


  • changed state from "resolved" to "closed"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request minor
Projects
None yet
Development

No branches or pull requests

1 participant