Configuration¶
The defaults are built in. A Ratslang file holds only what differs:
dedrunk intrinsics imu recording.mcap --config dedrunk.rl
dedrunk intrinsics imu recording.mcap -o intrinsics.gravity=9.8127
Precedence: defaults, then --config, then -o. Values use Ratslang syntax
with units. String values need their quotes inside the shell quotes,
-o input.topic='"/imu/data_raw"'.
dedrunk config generate recommended > dedrunk.rl # common settings
dedrunk config generate full # all settings
dedrunk config verify dedrunk.rl
Schema¶
default.rl is also the schema. Types and limits are annotations
(@type time, @min 0s, @enum header, log), and every value is checked:
Unknown settings are reported with the closest name,
'camera.featuers' (did you mean 'camera.features'?). In a file this is a
warning, so files shared with other tools still load. With -o it is an
error.
Generated files start with a schema line for the installed version:
The Ratslang language server uses it for completion, documentation on hover and limit checks. The Ratslang CLI needs a local schema:
dedrunk config generate full > dedrunk-defaults.rl
ratslang check dedrunk.rl --schema dedrunk-defaults.rl
Renamed settings¶
extrinsics.* became lidar_imu.*, and extrinsics.odometry_topic became
trajectory.topic. Old names are refused with the new one. Ratslang rewrites
a file and keeps the old lines as comments:
Sections¶
input- topics, time source, unit scales, time window
output- YAML block name and topic
intrinsics,noise- IMU intrinsics and Allan deviation
trajectory,lidar_imu- Lidar-only trajectory and the Lidar-IMU solver
camera,lidar_camera,camera_intrinsics- feature tracking, edge alignment, board sampling
Every setting with its documentation is in the annotated defaults.