actinium226's profile - activity

overview network karma followed questions activity

2023-03-28 10:37:43 -0500	received badge	● Nice Question (source)
2022-09-27 15:40:44 -0500	received badge	● Favorite Question (source)
2020-11-01 15:21:22 -0500	received badge	● Famous Question (source)
2020-01-03 06:29:26 -0500	received badge	● Notable Question (source)
2019-12-20 23:35:12 -0500	received badge	● Popular Question (source)
2019-12-19 14:34:08 -0500	received badge	● Student (source)
2019-12-19 01:07:20 -0500	received badge	● Enthusiast
2019-12-18 18:19:51 -0500	asked a question	How to disable FastRTPS generation in ROS2? How to disable FastRTPS generation in ROS2? We've switched over to using RTI Connext Micro, and I'm wondering if we can
2019-12-18 18:18:50 -0500	asked a question	How to disable FastRTPS generation in ROS2? How to disable FastRTPS generation in ROS2? We've switched over to using RTI Connext Micro, and I'm wondering if we can
2019-09-25 02:12:39 -0500	received badge	● Famous Question (source)
2019-07-15 17:58:16 -0500	received badge	● Notable Question (source)
2019-07-08 17:54:06 -0500	commented answer	Params appear broken in ROS2? PR Here: https://github.com/ros2/ros2_documentation/pull/297
2019-07-08 15:58:46 -0500	received badge	● Popular Question (source)
2019-07-08 13:15:10 -0500	commented answer	Params appear broken in ROS2? Aha, that was it. I enabled allow_undeclared_parameters and that got it going. I'll make a PR against the parameters doc
2019-07-08 12:59:04 -0500	commented answer	Params appear broken in ROS2? Aha, that was it. I enabled allow_undeclared_parameters and that got it going. I'll make a PR against the parameters doc
2019-07-08 12:57:42 -0500	received badge	● Supporter (source)
2019-07-08 12:57:41 -0500	marked best answer	Params appear broken in ROS2? According to https://index.ros.org/doc/ros2/Tutori..., if I have a properly formatted parameters yaml file, and I call `ros2 run` with `__params:=` pointing to that file, I should see the parameters defined in that file listed when I run `ros2 param list`, correct? I'm doing this, but the only parameter I see when running that command is `use_sim_time`, which appears whether or not I pass the parameters. The parameter file is getting parsed, I know this because if I don't have `ros__parameters` in there or some other inappropriate syntax it will complain and exit without running the node. I'm on Ubuntu 18.04 on ROS Dashing. Is there any other useful info about my setup that I could provide? I'm also a little confused on the expected node name within the parameters file. Does it need to match exactly the node name I provide when I call `ros2 run`? That is what I've been doing, but it doesn't seem to make any difference.
2019-07-08 12:57:41 -0500	received badge	● Scholar (source)
2019-07-08 02:02:03 -0500	asked a question	Params appear broken in ROS2? Params appear broken in ROS2? According to https://index.ros.org/doc/ros2/Tutorials/Node-arguments/#parameters, if I hav