Skip to content

Commit 880d295

Browse files
committed
Refactor visual appearance of Tips in README
1 parent eea8694 commit 880d295

File tree

1 file changed

+13
-10
lines changed

1 file changed

+13
-10
lines changed

README.md

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -165,13 +165,14 @@ roslaunch continuous_clustering demo_kitti_folder.launch path:=${KITTI_SEQUENCES
165165
roslaunch continuous_clustering demo_touareg.launch bag_file:=${ROSBAG_PATH}/vw_touareg_example1.bag
166166
```
167167

168-
**Note:** For the latter launch file, you can use `--wait_for_tf:=false` (default: `true`) argument. It controls whether
169-
to wait for the transform from velodyne to fixed frame (e.g. odometry frame) with a timestamp larger than the one of the
170-
firing or whether to use the latest available (probably incorrect) transform. The former is the accurate approach
171-
(that's why it is the default) but the columns are published in larger batches/slices because they are accumulated
172-
between two transforms. The size of a slice depends on the update rate of the transform (i.e. transforms with 50Hz lead
173-
to batches/slices of 1/5 rotation for a LiDAR rotating with 10Hz). So for a nice visualization where the columns are
174-
published one by one like it the GIF at the top of the page you should disable this flag.
168+
> [!Tip]
169+
> For the latter launch file, you can use `--wait_for_tf:=false` (default: `true`) argument. It controls whether to wait
170+
> for the transform from velodyne to fixed frame (e.g. odometry frame) with a timestamp larger than the one of the
171+
> firing or whether to use the latest available (probably incorrect) transform. The former is the accurate approach
172+
> (that's why it is the default) but the columns are published in larger batches/slices because they are accumulated
173+
> between two transforms. The size of a slice depends on the update rate of the transform (i.e. transforms with 50Hz
174+
> lead to batches/slices of 1/5 rotation for a LiDAR rotating with 10Hz). So for a nice visualization where the columns
175+
> are published one by one like it the GIF at the top of the page you should disable this flag.
175176
176177
# Evaluation on SemanticKITTI Dataset
177178

@@ -230,7 +231,7 @@ Semantic Kitti Labels and using a euclidean distance-based clustering.
230231
See [Issue](https://github.com/url-kaist/TRAVEL/issues/6) in TRAVEL GitHub repository
231232
and [src/evaluation/kitti_evaluation.cpp](src/evaluation/kitti_evaluation.cpp) for more details.
232233

233-
### Option 1: Download pre-generated labels
234+
### Option 1: Download pre-generated labels (fastest)
234235

235236
```bash
236237
cd /tmp
@@ -246,13 +247,15 @@ the correct location (in parent directory of `dataset` folder).
246247
### Option 2: Generate with GUI & ROS setup (assumes prepared ROS setup, see above, useful for debugging etc.)
247248

248249
Generate labels, which are saved to `${KITTI_SEQUENCES_PATH}/<sequence>/labels_euclidean_clustering/`
249-
If you want to visualize the generated ground truth labels in ROS then remove the `--no-ros` flag and use just one
250-
thread (default).
251250

252251
```bash
253252
rosrun continuous_clustering gt_label_generator_tool ${KITTI_SEQUENCES_PATH} --no-ros --num-threads 8
254253
```
255254

255+
> [!TIP]
256+
> If you want to visualize the generated ground truth labels in ROS then remove the `--no-ros` flag and use just one
257+
thread (default).
258+
256259
### Option 3: Generate without GUI or ROS within Minimal Docker Container
257260

258261
```bash

0 commit comments

Comments
 (0)