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

Followup Issues for Port to VORC #20

Open
4 of 9 tasks
mabelzhang opened this issue Nov 11, 2020 · 3 comments
Open
4 of 9 tasks

Followup Issues for Port to VORC #20

mabelzhang opened this issue Nov 11, 2020 · 3 comments

Comments

@mabelzhang
Copy link
Collaborator

mabelzhang commented Nov 11, 2020

A meta-ticket of followup issues to #19. Applies to the vorc branch.

VORC essentials

Infrastructure

Style

  • This line in VRX competition evaluation
    roslaunch vrx_gazebo sandisland.launch gui:=false urdf:=$WAMV_URDF world:=$TRIAL_WORLD extra_gazebo_args:="-r --record_period ${RECORD_PERIOD} --record_path $HOME/.gazebo" verbose:=true non_competition_mode:=false > ~/verbose_output.txt 2>&1 &
    should really use a separate launch file in vrx_gazebo in https://github.com/osrf/vrx vrx_gazebo, as opposed to piggybacking on sandisland.launch, which is an entry-level example file and doesn't need all the complexity associated with the non_competition_mode Boolean.
  • The non_competition_mode Boolean should be renamed to avoid the double-negative, especially in the launch file, where it is used like "unless non_competition_mode". This might be the flag that hides ROS topics with ground truths when the world runs in competition mode, so be mindful to not drop that feature.
  • Look into why environment variable GAZEBO_MODEL_PATH needs to be set in the launch file with non_competition_mode Boolean. The parameter should really be <export>ed from package.xml and not need to be manually set.
  • xacro files in generated/task_generated/*/world_xacros/ can use better indentation
@mabelzhang mabelzhang mentioned this issue Nov 11, 2020
@crvogt
Copy link
Collaborator

crvogt commented Nov 19, 2020

Modifying task_config

@mabelzhang
Copy link
Collaborator Author

Thanks! By the way I forgot to say I'm doing the gymkhana task in bullet 1. I'm assuming you're taking on bullet 2? I'll open a PR for gymkhana and maybe you could help with trial numbers > 0 for that one as well......? :D

@crvogt
Copy link
Collaborator

crvogt commented Nov 20, 2020

Of course! Sorry, I just noticed that both bullets say task_config XD Yes, I'm working on bullet 2. Definitely, happy to do the gymkhana ones > 0.

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

No branches or pull requests

2 participants