JakeBaldwin's profile - activity

It is the former, the compilation and linking. Deleting the build/ and devel/ directories makes no difference. My build went from about 5 or 6 min to 30 min!

I recently upgrade my machine from Ubuntu 14 to Ubuntu 16 and upgrade from ROS Jade to ROS Kinetic as well. I pulled my repository and built and every thing built just fine, tests seem to pass, however, the build is now about 5 times slower! Has anyone experienced this? Any idea what could be causing this and how to fix it?

My understanding of the use of the <arg> tag in launch files is that args must be visible at a higher launch file layers and passed down to lower launch file layers like this:

<launch>
  <arg name="robot_height" value="0.5"/>

  <include file="$(find package)/launch/robot.launch" >
  <arg name="robot_height" value="$(arg robot_height)" />
  </include>

</launch>

What I would really like to do is read arguments from lower layers and use them in higher layers. That would make it quite a bit more flexible and useful. I could have a global configs file for instance and read it from several launch files. Is something like this possible?

An alternative I attempted was to have a launch file set a parameters on the parameter server but as far as I could tell a launch file is unable to retrieve those parameters from the parameter server. I guess that makes sense based on the fact that a launch file is processed as a whole so the timing may not coordinate very well but wouldn't that be sweet!?!?

I guess what I'm really looking for is a way to have globally accessible variables between my launch files to make configuration a breeze. Is this possible?

I am running a .bag file from a launch file but I want to make the filepath generic so other team members can run this launch file. So I have:

<launch>
    <node pkg="rosbag" type="play" name="player" args="/home/jimbob/bagfiles/test.bag" />
</launch>

But not everyone on my team is named jimbob so I want to replace "/home/jimbob/" with maybe ${HOME} or something generic.

In my CMakeList.txt file for a package I would like to add a test using catkin_add_gtest(test_name cpp_file_name)

Is there a way to pass arguments to gtest such as --gtest_also_run_disabled_tests?

I would like to pass an argument to .test launch files in order to run only specific tests. Currently I can run all of my unit tests and node unit tests with: catkin_make run_tests

But I would like to pass an argument to the .test files and determine if that test should run or not like: catkin_make run_tests ARGS="runNodeTests"

Then in my .test file have something like:

<launch> <group if="runNodeTests"> <node name="serial_driver" pkg="my_package" type="serial_driver_node"/> <test test-name="serial_driver_test_node" pkg="my_package" type="Test"/> </group> </launch>

where runNodeTests either launches the node test or it doesn't.

Is this possible? (Sorry about the .test file formatting)

I have several classes of tests that I would like to run independently. I have standard unit tests which I am adding in the CMakeLists file as catkin_add_gtest(...) and node unit tests (some that depend on HW and some that do not) which are added in CMakeLists as add_rostest_gtest(...). I have around 7 packages or so and each of them contain both standard unit tests as well as node tests. I would like to be able to run all of the tests of a certain type from all of my packages. Like run all of the unit tests or run all of the node tests that depend on HW, etc. Currently running "catkin_make run_tests" will run all of the tests. and "catkin_make run_tests_package_name" will run the tests in a given package. Is there a way to run my tests independently by type no matter what package they reside in?