models_to_spawn only works in --development-mode

Issue #162 resolved
Shane Loretz created an issue

using the ariac-network-melodic branch of https://github.com/osrf/ariac-gazebo_ros_pkgs the config models_to_spawn option only works if --development-mode is passed. If it is not passed then the model is never spawned. The service /gazebo/spawn_sdf_model doesn't seem to exist.

Comments (5)

  1. Shane Loretz reporter

    This can be reproduced by launching with

    rosrun osrf_gear gear.py -f $(catkin_find osrf_gear --share)/config/example_custom_config.yaml $(catkin_find osrf_gear --share)/config/sample_user_config.yaml --verbose
    
  2. Steven Gray

    What are the implications of this for testing? Does this prevent the automatic evaluation script from working?

  3. Shane Loretz reporter

    Does this prevent the automatic evaluation script from working?

    The automated evaluation script should work with any trials that avoid models_to_spawn. This includes the three part A qualifier trial config files (wiki page), since they have been written in a way that avoids using this feature.

    However, the Debugging commands on that wiki page use config files in the shipments folder which do rely on this feature, so visualizing what perfect shipments look like will only work using --development-mode.

  4. Log in to comment