Dang Tran

Results 11 comments of Dang Tran

Activate `roscore` solve the problem. Sometime even when the roscore is running, the `catkin run_tests` still get stuck. Reset the `roscore ` again solve the problem for me.

Hi, having the same problem at first time. Try running `rosrun rqt_tf_tree rqt_tf_tree` to see the odom name. Then go to `base_frames.yaml` and fix the odometry parameter (ex: `odometry: odom`).

Hi @mohit-khosti, probably you may want to create a new post for this problem. Anyway, can you check whether there is a `tf` between LIDAR and odometry.

Hi @mohit-khosti , can you check which frame does Ouster LiDAR is using? I have not had experience with Ouster, but I use Velodyne 16 (it uses `/velodyne` frame).

`/os1_cloud_node/points` is a topic, not a `tf` frame. To know which frame LiDAR are using, run the `viz.rviz` file and look at `Global Options -> Fixed Frame`

Hi @mohit-khosti, if you use along with the robot (then there will be a frame called `odom` or `odometry`, then probably you want to make sure there is transition between...

@mohit-khosti Can you change `fixed` parameter back to `world` in `base_frames.yaml` file? If you use sensor alone, the original parameter should work fine.

Thank you so much @johnyf for amazing references! Help me a lot in understanding the big picture. Please correct me if I'm wrong: Is the big picture of GR(1) synthesizing...

Thank you so much for such kind explanations @johnyf!

@BrandonStudio I skip the type checking by comment out `@typechecked` at `AttentionMechanism` and its derived classes