-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add LIDAR 3D model: Helios 32. Removed LIDAR3D fbo_nrows parameter, a…
…utomatically computed now from geometry solutions.
- Loading branch information
Showing
9 changed files
with
76 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
<sensor class="lidar3d" name="${sensor_name|lidar1}"> | ||
<pose_3d> ${sensor_x|0.5} ${sensor_y|0.0} ${sensor_z|0.7} ${sensor_yaw|0.0} ${sensor_pitch|0.0} ${sensor_roll|0.0}</pose_3d> | ||
|
||
<vert_fov_degrees>${vert_fov_degrees|20}</vert_fov_degrees> | ||
<vert_nrays>${vert_nrays|32}</vert_nrays> | ||
|
||
<!-- Horizontal / azimuth angular resolution: | ||
The rotation of the Helios sensor configurable: 5 / 10 / 20 Hz | ||
Firing timing of the sensor is fixed at 55.296 μs (=18.084 kHz). | ||
Set the "sensor_rate" (Hz) variable from the parent XML to automatically | ||
adjust the number of points per horizontal line. | ||
--> | ||
<sensor_period>$f{1.0/${sensor_rate|10}}</sensor_period> | ||
<horz_nrays>$f{(1.0/${sensor_rate|10})/55.296e-6}</horz_nrays> | ||
|
||
<!-- 1.0=minimum (faster), larger values=potentially finer details captured --> | ||
<horz_resolution_factor>${horz_resolution_factor|2.0}</horz_resolution_factor> | ||
<vert_resolution_factor>${vert_resolution_factor|2.0}</vert_resolution_factor> | ||
|
||
<range_std_noise>${sensor_std_noise|0.005}</range_std_noise> | ||
<min_range>${min_range|0.20}</min_range> | ||
<max_range>${max_range|110.0}</max_range> | ||
|
||
<visual> <model_uri>../models/velodyne-vlp16.dae</model_uri> <model_roll>90</model_roll> </visual> | ||
|
||
<!-- Publish sensor on MVSIM ZMQ topic? (Note, this is **not** related to ROS at all) --> | ||
<publish enabled="${sensor_publish|false}"> | ||
<publish_topic>/${PARENT_NAME}/${NAME}</publish_topic> | ||
</publish> | ||
</sensor> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters